Oracles

Oracles are always necessary wherever the on-chain and off-chain world meets as trusted intermediaries. The Multiverse Bridge relies on oracles to insert an interpretation layer in-between the Metaverse and the on-chain protocol. Oracles can handle all the data and logic required to enable the cross-layer utility of the assets. Information such as a) the list of imported assets by a particular user, b) the effects of the assets in-game and c) behaviors such as what to do with an asset once it crosses the Multiverse Bridge, are all stored and pre-programmed by an oracle, e.g. a backend. Though centralized services, trusted middleman and single point of failures are generally frowned upon in the web3 world and their usage is best avoided, in case of e.g. a complex multi-player game which cannot run on the chain it is unavoidable. This is often the case for Metaverses, where e.g. a game server acts as the single source of truth aka. the trusted oracle. Nevertheless, should the Metaverse be on-chain or off-chain, the Multiverse Bridge protocol supports it.

The Multiverse Bridge is completely Metaverse agnostic. It is capable of connecting any Metaverse, provided the right oracle configuration. Said differently, any game/app will need its own customized implementation of an oracle to leverage the Multiverse. Interpretation of Multiverse Bridge events might differ depending on the Metaverse’s needs defined by its unique characteristics and mechanics, therefore it’s hard to generalize it with a single protocol. The Multiverse Bridge standardizes a Metaverse oracle’s relationship with the on-chain world, without imposing strong opinions or limitations on it.

Fig. 3. Oracle in an example config