Chapter 1 • Masterchain & Sharding
The Architecture
Forget everything you know about blockchain architecture. Ethereum has one chain. Solana has one chain. TON has... infinite chains.
This isn't marketing speak. TON was designed from day one to scale horizontally without limit. The secret? A multi-chain architecture where the number of chains can grow dynamically based on load.
The TON Structure
Masterchain (Chain 0) The brain. Stores validator info, shard configs, and references to all workchains. Workchains (up to 2³² possible) Application chains. Currently only Workchain 0 (the "basechain") is active. Each can have custom rules, VMs, and token standards. Shardchains (dynamic) Workchains split into shards when load increases. Each shard processes a subset of accounts. Shards can split (2→4) or merge (4→2) automatically.
Understanding the Layers
The Masterchain is TON's "chain of chains." It doesn't process user transactions — it coordinates everything else.
What the Masterchain stores:
• **Validator set** — Who validates blocks this epoch
• **Shard configuration** — Which shards exist in each workchain
• **Block references** — Hashes of latest blocks from all shards
Think of it as the "routing table" for the entire network. Every 5 seconds, a new masterchain block finalizes the state of all other chains.
1
Masterchain
Coordination layer
2³²
Max Workchains
4+ billion possible
1
Active Workchain
Workchain 0 (base)
Auto
Shard Split/Merge
Dynamic scaling
ELI5 Version: Imagine a highway system. The Masterchain is the map showing all roads. Workchains are different highways (currently just one). Shardchains are lanes that can multiply when traffic increases. TON adds lanes automatically — no construction needed.
📝 Quick Check