Other > FAQs
On this page, we summarize all the FAQs included in our documentation split by category.
The algorithm is programmed to analyze the supply rate functions across integrated protocols and total funds in the pool, and it's able to constantly rebalance capital across any number of protocols to earn the highest interest rate possible with very high precision.
The displayed APY is the aggregated interest rate of the APYs coming from multiple lending providers, depending on the allocated funds and the governance tokens from the underlying protocols.
Several factors can trigger a rebalance. Factors related to network conditions/congestion, and if a new allocation exceeds the previous one by a significant percentage. Hence, the timing is variable.
In general, a rebalance happens every 3 hours on Ethereum and hourly on Polygon.
Yes, any user who has already deposited funds within one or more pools can add additional funds to the current deposited assets.
Each addition of new funds always requires a confirmation and signature via smart contract, and therefore require to pay the related network fees (not controlled or received by Idle in any case).
Read the PYTs Edge Cases section to learn more about default or hack scenarios and how they would be managed.
If the attacker is able to completely drain a protocol, both Senior and Junior tranches would be affected. This event is extremely rare, as usually a hack is composed of recursive interactions that steal part of the funds. When the protocol itself is hacked, there are guardians that can pause the system and prevent further losses. Even if validators are directly hacked, it's unlikely that all the validators will suffer the same issue, just causing partial losses.
In this vision, Senior Tranche increases the security profile of the liquidity provider, adding an extra layer of protection: Junior Tranche deposits.
There are no locking periods or epochs and users are free to enter and exit at any time. The interest earned (and governance tokens, after being partially sold in the market) will be split between the two classes according to a predefined ratio called trancheAPRSplitRatio (e.g. 10% interest to Senior tranche holders and 90% to Junior tranche).
There is no lockup period for staking.
The base APY, before being split between tranches, is provided by the underlying strategy that takes into account the reinvestment of the accrued governance tokens (except for eventual IDLE rewards). The actual APY of each tranche class is determined by the ratio between the current underlying TVL of Senior and Junior tranches (i.e. APY = share of yield allocated to senior tranches/Senior TVL). The APY has to be considered net of fees.
For more info view the readme on GitHub.
Fees are collected at each harvest event. When the strategy auto-reinvest accrued tokens, the Idle protocol charges a 10% performance fee. Revenues get routed to the FeeCollector address.
To keep a good ratio between Senior and Junior tranches and a healthy APY, part of farmed governance tokens (e.g. IDLE) are redistributed to users who stake their tranche tokens in specific tranche rewards contracts.
You can always deposit in the Tranche of your preference. Staking is available only in Senior tranches. Next to Senior tranches APYs you can over the ℹ️ and see the breakdown of the APR.


Include your wallet address as part of the deposit transaction data. More information regarding the input parameters of the deposit method can be found in the BY Methods section in the Protocols chapter.
Leagues process the $IDLE payments towards the vesting contracts weekly. The minimum threshold to execute the fee-sharing is 500 $IDLE.
Accrued shared fees that do not reach the minimum threshold are recorded in the dashboard until their sum is higher than 500 $IDLE. Once rewards reach that threshold, the fee-sharing payment is executed.
The Treasury League deploys a vesting contract for each partner. Deployment is executed when the first payment is processed. The same contract will receive the following payments and only the referral address is entitled to redeem the vested tokens. Tokens are vested on a linear basis over a 3-month period and the partner can claim them anytime.
Your tier is calculated as the average Partner Deposited Asset (PDA) value between the first deposit and the first payment. When the fee-sharing transaction is executed, the tier is then calculated in the timeframe between that day and the next payment. You can check some helpful examples here.


Include your wallet address as part of the deposit transaction data. More information regarding the input parameters of the deposit method can be found in the BY Methods section in the Protocols chapter.
$MATIC rewards are processed on a weekly basis.
Accrued bonuses that do not reach the minimum threshold are recorded in the dashboard until their sum is higher than 100 $MATIC. Once rewards reach the threshold, the bonus payment is executed.
The Treasury League sends the bonus to the referral address attached to deposits, no need to claim it.
You can track the $MATIC rewards on the dedicated Polygon Dune Analytics dashboard.

Idle DAO

IIP, as explained in the docs Glossary, stands for the Idle Improvement Proposal and represents a proposal for a protocol change that needs to go through $IDLE token holders' on-chain vote.
Every user that holds $IDLE can vote, but to get the eligibility before voting they must self-delegate or delegate to others their voting rights.
Every address with at least 130,000 $IDLE delegated can submit on-chain proposals. At any stage, the proposal can be cancelled by its creator or if he/she loses the required delegated votes.
The quorum to execute any change on the protocol is 520,000 $IDLE and an IIP is executed if the majority (50% +1) of the voters cast a “For” vote.


Gauge weights account how much $IDLE will be received by a liquidity gauge.
Only users who stake/lock their $IDLE (i.e. stkIDLE holders) have access to gauge weight voting.
Gauges’ weights change once a week, every Thursday (~12:00 AM UTC).
Users can change their weights once every 10 days. The 10-days window is counted since their last voting preference submission.
Users don't have to vote again every week except if they want to change their vote distribution.
Your voting power applies to all gauges but may produce different boosts based on how much liquidity you are providing and how much total liquidity the PYT pool has.
Need further help? Check our guides list or get in contact on Discord.