Skip to main content

About Set L2 architecture

This explanation covers how Set L2 stores commitments and enables verification across systems. Set L2 anchors batch commitments and proof metadata on-chain so clients can verify inclusion and compliance without trusting the sequencer.

How Set L2 works

  • The sequencer orders events and computes Merkle roots.
  • The prover generates compliance proofs.
  • SetRegistry stores the batch commitment and proof hashes.
  • Verifiers recompute and compare proofs locally.

Why this design

On-chain anchoring makes the chain the source of truth and allows independent verification.

When to use this approach

  • Audit trails: When you need tamper-evident event history
  • Compliance: When policies must be provable to third parties
  • Trust minimization: When parties do not trust the sequencer

Relationship to other features

Set L2 is part of the VES flow with the sequencer and verifier clients.

Further reading