Batched execution settles thousands of operations into a single finality proof.
Looking at infrastructure from the side reveals what sits flush against what. The diagonal here is not stylistic — it is an inspection line, the angle along which two dimensions meet so neither dominates. Above the line: topology, the geometry of who-talks-to-whom. Below the line: the prose that explains why the geometry is shaped this way.
Each settlement node maintains a Merkle-root pointer to the consensus layer beneath. Identifiers live at the core; certificates fan outward. The mesh is intentionally dense, because redundancy is the cheapest insurance in a system where finality is forever.
Read this section the way you would read a specification sheet: slowly, and with a pencil in your hand.
Batched execution settles thousands of operations into a single finality proof.
A persistent .id rooted in cryptographic biography, portable across protocols.
Settlement is anchored to L1 consensus — provable, durable, irreversible.
Speaks to neighboring layers through standardized message envelopes.
Keys remain with their holder; the protocol only records consent and proof.
Per-operation cost descends as utilization rises — economies of scale, on-chain.
Infrastructure is the skeleton, but the body is identity. The dot-id is not a username; it is a coordinate — the point where a particular person, organization, or instrument intersects with a verifiable history. We build the protocol so that this coordinate is yours to hold, not ours to license.
A fingerprint is unique because it is yours alone, but it is meaningful only when it is read. Layer 2 is the reader — the stratum that takes the unique mark and gives it a place to act. The ridges of biometric individuality and the orthogonal traces of digital infrastructure share the same goal: to say, with as little ambiguity as the medium allows, this is who, and this is where.
— layer2.id, drafted in vellum and code