For teams running recurring SP1 proofs

SP1 proofs.
One HTTP API.

ProveIt is an API prototype designed to offload SP1 GPU proving. We want to understand the work around your proof jobs: worker setup, failed runs and upgrades.

Discuss one proof job Explore the idea ↓
TARGET ZKVMSP1 v5
INTERFACEHTTP API
PAYMENT MODELPay per proof
01 / THE APPROACH

Send a program.
Get a proof back.

The prototype is designed to accept a compiled SP1 program and its input over HTTP, run a GPU proving job and return the result. Async jobs have a status URL for checking progress and retrieving the result. The payment design uses USDC on Base through x402.

Does this look like your workflow?

Bridge batches
Does each new batch trigger an SP1 proof job?
Light-client updates
Do you prove header updates on a schedule?
Public data computations
Do you rerun the same SP1 program as new public data arrives?
// Example request payload
POST /v1/prove
{
  "system": "sp1",
  "program": "<base64-encoded SP1 ELF>",
  "stdin": "<base64-encoded input>",
  "mode": "plonk",
  "async": true
}
02 / WHAT MATTERS

What makes proving
hard to operate?

Already using your own GPUs or the Succinct Prover Network? Tell us what works and about the last job that needed manual attention. Approximate figures are fine.

/ 01

Volume & cost

What triggers each proof: a batch, a block range or a schedule? How often does it run, and what compute costs recur?

/ 02

Failures & recovery

Think of the last delayed or failed proof job. What happened, and who had to step in?

/ 03

Integration & upgrades

Who maintains the worker setup and handles upgrades? What takes the most engineering time?

Current stage

Early-stage research prototype for SP1 v5, Plonk and Groth16. Not a production service. No SLA or published prices; speed and cost comparisons have not been measured.

What the prover sees

The proving backend and its GPU provider receive your program and input (witness). Use only data you are comfortable sharing with them. For this conversation, a workflow description is enough.

Start with one proof job.

The email opens with four prompts: your SP1 version, workload and frequency, current setup, and last operational issue. A few lines are enough.

Contact us