Skip to main content

Validator

Overview​

Protocol V2 validator worklow

As the snapshot submission batches are anchored on the protocol state by the sequencer, the validators become responsible for submitting their attestations on these batches.

State transitions​

Snapshot submission, validation and finalization state transitions

Batch submission​

When the sequencer submits a batch, it puts the snapshots contained within in a PENDING state on the protocol state. It also causes the emission of a SnapshotBatchSubmitted event.

info

Learn more:

Batch validation​

The finalized CID of every project ID committed by the sequencer in the PENDING state moves to a FINALIZED state when a majority of the validators submit their attestations on that finalization.

In the case where a majority of validators do not agree to the finalization, a resubmission workflow is triggered. This time, the validators work on re-creating the snapshots against the project IDs that did not reach consensus for finalization, and re-submit them to the protocol state to be resolved by the same consensus rules.

Trigger for batch validation​

For the current iteration of the Protocol V2 release, once the sequencer for a data market has finished committing all batches of submissions, it triggers an event release BatchSubmissionsCompleted from the protocol state smart contract that signals the validators to begin submitting their attestations.