Polygon Contracts

Badger Infrastructure

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: 0x1FcbE5937B0cc2adf69772D228fA4205aCF4D9b2

  • ibBTC: 0x4EaC4c4e9050464067D673102F8E24b2FccEB350

General Infrastructure

  • keeperAccessControl: 0x46fA8817624eEA8052093EAb8e3FdF0e2e0443b2

  • guardian: 0xCD3271021e9b35EF862Dd98AFa826b8b5198826d

  • badgertree: 0x2C798FaFd37C7DCdcAc2498e19432898Bc51376b

  • rewardsLogger : 0xd0EE2A5108b8800D688AbC834445fd03b3b2738e

  • registry: 0xFda7eB6f8b7a9e9fCFd348042ae675d1d652454f

  • governance_timelock: 0x4f7D83623eeB135eB13DBcEA1A87a96945abE9cc

Multisig Wallets

  • dev_multisig: 0x4977110Ed3CD5eC5598e88c8965951a47dd4e738

  • techops_multisig: 0xeb7341c89ba46CC7945f75Bd5dD7a04f8FA16327

Operational Wallets

  • 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

Proxy admins

  • proxyAdminTimelock: 0x9208E6c28959c47E58344d5f84d88F07Fca96CFC

  • proxyAdminDev: 0xC4fE5Db8D3c0d0f410D6A7496Faa4f1658d2a301

Sett System

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).

  • NA

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).

  • NA

Controllers The Controllers interface the vault contracts with their respective strategies. They are used to handle strategy migrations, earns and withdraws:

  • native: 0xc00e71719d1494886942d6277DAeA20494cf0EeC

Deprecated Contracts

Vaults

  • bslpibBTCWbtc: 0xEa8567d84E3e54B32176418B4e0C736b56378961

  • bqlpUsdcWbtc: 0x6B2d4c4bb50274c5D4986Ff678cC971c0260E967

  • bcrvRenBTC: 0x7B6bfB88904e4B3A6d239d5Ed8adF557B22C10FC

  • bcrvTricrypto: 0x85E1cACAe9a63429394d68Db59E14af74143c61c

Strategies

  • native.slpibBTCWbtc: 0xDed61Bd8a8c90596D8A6Cf0e678dA04036146963

  • native.qlpUsdcWbtc: 0x809990849D53a5109e0cb9C446137793B9f6f1Eb

  • native.crvRenBTC: 0xF8F02D0d41C79a1973f65A440C98acAc7eAA8Dc1

  • native.crvTricrypto: 0xDb0C3118ef1acA6125200139BEaCc5D675F37c9C

PreviousArbitrum ContractsNextFantom Contracts

Last updated

Was this helpful?