> For the complete documentation index, see [llms.txt](https://aster-metaverse.gitbook.io/aster-metaverse/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://aster-metaverse.gitbook.io/aster-metaverse/project-architecture.md).

# 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="/files/IDThR0sjOIjGruAJ2I4P" 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.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://aster-metaverse.gitbook.io/aster-metaverse/project-architecture.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.