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
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.
Last updated