Leveraging the zkSVM
Last updated
Last updated
Please reach out to request an API key and generate a proof in only a few minutes.
The high-level flow is to start the session, send requests containing SVM transactions, end the session to trigger proof generation, and poll the endpoint to retrieve summary statistics.
End the session to trigger proof generation and select the . Supported types are core
, compressed
, and groth16
. The last option is recommended for most uses, including on-chain verification.
Since proving is async, the response only contains a successful acknowledgement of the request but not the completed proof details.
Once the prover has completed proof generation, the proof can be verified either locally or via an on-chain program.
The library provides a few utilities to initialize program accounts and generate sample SVM transactions for convenience.
There are a few limitations to keep in mind. The system currently places a hard cap of 50 transactions per session due to memory constraints of the underlying zkVM, which is around 24B cycles. The server will reject requests that send additional transactions beyond 50. Not that if you start a new session, old data from previous sessions are not persisted.
The zkSVM contains several pre-installed Solana Program Library (SPL) programs, e.g. the token
and token-2022
programs, but any custom programs need to be deployed before they can be interacted with.