Arbitrum Contracts
The Badger infrastructure is conformed by all the contracts around the general functioning and operations of the BadgerDAO. This includes the tokens, emissions, governance, permissioned actors and proxies administration.
Tokens
- badger: 0xbfa641051ba0a0ad1b0acf549a89536a0d76472e
- ibBTC: 0x9Ab3FD50FcAe73A1AEDa959468FD0D662c881b42
- keeperAccessControl: 0x265820F3779f652f2a9857133fDEAf115b87db4B
- guardian: 0xDb0C3118ef1acA6125200139BEaCc5D675F37c9C
- badgertree: 0x635EB2C39C75954bb53Ebc011BDC6AfAAcE115A6
- rewardsLogger : 0x85E1cACAe9a63429394d68Db59E14af74143c61c
- registry: 0xFda7eB6f8b7a9e9fCFd348042ae675d1d652454f
- dev_multisig: 0x468A0FF843BC5D185D7B07e4619119259b03619f
- techops_multisig: 0x292549E6bd5a41aE4521Bb8679aDA59631B9eD4C
- techops_multisig_deprecated: 0xF6BC36280F32398A031A7294e81131aEE787D178
- ops_deployer: 0xDA25ee226E534d868f0Dd8a459536b03fEE9079b
- ops_deployer2: 0xeE8b29AA52dD5fF2559da2C50b1887ADee257556
- ops_deployer3: 0x283C857BA940A61828d9F4c09e3fceE2e7aEF3f7
- ops_deployer4: 0xef42D748e09A2d9eF89238c053CE0B6f00236210
- ops_deployer5: 0xC6a902de22b10cb176460777ce6e7A12A6b6AE5a
- ops_deployer6: 0x7c1D678685B9d2F65F1909b9f2E544786807d46C
- ops_executor1: 0xcf4fF1e03830D692F52EB094c52A5A6A2181Ab3F
- ops_executor2: 0x8938bf50d1a3736bdA413510688834540858dAEA
- ops_executor3: 0xC69Fb085481bC8C4bfF99B924076656305D9a25D
- ops_executor4: 0xBB2281cA5B4d07263112604D1F182AD0Ab26a252
- ops_executor5: 0xcDAb3AcC1AD3870a93BB72377092B67e290D76f3
- ops_guardian: 0x29F7F8896Fb913CF7f9949C623F896a154727919
- ops_keeper: 0x872213E29C85d7e30F1C8202FC47eD1Ec124BB1D
- ops_root-validator: 0x1318d5c0C24830D86Cc27Db13Ced0CED31412438
- ops_cycle_bot: 0x68de9E2b015904530593426d934CE608e117Fa7A
- ops_botsquad: 0xF8dbb94608E72A3C4cEeAB4ad495ac51210a341e
- ops_botsquad_cycle0: 0x1a6D6D120a7e3F71B084b4023a518c72F1a93EE9
- ops_earner: 0x46099Ffa86aAeC689D11F5D5130044Ff7082C2AD
- ops_harvester: 0x73433896620E71f7b1C72405b8D2898e951Ca4d5
- ops_external_harvester: 0x64E2286148Fbeba8BEb4613Ede74bAc7646B2A2B
- proxyAdminTimelock: 0xBA77f65a97433d4362Db5c798987d6f0bD28faA3
- proxyAdminDev: 0x95713d825BcAA799A8e2F2b6c75aeD8b89124852
The Sett System is conformed by all the contracts behind the Sett products. Each one of the Setts is made up of three components: Vault, Strategy and Controller.
Vaults
Vaults handle the user interaction with the Setts. This mainly includes the deposits and withdraws. The naming convention for vaults is:
b + Underlying Asset Name
(Example: A vault that handles BADGER token is called bBADGER).- No active vaults in Arbitrum
Strategies
Strategies implement the logic to generate yield for a Sett. They handle actions such as harvest and tending. The naming convention for strategies is
type of strategy + . + underlying asset
(Example: A native strategy that handles BADGER is called native.badger).- No active strategies in Arbitrum
Controllers
The Controllers interface the vault contracts with their respective strategies. They are used to handle strategy migrations, earns and withdraws:
- native: 0x3811448236d4274705b81C6ab99d617bfab617Cd
Last modified 9mo ago