Succinct

• Succinct operates a decentralised prover network built around SP1, a zero-knowledge virtual machine.

• Developers write ordinary Rust programs and SP1 proves their execution, rather than requiring hand-built circuits.

• PROVE is used for proof fees, prover staking and governance.

• Fixed supply with allocations to community, ecosystem and contributors.

• Provers stake PROVE to enter auctions for proof jobs and can be slashed for failing to deliver.

Pros:

• Writing proofs in Rust rather than a circuit language removes the largest barrier to adopting zero-knowledge proofs.

• SP1 is used in production by other protocols rather than only demonstrated.

• Competitive prover auctions should push proving costs down over time.

Cons:

• Proving demand is concentrated among a small number of rollups and bridges.

• Several proving networks compete for the same limited market.

• Prover economics depend on hardware costs the network does not control.

• Exposure to zero-knowledge proving infrastructure with real production usage.

• The developer experience improvement is substantive rather than marketing.

• Weigh whether proving demand supports several competing networks.

• Proofs generated from ordinary Rust programs, so developers do not need cryptography expertise to use zero-knowledge proofs.

• Building zero-knowledge applications has required hand-writing arithmetic circuits, which very few engineers can do.

• A zkVM that proves normal program execution makes the technology usable by ordinary developers.

• Founded by Uma Roy and John Guibas.

• Backed by Paradigm and Robot Ventures.

• No public ICO. PROVE was distributed through airdrop and ecosystem allocations in August 2025.

• Proving demand is concentrated and could contract if rollups build in-house.

• Multiple competing proving networks target the same customers.

• Prover profitability depends on hardware and energy costs.

• Slashing risk for provers failing to deliver.

Succinct's papers on SP1 make a straightforward argument: zero-knowledge proofs have been held back not by proving speed but by who can write them. Building an application meant expressing it as an arithmetic circuit, which is a specialist skill held by very few engineers, so the technology stayed confined to teams that could afford cryptographers. SP1 proves the execution of a RISC-V program instead, meaning a developer writes ordinary Rust and the proving happens underneath. The papers are clear that this costs proving efficiency relative to a hand-optimised circuit, and argue the tradeoff is worth it because a slower proof that thousands of developers can produce beats a faster one that almost nobody can.