Process Flow

  1. A ZK project lists its proof task parameters (backend, latency, reward pool, etc.) on the Proverium chain.

  2. This task is recorded as a transaction.

  3. Provers, selected based on reputation and availability, compute the task and store the proof on a Proof Data Availability (DA) layer. A transaction tracks this status.

  4. Validators are chosen to verify the proof.

  5. Once a verification threshold is met, the task is marked as complete. The ZK project can then access the proof and its associated data.

PreviousWorkflow & ParticipantsNextConsensus Mechanism

Last updated