Skip to main content StateSet Set L2 Set L2 is the anchoring layer for verifiable commerce events. It stores batch commitments and proof metadata so any party can verify event inclusion, policy compliance, and state transitions.
What Set L2 Provides
On-chain batch commitments for sequenced events
Proof anchoring for compliance and policy verification
Public verification for inclusion and state transitions
Components
SetRegistry : Stores batch commitments and proof metadataAnchor service : Submits commitments and proofs on-chainVerifier clients : Validate inclusion and compliance
Data Flow
Sequencer batches events into a Merkle tree.
Proofs are generated for policy compliance.
Commitments and proof hashes are anchored on Set L2.
Verifiers confirm inclusion and policy compliance.
When to Use Set L2
Auditing event trails across systems
Verifying compliance against policy limits
Ensuring ordering and integrity of commerce events
Core Contracts Set L2 exposes a registry contract that accepts commitments from the sequencer and proof system. The registry stores metadata that can be used to verify event inclusion and policy compliance without trusting the sequencer or the proving service.
SetRegistry Responsibilities
Store batch commitments for event sequences
Store proof metadata for policy compliance
Provide inclusion verification for external verifiers
How It Fits Together
Events are sequenced by the StateSet Sequencer.
The sequencer commits batch roots to Set L2.
Proofs are generated and anchored for policy compliance.
External verifiers can confirm inclusion and compliance on-chain.
Getting Started If you are evaluating the full VES stack, start with the sequencer overview and demo to understand how events are captured and committed.
