Modular vs Monolithic Blockchains
The biggest architectural debate in blockchain design: should one chain do everything, or should the jobs be split across specialised layers? What 'modular' and 'monolithic' really mean, and their trade-offs.
Four Jobs Every Blockchain Does
Under the hood, every blockchain performs a few distinct jobs. Execution: running the transactions and computing the new state. Settlement: providing a final, agreed record and resolving disputes. Consensus: agreeing on the order of transactions. Data availability: making sure the transaction data is actually published so anyone can check it. A monolithic blockchain does all of these jobs itself, in one integrated system — Bitcoin and (historically) most single chains work this way. A modular blockchain instead splits these jobs across specialised layers, each optimised for its task, that work together. This 'do it all yourself' versus 'divide the labour' choice is one of the deepest architectural debates in the space.
Why Split Things Up?
The modular argument is essentially specialisation and scalability. A single chain trying to do everything faces hard limits: making execution faster can raise hardware requirements and hurt decentralisation, and every node must handle every job. By separating concerns — for example, letting rollups handle execution while a base layer handles settlement and consensus, and a dedicated layer handles data availability — each part can be optimised and scaled independently, and many execution layers (rollups) can share one secure base. The monolithic counter-argument is that integration is simpler, avoids the complexity and new trust assumptions of stitching layers together, and can offer tight performance and a unified experience. Neither is universally 'better'; they optimise for different things.
- Blockchains do four jobs: execution, settlement, consensus, data availability
- Monolithic chains do all jobs themselves in one integrated system (e.g. Bitcoin)
- Modular chains split the jobs across specialised, cooperating layers
- Modular = specialisation and shared security; monolithic = simplicity and integration
Key Takeaways
- Every chain handles execution, settlement, consensus, and data availability
- Monolithic does it all in one; modular divides the work across layers
- The debate is specialisation/scalability vs simplicity/integration — not one 'winner'
Related Content
More Topics
Browse all 179 topicsFormal Verification of Smart Contracts
Mathematically proving a smart contract does what it should — how formal verification differs from testing and auditing, what it can and can't guarantee, and why it isn't a silver bullet.
Censorship Resistance & Inclusion Lists
Can a blockchain be forced to ignore your transaction? How block-building centralisation created a censorship risk, and how inclusion lists (like FOCIL) aim to guarantee that valid transactions get in.
Proof of Personhood
How do you prove there's a unique human behind an account without a government ID? The approaches — biometrics, social graphs, in-person events — and the privacy and centralisation trade-offs each makes.
On-Chain Identity & Attestations
Portable, user-controlled reputation and credentials built from verifiable attestations — how attestations, verifiable credentials, and soulbound tokens work, and the privacy tensions of putting identity on a public ledger.
Single-Slot Finality
Why finality on proof-of-stake Ethereum takes about 15 minutes today, why that's a problem, and how single-slot finality aims to make transactions irreversible within one slot — plus the hard trade-offs.
Light Clients & Sync Committees
How a phone or a smart contract can verify the blockchain without downloading all of it — light clients, Ethereum's sync committees, and why trust-minimised light verification underpins bridges and decentralisation.
Secure Multi-Party Computation (MPC)
How several parties can jointly compute a result over their private inputs without any of them revealing those inputs — the cryptography behind MPC wallets, private data collaboration, and threshold systems.
Verifiable Secret Sharing & DKG
How to split a secret so no single party holds it, prove the shares are valid, and even generate a key that never existed in one place — the backbone of threshold wallets, validators, and decentralised custody.
References & further reading
- primaryCelestia — Monolithic vs Modular Blockchains
A modular-DA project's explainer of the two architectures.
archived copy ↗