Contracts

The core of the protocol are the contracts, and in principle they work similarly to any blockchain bridge. Their main purposes are 1) to serve as a standardized registry of on-chain Metaverse domains and related oracles 2) to standardize binding on-chain assets to said domains 3) to provide a standardized interface for oracles to manage assets belonging to their domain and to register related events.

The protocol takes away the pain of having to implement all of these from scratch each time someone wants to meld a Metaverse with on-chain assets. It is a generic platform for everyone to build a Metaverse integration on.

When importing assets into a Metaverse or manifesting off-chain items through the bridge, the outcome is enforced by a ruling oracle of the domain. Such outcome will depend on factors such as the type of asset being bridged or the direction of the bridging. Bridge operations are executed by a whitelisted account belonging to an oracle, or by anyone sending a correct payload with an oracle’s signature on it. We identified 4+2 basic operations that are needed to support a Metaverse: import, irreversible import, export, summon, change owner and change beneficiary.