Skip to main content

Introduction

Mo Chain is a BSC-compatible Layer-1 built by forking bnb-chain/bsc v1.7.3. It uses Parlia PoSA consensus with BLS fast finality and targets a ~450 ms block time.

Network Name
Mo Chain Testnet
Chain ID
6688 (0x1a20)
Currency Symbol
MO
RPC URL
https://rpc-testnet.mo.fit
WebSocket
wss://wss-testnet.mo.fit
Block Explorer
https://scan-testnet.mo.fit

Why another BSC-style chain

  • EVM + BSC tooling out of the box — anything that runs on BSC (MetaMask, Hardhat, Foundry, ethers/viem, Uniswap forks, subgraphs) runs here with only a chain-config change.
  • Fast blocks — sub-second blocks for responsive dApps.
  • Full DeFi stack pre-deployed — Multicall3 at the canonical address, Uniswap V2 + V3, wrapped native (WMO), stablecoins, a bridge, and ENS-style .mo naming.

Relationship to BSC

AspectMo ChainBSC mainnet
Clientbnb-chain/bsc v1.7.3 forksame lineage
ConsensusParlia PoSA + BLS finalityParlia PoSA + BLS finality
System contractsbsc-genesis-contract v1.2.5same family
Block time~450 ms~750 ms–3 s
Native coinMOBNB
Multicall3canonical 0xcA11…CA11canonical 0xcA11…CA11

Because we follow the upstream path (standard fork order, standard contracts), tooling that hard-codes BSC behavior generally just works.

Roadmap

  • Now (Testnet) — public RPC, explorer, faucet, DEX, bridge, wallet onboarding, ENS, dev portal.
  • Graduate — multisig + timelock on all owners, audit package, synthetic monitoring, validator onboarding.
  • Mainnet — production validator set, liquid staking, hardened bridge (N-of-M).

Next steps

  • Quick Start — add the network and send your first transaction in minutes.
  • Architecture — how the chain, apps, and gateway fit together.