> 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/mrc16.md). # MRC 16: Toward MOR Interoperability *** ## Status **April 1, 2024: IMPLEMENTED** *** ## Introduction To set the stage, MOR is currently instantiated as an ERC20 on Arbitrum. The coin exists, however is unmoveable/untradable until May 8th 2024. ## Goal MOR to be omnichain to whatever degree it makes sense. At minimum, we want it to exist seamlessly on Arbitrum & ETH L1. Before May 8th 2024 to modify/upgrade/change the Smart Contract is easier. After that date it's obviously messier. Thus this topic should be considered / then implemented before May 8th 2024. ## Evaluation Many of the open source Smart Contract developers have evaluated LayerZero's OFT paradigm for use in the Morpheus Smart Contracts. In particular, they liked: * 1. the immutability/non-upgradability of the contracts, and * 2. the gas abstraction for better UX. * 3. The oracle function that can help denominate all yield contributions to Morpheus via ETH price. While Morpheus is not exclusive to any chain or project, Layer Zero seems to be a good starting point to increase the Interoperability of the MOR token and broaden types of yield contribution. ## Implementation To start sending tokens from arbitrum to other chains, developers need to do is: * 1. Deploy the OFT Adapter contract which works like a lockbox on the source chain. * 2. Deploy the OFT contract on each new chain which will become the canonical MOR tokens for those new chains. ## Technical Documentation Details Link to Layer Zero Docs: --- # 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/mrc16.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.