layer-2.wiki

The Underneath

Beneath every system lies another system. Beneath every truth, a second truth that the first one rests upon, the way a cathedral rests on crypts that predate it by centuries. Layer 2 is the name we give to this architectural confession: that the visible surface is never the whole story, that every protocol, every agreement, every handshake between machines is supported by invisible scaffolding that most users will never see and would not understand if they did.

The wiki records what the surface cannot. Here, in the margins of the known, we annotate the unspoken — the gas costs, the finality windows, the merkle proofs that hold the bridge between what is claimed and what is true. Every entry is an act of excavation: digging through layers of abstraction to find the bedrock underneath.

Some entries here contradict each other. This is by design. The second layer is not a place of consensus but of dissent — a ledger of disagreements that the first layer smooths over in its pursuit of finality. To read this wiki is to accept that knowledge is stratified, that what you know depends on which layer you are standing on.

Substrates

A substrate is the thing beneath the thing. In biology, it is the surface on which an organism grows. In computing, it is the hardware beneath the software. In this wiki, the substrate is the question itself: what holds up the layer that holds up the layer that holds up the world you interact with every day when you send a message, transfer a token, or sign a transaction?

The answer, like all answers in this encyclopedia, is provisional. The substrate shifts. What was bedrock yesterday becomes sediment tomorrow. The only constant is the layering itself — the principle that complexity is managed by abstraction, and that every abstraction introduces a new surface that will eventually need its own wiki entry.

Consider the state root: a single hash that claims to represent the entirety of a system's state at a given moment. The substrate beneath the state root is the trie structure. Beneath the trie is the key-value store. Beneath that, the filesystem. Beneath that, the disk sectors. At every layer, a different truth is told, and at every layer, the previous truth becomes a substrate for the next.

The Bridge

A bridge in blockchain terminology is the mechanism that allows assets to move between Layer 1 and Layer 2. But a bridge is also a metaphor, and metaphors in this wiki tend to be load-bearing. The bridge connects the heavy, slow, trustworthy settlement layer to the light, fast, probabilistic execution layer. It is the most vulnerable point in the system — the place where trust must be actively maintained rather than passively inherited.

Every bridge is a promise. The Layer 2 promises that it will faithfully report its state to Layer 1. Layer 1 promises that it will enforce the rules even when the bridge operator disappears. The user promises to wait for finality before assuming safety. These promises interlock like the stones of an actual bridge, each one bearing weight that it passes to the next.

The history of bridges is a history of failures. Not because the engineering was wrong, but because the promises were too ambitious. A bridge that tries to be trustless must still trust the validator set. A bridge that tries to be instant must still wait for the challenge period. Every bridge is a compromise between what is desired and what is possible, and this wiki exists to document those compromises with unflinching honesty.

Finality

In distributed systems, finality is the moment when a transaction can no longer be reversed. It is the point of no return, the instant when the probabilistic becomes the definite. Different protocols define finality differently — some in seconds, others in hours, others never quite reaching absolute certainty but approaching it asymptotically, like a curve that forever nears a line without touching it.

This wiki, too, approaches finality without achieving it. Each entry is provisional, each definition subject to revision. The knowledge here is alive in the way that all genuine knowledge is alive — perpetually incomplete, perpetually reaching toward a truth that moves as fast as the seeker. The second layer is not a destination. It is a direction.

There is a philosophical dimension to finality that the technical literature rarely acknowledges. When we say a transaction is final, we are making a claim about the nature of time itself: that there exists a moment after which the past becomes immutable. But in a system of layers, finality on one layer does not guarantee finality on another. The challenge window exists precisely because Layer 2 finality is always conditional — final until proven otherwise.

The Proof

A proof, in the context of Layer 2, is a mathematical argument that a set of state transitions was executed correctly. The proof does not reveal the transitions themselves — only that they happened according to the rules. This is the essential magic of zero-knowledge: the ability to demonstrate truth without disclosing the facts that make it true.

The prover constructs an artifact — a small piece of data, insignificant in size but monumental in implication — and submits it to the verifier on Layer 1. The verifier checks the proof in milliseconds, confirming what took the prover hours to compute. This asymmetry is the foundation of scaling: the cost of verification must always be less than the cost of execution.

But what does it mean to prove something without showing your work? In mathematics, proof has always meant transparency — the step-by-step demonstration that any reader can follow. In cryptography, proof means the opposite: conviction without comprehension, certainty without sight. This wiki holds both definitions in tension, refusing to choose between them, because the second layer is precisely the space where such contradictions are permitted to coexist.

Rollback

A rollback is the undoing of what was thought to be done. In traditional databases, it is a controlled operation — the system restores a previous state, and the aborted transaction is cleanly erased. In Layer 2 systems, a rollback is something more existential. It is the discovery that the recent past was a fiction, that the state everyone believed in was constructed on a lie, and that the system must now retreat to the last point of honest agreement.

The fraud proof triggers the rollback. Someone — the watcher, the challenger, the honest minority — submits evidence that the sequencer lied. The bridge contract examines the evidence. If the proof is valid, the lie is unwound: transactions are reversed, balances are restored, and the sequencer is punished. The system heals, but the scar remains in the form of a delay that all future users must endure.

This wiki has been rolled back seventeen times. Each time, an entry was found to contain a claim that could not be substantiated by the layer beneath it. Each time, the entry was reverted to its previous version, and a marginal note was added: revised after challenge. These notes accumulate like geological strata, each one a record of a truth that was tried and found wanting. The wiki grows not by addition alone, but by the slow accretion of corrections — knowledge refined through the removal of error.