MIT-licensed, resource-bounded proving backend for Plonky3 0.6.1.
Complete larger STARK traces under an explicit RAM ceiling, using deterministic
SSD scratch, while keeping the official Plonky3 proof format and an unmodified
upstream verifier. This is prover-side infrastructure, not a new proof system:
no new transcript, verifier, proof format, or security profile.
Measured
On a 4-vCPU / 16 GiB Linux runner, bounded vs conventional peak resident memory:
| Workload | bounded | conventional | reduction |
|---|---|---|---|
| Fibonacci 1M rows | 119 MiB | 703 MiB | 5.9x |
| Poseidon2 1M rows | 567 MiB | 3,526 MiB | 6.2x |
| Fibonacci 16.7M rows | 1,815 MiB | does not fit | — |
Memory is a policy-pinned ceiling, not an emergent value: the 1M and 16.7M
Fibonacci jobs both ran under the same 2 GiB ceiling, with the growth absorbed by
scratch (1 GB → 10 GB). The trade is RAM for NVMe, and it costs CPU time —
roughly 2.4–3.1x slower than the conventional path. Quote both numbers.
Qualified for this release
backend-v1-final-evidence.json (attached) records status: ready for this exact
commit across 11 gates: official verifier acceptance for both reference AIRs,
deterministic cross-mode proofs, a crash/resume/corruption suite, 1M and 10M row
cgroup-v2 resource gates, pinned Plonky3 dependency profile, clean release source,
AIR job contracts, engine/CLI/OCI identity match, and signed SBOM + checksums.
Artifacts are signed; verify SHA256SUMS against SHA256SUMS.sigstore.json.
Supported scope — read before use
- Linux x86-64 only.
- Profile
tinyzkp-p3-goldilocks-v1: Goldilocks field,p3_uni_stark
(single-table), Poseidon2 permutation. - Two reference workloads:
fibonacci(≤ 2^24 rows) andposeidon2_goldilocks
(≤ 2^20 rows). - Not supported: lookups, buses, multi-table AIRs, recursion, GPU, or other
fields. If your workload needs those, this release will not run it. - Local NVMe scratch under your control is required.
Not included
Hosted proving, hosted verification, accounts, usage metering, MCP commerce, and
the retired public beta are not TinyZKP products. Standalone TinyZKP protocols,
legacy receipts, recursion, zkML, zkVM, IPA, Spartan, KZG, and rollup prototypes
are research only and are not compiled into this engine.
This release is not a performance guarantee for your workload, and not an
independent security audit.