This post sets the minimum standard requirements required to implement a new yield source or an asset in the Idle protocol.
Leagues could extend the framework on decisions that affect core operations and infrastructure, as well as the timing for new integrations to pass into the production stage.
|Security||Has a reputable company audited contracts, or are they fork of audited projects?||1 custom audit|
|Months of activities since last contract update||3 months|
|Are contracts immutable or upgradeable by admins? If upgradable, how many admins control the keys, and are they anonymous?||Immutable preferred, but answers evaluated case by case|
|Is there an emergency exit plan?||Evaluated case by case|
|Are there protocol dependences?||Evaluated case by case|
|Has the protocol/asset suffered losses in the past?||Evaluated case by case|
|Resiliency||Current protocol TVL or asset market cap||$ 50M+|
|Expected TVL/market cap in 3 months||$ 100M+|
|Current protocol’s or supported services’ APYs||+30% than Idle 30-day strategy average|
|What would be the impact on APYs when deploying Idle TVL?||Less than 10%|