On Chain Registry for V1, V2 Vaults as well as Known Addresses via extensibly key address pairs
Mainnet https://etherscan.io/address/0xfda7eb6f8b7a9e9fcfd348042ae675d1d652454f
Polygon: https://polygonscan.com/address/0xfda7eb6f8b7a9e9fcfd348042ae675d1d652454f
Arbitrum: https://arbiscan.io/address/0xFda7eB6f8b7a9e9fCFd348042ae675d1d652454f#code
Fantom https://ftmscan.com/address/0xFda7eB6f8b7a9e9fCFd348042ae675d1d652454f
registry.get("controller")
registry.getFilteredProductionVaults("v1", 2);
registry.getFilteredProductionVaults("v2", 0);
registry.getProductionVaults();
- Run The Console
brownie console
- Get the registry
registry = BadgerRegistry.at("ADDRESS FOR THE NETWORK YOU WANT")
- Get the keys
registry.get("whatever")
Go spam keys(uint)
with various indexes until you run out of range
Go spam versions(uint)
with various indexes until you run out of range
Check the Enum VaultStatus
for the steps
By defintion the list of keys is incomplete, just iterate over the keys(uint256)
to find them
Some of these keys may be missing in some deployments
While not a security vulnerability this may impact some of our flows
Please do create a ISSUE if you find a missing key
This is a list of keys we use at Badger to standardize cross-chain deployments
-
controller
-
guardian
-
keeper
-
badgerTree
-
governance
-
devGovernance
-
proxyAdminDev
-
proxyAdminTimelock
-
governanceTimelock
-
timelock
-
keeperAccessControl
-
rewardsLogger
-
BADGER
-
ibBTC