IDLE token
Governance > Idle DAO > IDLE token
Last updated
Governance > Idle DAO > IDLE token
Last updated
The Idle protocol is governed and upgraded by IDLE token-holders, using three distinct components:
IDLE token:0x875773784Af8135eA0ef43b5a374AaD105c5D39e
Governance contract (Governor Bravo):0x3D5Fc645320be0A085A32885F078F7121e5E5375
Timelock contract:0xD6dABBc2b275114a2366555d6C481EF08FDC2556
Together, these contracts allow the community to propose, vote and implement changes to the contracts owned by the Timelock. The ownership of idleTokens from BY strategies, idleCDO from PYTs, and the IdleController contracts have been all transferred to the Timelock contract.
The Timelock contract can modify system parameters, logic, and contracts in a 'time-delayed, opt-out' upgrade pattern, as reported here [1], [2].
When a proposal is created, the community can submit their votes during a 3-day voting period. If a majority and at least 520,000 (4% of the total supply) votes are cast for the proposal, it is queued in the Timelock and can be implemented after 2 days.
