# Project Architecture

**Project Architecture:**

The AsteR Metaverse project protocol is composed of three layers:

1. **Consensus Layer:**\
   This layer tracks asset ownership and content. Asset ownership is established using a hash of the file’s content. The file includes descriptions of sounds, objects, textures, and other elements required to render the game scene. It also contains a URL to coordinate peer-to-peer (P2P) connections.
2. **Asset Content Layer:**\
   This layer allows for the decentralized downloading of assets, facilitating content distribution without a centralized system.

These layers work together to ensure smooth gameplay and decentralized content management in the AsteR Metaverse.

<figure><img src="https://3540385451-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fe14zB8q2TKmR3yKJSBs2%2Fuploads%2FFEJvMzBJgBz4kFlVUsWe%2F5.png?alt=media&#x26;token=c5dde9d2-6c28-4d47-b6f2-a44814c70e9d" alt=""><figcaption></figcaption></figure>

**Consensus Layer:**\
The AsteR Metaverse utilizes the Binance Smart Chain and smart contracts to maintain a ledger of asset ownership. Each asset has unique (x, y) coordinates, an owner, and a reference to a content description file that encodes the owner’s intended use of the in-game assets.

**Content Distribution Layer:**\
The AsteR Metaverse employs a decentralized storage protocol to distribute the content required for rendering the metaverse. For each rendered parcel, a reference to the content file is retrieved from the smart contract. This decentralized system operates without a centralized infrastructure, with the cost of hosting and bandwidth currently borne by users. In the future, the project aims to implement a cost distribution model.

**Real-time Layer:**\
Users in the AsteR Metaverse can communicate through peer-to-peer (P2P) connections facilitated by servers hosted by asset owners and third parties. These P2P connections are essential for social interactions in the absence of a centralized structure. Asset owners will provide rendezvous servers to coordinate user connections.