Architecture
Mo Chain separates the chain layer (consensus + RPC), the application layer (explorer, faucet, DEX, bridge, wallet portal, ENS), and the gateway (TLS + routing).
Component map
Chain layer (two tiers)
- Validators — seal blocks only. They never expose public RPC (
8545/8546stays closed on validators). - RPC nodes — serve all external traffic. At least one runs in
--gcmode=archiveso the explorer can trace historical transactions (debug_traceTransaction).
This split decouples security (validators) from availability/performance (RPC).
Application layer
| Service | Purpose |
|---|---|
| Blockscout | Block explorer + contract verification |
| Faucet | Test MO + stablecoin distribution |
| Swap UI | Uniswap V2/V3 swap, liquidity, pools |
| Wallet UI | One-click add network / tokens, wallet guides |
| Bridge UI | BSC ↔ Mo transfers |
| ENS UI | .mo name registration |
| Dev Portal | This documentation site |
Gateway
A reverse proxy terminates TLS and routes each subdomain (rpc-, scan-, faucet-, swap-, wallet-, bridge-, docs-testnet.…) to the right upstream. RPC nodes are rate-limited and method-filtered at this layer.
Contracts (post-genesis)
System contracts are baked into genesis (BSC standard). Application contracts (Multicall3, WMO, stablecoins, DEX, bridge, ENS) are deployed afterward:
| Contract | Address | Explorer |
|---|---|---|
| Multicall3 | 0xcA11bde05977b3631167028862bE2a173976CA11 | view ↗ |
Next steps
- Chain Specs — exact parameters.
- RPC API — endpoints and limits.