Module types 

Types used by the prover

Structs

AirProofRawInput

Raw input for proving a single AIR. For DEBUG use only.

AirProvingContext

Necessary context for proving a single AIR. Consists of the trace and public values (witness and instance data) as well as cached prover data from cached traces (already committed traces).

AirView

A view of just the AIR, without any preprocessed or after challenge columns. The AIR’s main trace is horizontally partitioned into multiple matrices, where each matrix can belong to a separate matrix commitment.

CommittedTraceData

Commitment to a single trace matrix, together with the trace matrix and prover data.

DeviceMultiStarkProvingKey

The proving key for a circuit consisting of multiple AIRs, after prover-specific data has been transferred to device. The host data (e.g., vkey) is owned by this struct.

DeviceMultiStarkProvingKeyView

A view of the proving key after it has been transferred to device. The view is filtered for only the proving keys corresponding to specific air_ids.

DeviceStarkProvingKey

The proving key after prover-specific data has been transferred to device. The host data (e.g., vkey) is owned by this struct.

HalProof

The full proof for multiple RAPs where trace matrices are committed into multiple commitments, where each commitment is multi-matrix.

PairView

ProverDataAfterRapPhases

ProvingContext

RapSinglePhaseView

RapView

The full RAP trace consists of horizontal concatenation of multiple matrices of the same height:

SingleCommitPreimage

A view of an already committed trace, together with a reference to the preimage of the commitment.