Integrations Standard Requirements

Summary

With the organization of grants and the B2B Affiliate Program launch, Idle is interfacing with many partners and protocols to start collaborations and make integrations.

As we look for the continued growth of the Idle ecosystem, this framework would guide the community in evaluating yield generating products into Idle protocol.

Thus, as discussed in this post, the proposed Due Diligence Process would define parameters that a yield source should meet before being implemented into Idle protocol. The framework could be extended on decisions that affect core operations and infrastructure.

Details

Topic	Metric	Minimum requirements
Audit and due diligence	Has a reputable company audited contracts, or are they forks 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
Performances	Current protocol TVL or asset circulating supply	$ 50M+
	Expected TVL/supply in 3 months	$ 100M+
	Current protocol’s or supported services’ APYs	+30% than Idle 30-day strategy average
	Would Idle asset liquidity affect APYs?	Less than 10%

Vote Options

Please cast your vote on one of the following options:

• FOR: Proceed with the listed safety criteria
• AGAINST: Not proceed with this proposal
• DISCUSS MORE: Discuss more the safety criteria