# IDLE token

<figure><img src="https://4022236167-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-Lw-v0NTae0RVW1spR9R%2Fuploads%2FYU4Aa1AgERu22f6C1Pfa%2FIDLE.png?alt=media&#x26;token=bf9adb33-e0f7-4b95-b8a2-0d35bb648f72" alt=""><figcaption></figcaption></figure>

The Idle protocol is governed and upgraded by IDLE token-holders, using three distinct components:&#x20;

1. IDLE token:[`0x875773784Af8135eA0ef43b5a374AaD105c5D39e`](https://etherscan.io/address/0x875773784Af8135eA0ef43b5a374AaD105c5D39e)
2. Governance contract (Governor Bravo):[`0x3D5Fc645320be0A085A32885F078F7121e5E5375`](https://etherscan.io/address/0x3D5Fc645320be0A085A32885F078F7121e5E5375)
3. Timelock contract:[`0xD6dABBc2b275114a2366555d6C481EF08FDC2556`](https://etherscan.io/address/0xD6dABBc2b275114a2366555d6C481EF08FDC2556#code)

{% hint style="info" %}
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\]](https://docs.idle.finance/developers/best-yield/security-management-policy), [\[2\]](https://docs.idle.finance/developers/yield-tranches/security-management-policy).
{% endhint %}

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.