Optimistic Rollups
Transactions are aggregated and posted optimistically. Validity is presumed; fraud proofs are the watchful sentries posted along the colonnade. The challenge window — typically seven days — is a stretch of geological patience.
A contemplative archive of rollup, bridge, and consensus knowledge.
layer-2.wiki is a quiet observatory for those who study the second stratum of the chain — a place where the language of consensus is set in marble and the dials of finality glow softly behind veined alabaster.
This archive does not advertise. It does not advise. It is a reading room — a contemplative chamber in which the operations of rollups, bridges, and validity proofs are inscribed with the patience of monastic copyists. Each section is a stratum: a layer of stone laid down across years of protocol evolution, deeper than the last, cooler in temperature, more deliberate in syntax.
You may read at any pace. There is nothing to subscribe to. There is no urgency. The text is here, and so is the marble, and so is the slow-rotating gauge in the corner of your eye, monitoring nothing in particular, simply present.
Scaling is not a feature; it is sedimentation. Each layer is laid down upon the consensus bedrock below it, inheriting security as one inherits the weight of stone.
The base layer — what miners and validators secure with energy and capital — is the bedrock. Above it, layer two settles like a calcified accretion: cheaper transactions compressed into bundles, posted upward as proof or data, anchoring eventually into the eternal record below. The terminology of rollups, validiums, plasma, and state channels is, fundamentally, the geology of trust.
What follows is a non-exhaustive cross-section. The reader is encouraged to think of each entry as a stratum of fossilized assumption — a moment in time when a particular trust-minimization decision crystallized into protocol.
Transactions are aggregated and posted optimistically. Validity is presumed; fraud proofs are the watchful sentries posted along the colonnade. The challenge window — typically seven days — is a stretch of geological patience.
Each batch carries with it a succinct cryptographic proof — a sealed reliquary attesting to its own correctness. Finality is mathematical, not temporal; the stone is already cool by the time the seal is broken.
Data availability is delegated to a committee or hybrid scheme. The trust assumption shifts; the throughput rises. A bargain inscribed in pale terracotta veins.
Two parties agree to a private alcove of state, settling the colonnade only at the conclusion. Ancient in lineage, narrow in scope, beautiful in restraint.
Finality is the moment a block becomes irreversible — a stone set into the colonnade, never to be lifted. Different protocols approach this vow with different temperaments: some swift, some patient, some probabilistic.
To achieve consensus is to convince a sufficient quorum of validators that a particular ordering of events is the canonical history. This is, in the abstract, a problem of coordination among strangers — and the elegance of modern protocols lies in the way mathematics replaces the need for trust between them.
The vertical rule along the left edge of this chamber traces a single thread of thought: what does it mean for a transaction to be irrevocable? The answer differs across families of consensus, and the difference is the entire content of this section.
The rollup is, at heart, a method of compression — a way of folding many transactions into the single signature of a posted batch. Below, the lineage is laid out as a quiet field of stelae.
What separates one rollup family from another is the answer to two questions: where does data live?, and how is correctness asserted? From these two axes, an entire taxonomy unfolds.
A bridge is a Roman aqueduct in protocol form: it carries value from one stratum to another, supported by mathematical arches that must hold against the weight of the river of liquidity passing across them.
Bridge designs span a wide trust spectrum. At one end, the canonical bridge of a rollup inherits the security of its base layer — a keystone of stone. At the other, federated multisig bridges trust a small council of signers — wood, perhaps, or wattle. In between, light-client bridges, optimistic bridges, and zk-bridges propose elegant arches of varying height.
The reader is reminded: most bridge exploits in recorded protocol history have been failures of trust assumption, not of cryptography.
At the deepest stratum, the marble gives way to mathematics. Here are the polynomials, the elliptic curves, the Merkle trees — the bedrock upon which every layer above rests.
The ZK proof systems form a small constellation of named entities. Each carries a particular trade-off — proving time, verification cost, trusted-setup requirements, recursion friendliness. The reader is invited to consider them as instruments in an orchestra of correctness.
Tiny proofs (~200 bytes), fast verification, but a per-circuit trusted setup. The candle that burns brightest, briefly.
Universal trusted setup, programmable, recursion-friendly. A long-lived ceremony in a marble basilica.
No trusted setup, post-quantum candidate, larger proofs (~50 KB). The granite slab — heavy, durable, transparent.
Incrementally-verifiable computation through folding schemes — recursion as sediment, layered without a verifier in the loop.
This page is set entirely in living CSS marble. There are no raster images. There is no analytics. There is nothing to subscribe to. The reader is welcome.
The marble veining is generated through SVG turbulence and displacement filters layered over radial gradients. The fracture-line dividers wobble along bezier paths perturbed by fractal noise. The HUD pips, gauge arcs, and corner brackets are simple SVG primitives, animated with CSS keyframes at intentionally slow rates. Hover any card to feel the stone exhale.
— compiled in the marble archive, epoch 4,917