Skip navigation
XChain Docs

2 · Design Principles

Last updated: 08/06/20261 min read

XChain's design follows from one principle and six corollaries. The principle is verify, don't re-execute: an upper layer confirms a proof that a lower layer did its work correctly, rather than re-running it. This is what makes planetary scale thinkable.

#PrincipleWhat it means
1Aggregate, not globalLarge capacity is aggregate nominal throughput, never one synchronous global state.
2Locality-firstOver 99% of activity should stay local; placing state correctly is job one.
3Assurance ∝ valueA transaction's security, data availability and proof scale with what it is worth.
4Verify, don't re-executeThe layer above checks an aggregated proof instead of re-running the work.
5A narrow waistThe core stays small and hard-defined; the space to build above it is unbounded.
6Prune by defaultLow-value data expires; only the commitment is permanent; every chain pays its own way.

Takeaway: every corollary serves one goal — let most of the world's volume travel a near-free path, while value and atomicity concentrate in the small, most-protected core. Scale and safety stop fighting each other.