Skip to main content

​
Set L2 Compliance Proofs

Set L2 anchors proof metadata so clients can verify that a policy was satisfied for a batch of events.

​
Proof Metadata

Each batch commitment can include proof metadata:
  • proofHash: Hash of the proof artifact
  • policyHash: Hash of the policy definition
  • allCompliant: Boolean compliance flag

​
Verification Flow

  1. Fetch proof metadata from Set L2.
  2. Retrieve the proof artifact from your prover storage.
  3. Verify the proof locally against the policy inputs.
  4. Compare computed hash with the on-chain proofHash.

​
When to Use Compliance Proofs

  • Regulatory or policy compliance (AML, order caps)
  • Third-party verification requirements
  • Trust minimization across vendors