Skip to main content

StateCommitment

StateCommitment anchors sequencer state to chain through publisher-signed checkpoints.

Responsibilities​

  • Accept checkpoint updates.
  • Enforce publisher quorum.
  • Store state and withdrawal roots.
  • Support root lookup for verification.
  • Provide emergency controls for unsafe conditions.

Publisher quorum​

The current design uses a 7-of-10 publisher quorum. This reduces single-key risk while keeping operational publishing practical.

Checkpoint contents​

A checkpoint may include:

  • batch or epoch id,
  • state root,
  • withdrawal root,
  • metadata hash,
  • publisher signatures,
  • timing metadata.

Verification path​

Users and indexers should be able to verify:

  1. The checkpoint exists on-chain.
  2. It was signed by a valid quorum.
  3. A withdrawal proof matches the committed withdrawal root.
  4. The vault accepts the proof for execution.

Test surface​

State commitment behavior is validated across quorum thresholds, duplicate signatures, invalid signers, stale checkpoints, root lookup, emergency controls, and proof-verification integration with the custody layer.