Title: RFC Multichain Deployment Process
Author(s): @Bobbay_StableLab, @Matt_StableLab
Submission Date: 2/20/2023
This proposal introduces the “Multichain Deployment Process” to provide a framework and process to deploy Euler on other chains.
This proposal introduces a “Multichain Deployment Process” as a method to formalize proposals regarding Euler deploying to new chains. This will provide a clear and organized pathway for new chains to be reviewed for deployment.
With recent forum posts, there is a motivation to deploy Euler on other chains, and we need to introduce a framework to standardize this process. In the current state, there will be a lot of discrepancies between the applications, with some providing too little or unnecessary information. As a community, we can refine this template to request the relevant information for the community to make an informed decision.
This proposal will include a new template for multichain deployment, a new process for proposing new deployment, and a list of minimum requirements chains must meet to be considered.
Multi-chain deployment Template
Author/relation to the proposed chain:
Point of contact(POC):
This will be the POC at the proposed chain through which the Euler Community will request further information.
Overview of Proposal:
Description of the proposal, including timeline, team, and benefits to Euler
How does this proposal benefit the Euler ecosystem? Why is the proposed chain ideal for Euler? What solutions does it provide to users?
Did you apply for an Euler Grant? (Approved/ Rejected/ Did not apply)
- TVL on the Chain
- Amount of protocols on the chain
- (#) of unique addresses on the chain
- (#)of new users joining in the past 90 days
- (#) of unique addresses executing a transaction in the past 30,60 and 90 days.
- Average gas fee in the past 30 days
Why did you choose this specific chain? What benefits does it provide over other chains? Do you have support (foundation or grant)? Will any incentives be provided to attract users?
What other borrowing/lending markets already exist? What is their TVL? Why would Euler be a good addition? What TVL do you anticipate Euler to have?
Will you use a native bridge or a third party for cross-chain messaging? Provide a rationale for your choice.
What will be the expected deployment cost?
What is the expected timeline for deployment?
How will Euler need to change to deploy to the proposed chain?
can it use a permissionless oracle? Will permissionless listing be possible? Etc…
Who will maintain the protocol after deployment?
Does the Euler Labs team need to dedicate more people to working on the new chain full-time?
How will the deployment be marketed?
Will the new chain help with promoting Euler’s deployment?
What technicalities are required to deploy on the chain? Are they available? E.g. Price feed, oracles etc.
Discuss the security implications/considerations relevant to deploying on your chain of choice.
How many node operators are there? How distributed are node operators? How many addresses own 50% of the chain’s token? How many of these are foundation addresses?
This will follow the current EulerDAO governance process.
Post a forum post using the multichain deployment template
Title the post “RFC Deploying Euler to XYZ Chain” with the tags “RFC” and “eIP”
Add a temperature check poll at the bottom of the post.
After the temperature check is passed and 7 days have gone by since the original posting, make the following changes:
Repost the proposal as a new comment in the same thread with any changes suggested by the community.
Change the title to “eIP ## Deploying Euler to XYZ Chain.
1. Where ## is the next sequential number of eIP
2. Where XYZ is the chain name
Change thread tags to “Formal Submission” and “eIP”
After two days in the formal submission stage anyone with at least 500 EUL can post the proposal to snapshot.
The proposal thread tags should then be changed to “live vote” and “eIP”
After the snapshot vote ends the tags should be changed to “eIP” and “voted proposal”
After a successful snapchat vote, the Euler Labs team will start the deployment process
After a failed snapshot vote no further action is needed. The proposal can be modified and submitted after a ten-day waiting period.
Guideline Minimum Standards
These are guidelines. These are the minimum requirements a chain must meet to be considered for deployment..
- At least $100M in TLV
- At least $5M in daily volume
- At least 5,000 daily active users
- A strong oracle or new governance system in place to manage asset tiers/listings
These standards are up for discussion and can be amended. If there is a first-mover advantage for Euler to launch on another chain, this should be considered a large contributing factor.
Expanding to other Alt L1s and L2s has been a reoccurring discussion in Euler for the past couple of months. Euler Governance has the power to deploy Euler on another chain; therefore, token holders must have sufficient information to distribute this license.
In creating a multi-chain deployment guide, the Euler community should request a level of information that enables token holders to make an informed decision when choosing to deploy Euler on other chains. The non-technical evaluation provides enough information to gain a superficial understanding of the chain. A technical assessment, supplemented by TBD, will provide enough information to make an informed decision.
- This introduces an official process for authors to follow to deploy Euler on other Chains.
- The community agrees on a standard evaluation template
- Reduces discrepancies between applications
- This makes the deployment process longer.
- The amount of information requested might deter applicants.
Overall, the pros outweigh the cons as this introduces a sustainable process to deploy Euler on other chains.
Gather community feedback to refine this process, discuss minimum standards chains must meet, and discuss the possibility of a working group to help manage this process. Then push this proposal to a Snapshot vote.
If this proposal passes, this will be recognized as the official process to deploy Euler on another chain. An author has to use the relevant template. Otherwise, the application will be considered void.
We recommend pinning the process up within the governance forums.