> For the complete documentation index, see [llms.txt](https://whitepaper.moouniverse.fun/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.moouniverse.fun/technical-overview/technical-architecture.md).

# Technical Architecture

**On‑chain layer (BNB Chain)**

* **Network:** BSC Mainnet (chain id 56).
* **Standards:** ERC‑721 (NFT), ERC‑20 ($MOO).
* **Audited contracts:**
  * **ERC‑721 Drop — Mooverse:** Minting and basic admin.
  * **ERC‑721 Staking:** Per‑second accrual, free claim, penalty‑free withdrawal.
  * **Marketplace:** Listings and buy/sell **exclusively in $MOO**.
  * **$MOO (ERC‑20):** Utility token used for payments/rewards in the ecosystem.
* **Metadata & media:** Decentralized storage on **IPFS** (NFT JSON + images).

**dApp / Web layer**

* **Frontend:** **Next.js 13 + React** with **Chakra UI**.
* **Web3 SDK:** **thirdweb** (React hooks and components like `MediaRenderer`, `useActiveAccount`, etc.).
* **Wallet connection:** EVM wallets via thirdweb (injected, WalletConnect, etc.).
* **Rendering & deploy:** SSR/ISR on a VPS with **PM2** and **Nginx** as reverse proxy.
* **RPC provider:** BSC endpoints (with fallback) managed via thirdweb client.

**Games layer (Moo Arcade)**

* **Client engine:** **Phaser** (web).
* **NFT gating:** On‑chain reads and player session signatures; holders only.
* **Rarity perks:** Multipliers/benefits enforced in the client and validated in the rankings server.
* **Leaderboards & prizes:** Weekly tables (Top 3) managed off‑chain with **signatures/nonces**; payouts in **$MOO** as per published rules.

**On‑chain AI layer**

* **Data ingestion:** Indexing BNB token activity (new deployments, liquidity pools, trades, holder distribution, and transfers).
* **Analysis modules:** Scoring/alerts for the community.
* **Access control:** NFT ownership/rarity gating (Epic/Legendary full access).
* **Surfaces:** Web dashboard and **Telegram** integration.

**Summary flow**

1. **Mint** (Mooverse) → 2) **Stake** (optional, real‑time $MOO accrual) → 3) **Claim** $MOO anytime → 4) **Marketplace** (list/buy/sell in $MOO) → 5) **Arcade** (NFT‑gated play with rarity multipliers) → 6) **Leaderboards & prizes**.

**Extensibility (future collections)**

* Ready to **add new collections** (own or partner) reusing the same utilities — staking, marketplace, arcade — without disruptive changes.


---

# 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://whitepaper.moouniverse.fun/technical-overview/technical-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.