SP1: A ZK virtual machine (zkVM) built by Succinct that can generate a proof of the correct execution of any program. To read more about SP1, see the SP1 docs.
Succinct Prover Network: A two-sided marketplace for ZK proofs that connects requesters and provers, implemented as a protocol that settles to Ethereum. Requesters submit SP1 programs to the network, and provers compete to generate proofs of the programs' execution.
Requester: An application that requests and receives ZK proofs from the Succinct Prover Network.
Prover: A participant in the network that generates ZK proofs using hardware like GPUs, ASICs, and more.
PROVE: The native token of the network, which enables payments, secures the network via staking and governance, and incentivizes provers.
Proof request: A request for a ZK proof of a program, containing:
The program to be proven, along with the program's inputs
Maximum prover gas units (the amount of work the request takes to complete)
The maximum PROVE fee the requester is willing to pay
The minimum amount of PROVE stake the request requires
The proof's deadline
A verification key that can be used to verify the proof
Proof contest: An auction mechanism for allocating requests to the most efficient provers that uses staking to prevent griefing and missed proof deadlines.
PROVE staking: A mechanism that asks provers or their delegates to stake PROVE to be eligible to participate in proof contests and fulfill proofs. Staking protects requesters against missed proofs and lets delegates who stake to provers earn rewards for their participation. PROVE staking is implemented via a nested vault structure that allows stakers to earn rewards from the network.
Auctioneer service: An off-chain service that coordinates requests, auctions, and proof fulfillments and settles ZK proofs of correct execution to Ethereum.