Web3 Realms Interoperability Standard

One core pillar of the open web3 metaverse is virtual tokenized land. However, as it sits today, there is no fluent way or well defined standard for different virtual worlds to be able to have an interoperability component within their land across the realms.

Establishing a standard for interoperable districts is of critical importance, because, if we are confined to silos within the metaverse then it goes against some of the core principles of what the metaverse actually is; a truly persistent, immersive and open space measured across time.

Under the last PODE announcement (Can be viewed here) extensive details were shared in regards to implementation of the Player Creator Portal as a native web3 steam alternative. The concept of Virtual Land Offerings (VLOs) for indie developers and modders within the platform as they integrate web3 value layer mechanics through NFT wrapped content and assets was described as well.

One of the most prominent pathways for these VLOs to promulgate beyond the initial seed game environments where their utility and value is first surfaced is done through a clear and established standard for the interoperability of these NFTs across different virtual worlds. This standard will first have strong usage within the IMG (Indie Modder’s Guild) Constellation and also can be adopted with a soft enforcement mechanism by any web3 orientated virtual land protocol, present or future.

With that said, this proposal is to start initiating the deliberation around both the establishment of the web3 realms interoperability standard, as well as the role of PODE V2 holders within the platform in relation to governance and influence over the interoperability standard itself, the mechanics behind a indie game or mod gaining VLO status and select functions within the IMG as IMG members expand into PODE V2 holders.

As the deliberation progresses more suggestions and comments will be added to this thread.

For this, governance voting functionality will be added for PODE holders across these select proposals.


I think this is one of the most critical key concepts: interoperability, portability and transportability & automatic re-configurability across the various Metaverse’s, in much the same way as the OSI 7 Layer model and TCP/IP allows data packets to be ubiquitously shared across Data Networks, the Internet and Applications. The Open Source Gaming (OSG) model as outlined in the White Paper will be critical in the Terraforming of the Decentralised Metaverse, we are seeing Facebook throw there Huge resources behind “Meta” , Microsoft has now entered the ring with Metaversal enhancements to the Team’s platform. Many other commercial platforms will follow suit. Within the Ecosystem Architecture for PODE there should exist a code security analysis toolset for the dev team to perform static and dynamic code analysis, as Security Audits will be a central requirement especially if Smart contracts are being leveraged across Multi code Forked repositories. There should also be a mechanism for responsible disclosure for any discovered code vulnerability by the player ecosystem. This is a recommendation for future perceived complexity as the architecture becomes more of a inter connected Architectural membrane, security should be integrated where possible from the outset. I realise this has already been considered, so i am more reinforcing its importance; as this growth engine spins up, and it becomes more economically attractive. Open sourcing the code base ensures that its open for security audit and feedback, but also open for attackers to discover any perceived present/future weakness; so having a audit function built in as part of an incentive model could be useful.