Platform
A program for the zkVM
The developer compiles a program for RISC-V. SP1 produces a proof of execution that can be verified independently.
Your ecosystem guide / Succinct
Succinct: ZK proofs and the PROVE token
Succinct builds ZK proving tools and a proof marketplace. SP1 proves program execution; the Prover Network connects requesters with hardware operators. Protocol contracts settle on Ethereum, with PROVE used for payments and staking.
- Platform type
- ZK proof marketplace
- Verified on 19.10.2026
- Settlement layer
- Ethereum contracts
- Verified on 19.10.2026
- Token
- PROVE · payments and staking
- Verified on 19.10.2026
Succinct
All sections
Program, proof and PROVE
A developer requests computation; a prover supplies the result and its proof.
Payment and economic security
An ERC-20 on Ethereum. Requesters pay for proofs; provers stake to participate in proof contests.
A share in a prover vault
A deposit passes through iPROVE into the selected prover’s vault. stPROVE represents the depositor’s share in that vault.
Operation lifecycle
Three roles in the proving network
Requesting proofs, generating them and delegating capital are separate ways to participate.
Proof requester
- 01Program and inputs
- 02Prover auction
- 03Proof and payment
A request specifies a deadline, maximum PROVE fee and stake requirements. Funds are escrowed; payment is distributed after fulfilment.
How it works ↗Hardware operator
- 01PROVE stake
- 02Win a proof contest
- 03Deliver before the deadline
A prover evaluates the program and bids a price. Stake affects access to requests; missing a deadline can cause slashing.
How it works ↗PROVE delegator
- 01PROVE → iPROVE
- 02Prover vault → stPROVE
- 03Unstake request → PROVE
The depositor receives stPROVE. Exiting starts with an unstake request and a waiting period; the position is then redeemed for PROVE.
How it works ↗SP1, a compute marketplace and Ethereum
Each component handles a different stage.
SP1
The virtual machine connects an ordinary program to a proof of correct execution.
Prover Network
An auction service matches requests with prover bids; the Explorer displays requests and fulfilment.
Settlement contracts
Ethereum contracts record protocol state and proofs. PROVE transactions on Ethereum pay gas in ETH.
Succinct products and integrations
SP1 serves blockchain infrastructure and cross-chain verification. Explorer and Staking provide separate interfaces for requests and delegation.
Proof marketplace
Succinct Explorer
Browse Prover Network requests, provers and fulfilled jobs.
Capital delegation
Succinct Staking
Select a prover, stake PROVE, view the stPROVE position and request unstaking.
SP1 integration
Base Azul
SP1 has been selected to generate ZK proofs for the announced Base Azul upgrade, which combines ZK proofs with hardware-protected execution.
Testnet cross-chain verification
Chainlink CCIP
The Chainlink CCIP module verifies Ethereum finality. Its announced deployment covers the Ethereum Sepolia → Arbitrum Sepolia testnet lane.
Getting started with Succinct
A requester deposits PROVE into the Ethereum settlement contract, then submits a request through the SP1 SDK. Delegators use PROVE on Ethereum and ETH for gas; provers also operate computing hardware.
Request proofs
Build the program, specify inputs and request requirements, then submit it through the SDK.
Delegate to a prover
Open Staking, choose a prover and deposit PROVE. The prover sets the share of its revenue paid to delegators.
Operate a prover
Prepare hardware and stake, accept requests and submit proofs within their deadlines.
Who pays for a proof
A requester pays PROVE for a fulfilled request. Revenue goes to the prover, its delegates and the protocol treasury. Foundation incentives are separate from customer payments.
Rewards, governance and exits
A delegator’s position depends on the selected prover and vault rules.
Two reward sources
Prover revenue sharing and foundation incentives. Position returns change with vault inflows.
Voting weight is delegated
A deposit delegates economic weight to the prover. The initial governance design leaves execution with the Security Council; Snapshot votes are advisory.
Request and wait
An unstake request starts the exit process. Redemption follows a waiting period; slashing a prover reduces its stakers’ positions.
Sources and communities
Succinct architecture ↗PROVE and its token contract ↗Proof request lifecycle ↗Staking and redemption ↗Protocol parameters ↗Governance ↗Succinct forum ↗
5 sources about Succinct
Read the Succinct team, Derive builders and Zero Knowledge Podcast for SP1, proof generation and applications of zero-knowledge technology.Checked on 18.10.2026
Brian Trunzo
NTBro
Succinct's Chief Growth Officer. Explains how institutions can use ZK for privacy, verification and asset settlement.
Official
Affiliation confirmed
Succinct
SuccinctLabs
Official Succinct announcements on SP1, the prover network and zero-knowledge integrations.
Official
Affiliation confirmed
Derive
DeriveXYZ
An application-side view of SP1: Derive rebuilt its options exchange around ZK proofs for margin and settlement.
Builders
About the ecosystem
fakedev9999
fakedev9999
Succinct contributor writing about proving performance, Flock and practical uses of zero-knowledge technology.
Builders
About the ecosystem
Zero Knowledge Podcast
zeroknowledgefm
Independent ZK interviews and research discussions, including Ron Rothblum's work at Succinct, Flock and SNARK.fast.
News
About the ecosystem
Full list on xfollowlist.com →
Reviewed: 19 October 2026
Succinct questions
1Is Succinct a separate L1 or L2?+
It is a proving platform with settlement contracts on Ethereum. PROVE is an Ethereum ERC-20 token.
2Do I need hardware to stake PROVE?+
A delegator deposits PROVE with a selected prover through Staking. The prover runs the computation.
3Where do rewards come from, and how do I exit?+
Rewards come from prover revenue sharing and foundation incentives. Exiting requires an unstake request and completion of the waiting period.