Community-maintained encyclopedia
Browse rollups, validity proofs, data-availability layers, and the application stack on top of them — each concept rendered as an isometric block in a connected, readable graph.
Knowledge modules
Optimistic rollups assume execution is valid by default and rely on a fraud-proof window. Read how the seven-day challenge period shapes UX, withdrawals, and bridge design.
A ZK rollup posts a succinct cryptographic proof to L1 that a batch of L2 transactions is valid. No challenge window — finality follows the proof.
A schematic of the responsibilities a base layer takes on: ordering, consensus, and publishing data so any honest party can reconstruct state.
A walkthrough of canonical vs. third-party bridges, the message-passing primitives behind them, and the trust assumptions they introduce.
A node responsible for ordering and pre-confirming L2 transactions before they are batched and committed to L1. Centralised today, decentralising over time.
The guarantee that block data has been published so anyone can download and verify it. Without DA, validity proofs lose meaning — you can prove a state nobody can see.
Three blocks tell the story: a user transaction submitted to the sequencer, a batch produced, and a commitment landing on L1.
Smart-contract wallets, sponsored gas, and session keys reshape what a user-facing dApp can offer once accounts are no longer constrained by EOAs.
Protocol catalogue
A subset — full catalogue lives under /protocols.
Glossary index
Click a term to jump to its full entry.
Contribute
Edits are submitted as pull requests against git@layer2.wiki:wiki.git. Diagrams ship as inline SVG. Articles are plain Markdown with a small set of front-matter fields.