layer-2.id

Identity on the execution layer. Decentralized. Sovereign. Immutable.

STATUS: ONLINE
_
PROTOCOL

Layer-2 identity exists in the space between chains. Not on Layer 1, which is too expensive. Not on a centralized server, which is too fragile. In the rollup, where cost meets sovereignty.

EPOCH

BLOCK: 19,847,203

GAS: 12 GWEI

SYNC: 99.7%
INFRASTRUCTURE

The Protocol

Identity is not a database entry. It is a cryptographic commitment -- a zero-knowledge proof that you are who you claim to be, without revealing anything more than necessary. The protocol ensures that identity is self-sovereign: you hold the keys, you control the attestations, you decide what is disclosed.

HASH REGISTRY

0x7f3a...b4c2

0xa1e8...9d3f

0xc4b7...2e1a

0x8d2f...6a8c

$ l2id verify --zk
> Proof valid
> Identity: confirmed
> Gas used: 21,000
DID:L2:001

ACTIVE

DID:L2:002

PENDING

DID:L2:003

ACTIVE

DID:L2:004

REVOKED

The Ledger

Every identity operation is recorded. Issuance, verification, revocation -- each state transition is a transaction, each transaction is a proof, each proof is a permanent mark on the shared state.

ATTESTATION

VERIFIED

DID:L2:005

ACTIVE

DID:L2:006

ACTIVE

IDENTITY CARD

LAYER-2.ID

ISSUED: 2026

STATUS: VALID

The Signature

What cold infrastructure produces is something warm: an identity. Not a username, not an email, not a cookie. A cryptographic self -- portable, private, provably yours. layer-2.id is where that self is minted.

layer-2.id

ENCRYPTED SIG

Ed25519::VALID