The underlay protocol used in MOSSAI and been changed to Hyperdust Protocol (Istanbul version)
Immersive experience is the key factor of a metaverse platform. Not every potential end user has a performance computer to render AAA photographic metaverse. The headset XR device often has limited 3D rendering capability. So for years , there have been some commercial cloud platforms that are providing real time cloud rendering services for gaming and other emerging markets, such as metaverses. But all these businesses leverage traditional business models. They prefer to be a service provider that sells shovels to the miners of new business builders rather than being part of the ecosystem and accepting the tokens of the metaverse platform.
In traditional business, metaverse/games need to pay the service to the cloud company with fiat or digital fiat/stable coin. So the computation power beneath cloud rendering is alway the cost of metaverse/games. The metaverse/games can never benefit from the network effects brought by its prospers. The cloud companies continue to get revenues from metaverse/games. In such circumstances, new businesses such as metaverse/ cloud games in the early stage have very little chance to prosper or even survive. That could be the reason why the successful web2 platform always has their own cloud service company. Amazon has AWS, Microsoft has Axure, Google has Google Cloud etc.
Although a few projects claimed they could provide cloud rendering service in web3 business model, i.e. tokenization of 3D rendering power. The absence of cloud real time rendering is still in the field. Only still scene or video offline rendering available in Web3 industry.
Decentralization of metaverse/games requires a more sustainable business model for massive aggregate computation, such as real time 3D/XR rendering to prosper.
The smart contracts of the MOSSAI are the core of the MOSSAI platform, containing the main functionalities of the platform.
-
MOSSAI_Free_Island_Mint.sol: The island minting contract, where users can mint islands at specified locations. -
MOSSAI_Island_Airdrop.sol: The island airdrop contract, responsible for configuring island airdrop activities, user airdrop collections, and other related business activities. -
MOSSAI_Island_Map.sol: The island location contract, responsible for storing the list of island locations. -
MOSSAI_Island_NFG.sol: The island NFG asset contract. -
MOSSAI_Island.sol: The island archive contract, managing all archival information for islands, such as names, sids, and Gym space state data. -
Island_721.sol: The exclusive ERC-721 asset contract assigned to users when they mint islands. -
Island_1155.sol: The exclusive ERC-1155 asset contract assigned to users when they mint islands. -
Island_Mint.sol: The island asset minting contract, responsible for the NFT token minting of all island asset contracts. -
Island721Factory.sol: The ERC-721 factory contract, responsible for deploying exclusive ERC-721 contracts for users. -
Island1155Factory.sol: The ERC-1155 factory contract, responsible for deploying exclusive ERC-1155 contracts for users. -
MOSSAI_mNFT_Mint.sol: The platform NFT minting contract, where users can mint official platform-issued NFT assets. -
MOSSAI_NFT_Product.sol: The NFT product contract, responsible for storing the information of NFTs listed by users in their own shops, such as selling price and quantity. -
MOSSAI_NFT_Transaction.sol: NFT trading contract, responsible for trading NFTs listed in the user's own store.