# Future Interoperability As the game continues to evolve, there are ambitious plans to expand its reach beyond the Arbitrum Layer 2 solution and into Ethereum's Layer 1, as well as other Layer 2s. The idea is to create a truly interoperable metaverse where assets can flow freely across multiple blockchains. Imagine a player being able to use a Legendary Avatar minted on Ethereum's mainnet in the "2d.miami" world running on Arbitrum. Or perhaps, using in-game assets from other Layer 2 solutions like zk-Rollups or even entirely different blockchains like Binance Smart Chain. The possibilities are endless and incredibly exciting. The integration of assets across these layers and blockchains would not only enrich the in-game economy but also enhance the overall user experience. Players could bring in unique assets from various ecosystems, adding a layer of complexity and strategy to the game. This cross-chain asset integration would also open up new avenues for partnerships with other games and DeFi projects, creating a more vibrant and interconnected metaverse. Moreover, this future development aligns perfectly with the broader trends in the blockchain space, where the walls between different chains are gradually coming down. By positioning "2d.miami" at the forefront of this interoperability movement, the game is not just following the trend but setting the pace for what a truly decentralized and interconnected gaming experience should look like. So, the future of "2d.miami: Memory Hunters" is not just confined to one blockchain or layer; it's a vision of a game that's as boundless as the imagination of its players. 🌌 --- # Agent Instructions: 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: ``` GET https://2dmiami.gitbook.io/2d.miami-memory-hunter/technology/future-interoperability.md?ask= ``` The question should be specific, self-contained, and written in natural language. 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.