Layer-2 protocols that execute transactions outside Ethereum Mainnet and post data and settlement information to Ethereum under a protocol-specific security model.
Supports: Defines rollups as off-L1 execution with data posted to L1 and distinguishes optimistic from ZK security models.
Supports: Documents challenge periods, data publication, sequencer risks, direct L1 paths, and protocol-specific exit mechanics.
Supports: Documents validity proofs, onchain contracts, state-data availability, and ZK withdrawal mechanics.
Supports: Explains why rollup data availability matters and the limited availability period for blobs.
Rollups batch off-Mainnet execution and publish data and settlement information to Ethereum under a specific design
Optimistic designs use a challenge process; ZK designs use validity proofs, but timing and exit rules vary by protocol
Data availability, bridge contracts, sequencer behavior, and upgrade controls are part of the user risk model
A rollup label or fast interface confirmation does not prove universal security, finality, or a completed Mainnet withdrawal
Before bridging funds, a user identifies the exact rollup and official bridge, reads the current exit rules and upgrade controls, and records the fee quote and withdrawal path. An interface confirmation is treated as local execution feedback; it is not treated as proof that funds have finalized on Ethereum Mainnet.
Assurance that data needed for a specified verification process was published and can be accessed under that system's rules. It is distinct from permanent historical retrievability.
A node in a Rollup (L2) responsible for ordering transactions before they are batched and sent to the L1 (Ethereum).
A cryptographic proof that a defined statement or computation satisfies a protocol without disclosing the witness beyond what that protocol reveals. It is not, by itself, a privacy or performance guarantee for an application.
A blockchain's own consensus and settlement layer. The label describes where that protocol processes and orders transactions; security, finality, data availability, and scaling guarantees differ by chain and design.
A protocol layer that executes transactions outside an L1 while using that L1 for some combination of data availability, proofs, dispute resolution, or settlement. Fees, finality, bridges, and withdrawal paths depend on the specific L2 design.
Explore all our strategic guides about Blockchain to take your operations to the next level.
View all articles