> For the complete documentation index, see [llms.txt](https://gitbook.mor.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://gitbook.mor.org/mrc/closed/mrc56.md).
# MRC 56: Design Options For Builders V2 Migration
The testing community has identified some fundamental trade offs with the version 2 of the Morpheus Smart Contracts. These are important trade offs to consider as the introduction of a trusted third party goes against the values of Morpheus as a project. For these reasons Migration of the Subnets to V2 should be moved to after these issues have been addressed.
### The 4 functions / features / trade offs of Builders V2 are:
* Multichain Support (Base + Arbitrum L2s on Ethereum)
* Requirement for an Oracle (multisig proposed)
* Requirement for an Escrow (multisig proposed)
* Power Factor
In order to gain Multi chain support requires the introduction of an Oracle & an Escrow. The use of the Power Factor also adds complexity and re-enforces these requirements.
I've proposed a simplified scenario. However to achieve it the trade off is to only deploy to Base instead of multiple L2s and the Power Factor has to removed. Until Ethereum has cross L2 support for transactions, I think that is the best set of trade offs.
## Technical Options to be Revisited
Worth revisting the single chain approach when ERC 7683 is implemented in mainnet Ethereum and L2s. Details at this website:
### Design Options Details:
### Real World Data on Chain Usage For Builders:
* 1. Most of the Subnets are Building / bootstrapping an agent, app, website, service.
* 2. To my knowledge only Coincap is using the Builders for payment as access to a product and Venice however not at a meaningful scale.
* 3. As for which chain the vast majority of Builders are on Base, again with the exception of Coincap & Venice.
* 4. Of the Stakers 300,000 are to a Builder Subnet (mostly on Base), 600,000 are self Stakers (mostly on Arbitrum).
* 5. If the goal is NEW people buying / using MOR to Stake to Builders most of that is on BASE. As is Venice. As are Coinbase's Agent tools and all the agent tools, as are the largest volumes.
### Conclusion on Question about Multichain Support
### Plan for Multi Chain Support:
* Stage 1: Support Arbitrum and Base (manual calculation) for May 15th (testing dependent).
* Stage 2: Coincap to help with Script and Hosting for June 15th / July 15th (testing depending).
* Stage 3: Switch to automated intents when available on Ethereum L2s (when ERC 7683 is implemented in mainnet Ethereum and L2s. Details at this website: )
---
# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.
Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:
```
GET https://gitbook.mor.org/mrc/closed/mrc56.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.