Rollups
What are Rollups?
Rollups offer a model that offloads heavy computation and state storage from the host while relying on the host for security guarantees. Rollups achieve this by electing dedicated, often centralized, Sequencers who are responsible for aggregating transactions and producing blocks.
The popularity of Rollups inspired projects like Celestia to champion data availability as an independent service, offering a Tendermint-based storage layer for Rollup deployment.
Critical thinking: Celestia promotes itself as modular - but how does this work with Blockchain 101?
How does it work?
Just like Monoliths - builders deploy app code to 'contract' accounts that the Sequencer and full-nodes store, update state, execute transactions on, and verify. The app code is only the 'state-machine' logic, whereas the Rollup client handles peer-to-peer, and persistence β while the host protocol (Ethereum) handles Consensus and finality.
Pros & Cons of building on Rollups
The good:
β quick to market
β have immediate security
β have access to Ethereum's ecosystem and tooling
β have an easy framework to build
It's important not to overlook the features that make Ethereum so popular
The bad:
β compete for limited resources, favoring the highest bidder
β leak economics to Ethereum for life (fees, network effects, ecosystem lock-in)
β can't leave without starting over
β have limited scalability
β are success-capped with historically lower FDV than L1s
β can't natively communicate with external ecosystems
are not decentralized relying on the host for:
β governance
β transaction execution
β state updates
β blockchain storage
Which means:
β can be censored by non-stakeholders
β are controlled by the host
β lack autonomy
β have single points of failure
A "not so" decentralized app is just Web2 with an inefficient and complicated architecture
Canopy and Rollups Comparison
Architecture
β Peer-to-Peer
β Layered on a Monolith
Scaling Method
β Every new chain horizontally scales Web3
β Semi-centralized layers
Builder Sovereignty
β Progressive
β Critical, lifelong reliance on host for security, finality, and blockchain storage
Ecosystem
β New
β The best
Long range attack
β Proof of Age
β Checkpoint on Ethereum
Builder Difficulty
β Quick to market
β Quick to market
Builder Economic Security
β Immediate
β Immediate
Builder Framework
β Fork & Clone: Golang
β Standards with DSL (Solidity)
Chain Resources
β Exponential: Each new chain is additive
β Limited: host single chain
Builder Success
β L0 Premium
β Typically lower FDV than sovereign L1s
Native Interoperability
β Permissionless
βWithin Ecosystem
Builder Decentralization
β Full/Progressive
β Not decentralized
Last updated