IDLE staking
Governance > IDLE staking
Last updated
Was this helpful?
Governance > IDLE staking
Last updated
Was this helpful?
Staking allows users to lock their IDLE for a flexible period (up to 4 years) in return for a series of benefits. The contracts for IDLE staking are based on the , decided via .
Depending on the lock time, a specific amount of stkIDLE is generated from the IDLE locked. The lock scale is as follows
1 IDLE
1 year
0.25 stkIDLE (25%)
1 IDLE
2 years
0.50 stkIDLE (50%)
1 IDLE
4 years
1 stkIDLE (100%)
stkIDLE linearly decreases from the lockup date to the end date. Only at the end of the lock time, it is possible to withdraw the starting locked IDLE tokens. The general formula to compute the stkIDLE balance at any point in time is:
Example: 5000 IDLE locked for 3 years and 2 months (with 30 days/month) would give:
As described above, the quantity of stkIDLE decreases constantly in proportion to the reduction in lock time (lock expiration), down to 0 at expiration. For example, two months after the initial lock, the stkIDLE holder from the example above would have a stkIDLE balance of:
The staking contract is implemented as a non-standard ERC-20 token, which is non-transferable and can only be created by staking IDLE by callingcreate_lock(uint256 _value, utin256 _unlock_time)
.
By default, smart contracts cannot participate in staking, as this would allow for trivial which could be implemented to circumvent the non-transferable nature of stkIDLE.
However, Smart contracts can be whitelisted via a governance proposal as described .
The IDLE voting power deposited in the staking contract is delegated to a community multisig, which is used to vote on governance proposals based on the .
The community multisig is located at: