You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
To prevent API poisoning, yearn created a contract that verifies data against on chain data to ensure the contracts the frontend is interacting with are approved contracts.
Summary (Required)
To prevent API poisoning, yearn created a contract that verifies data against on chain data to ensure the contracts the frontend is interacting with are approved contracts.
To implement this we'd need to:
badger.com
on DNSSEC via ENSallowlist
contract and add conditions like thisRequest Metrics (Required)
Rate how the level of importance of the feature, effort and and risk associated
Options: low, medium, high
Documentation (optional)
Main repo for eth-allowlist
https://github.com/x48-crypto/eth-allowlist
Contract deployment:
https://etherscan.io/address/0xef01bc08cf155098bda7a2efbc7ccef632d03440#readContract
Integration contract example (to use registry to check if the address is a vault for example):
https://github.com/x48-crypto/eth-allowlist/blob/main/contracts/implementation_examples/ImplementationYearn.sol
Resources (optional)
Add any new or updated resource requirements for the system
The text was updated successfully, but these errors were encountered: