TinyZKP
Measured claims only

Performance claims start with reproducible evidence.

Every published result must bind the source release, proof profile, workload, host, command, raw measurements, proof digest, verifier result, and independent reproduction.

Run the open engineReview launch gates
No production performance claim is asserted here yet. The thresholds below are release gates, not measured customer promises. Candidate reports appear only after review and identity verification.

Fixed-host qualification matrix

RowsWorkloadsRequired evidence
1,048,576Fibonacci and Poseidon2Conventional baseline and bounded run; bounded peak RSS at least 4× lower; bounded wall time no more than 3× baseline
16,777,216Fibonacci and Poseidon2Bounded peak RSS no more than 2 GiB; observed scratch within 10% of preflight; official verifier acceptance
ExternalAt least three non-reference workloadsSame public adapter and contract; no customer-specific branch; acceptance on customer-owned compute

Reference host

Linux x86-64, 8 CPUs, 15–17 GiB resident memory, swap disabled, cgroup v2 enforcement, local NVMe, and at least 500 GB free scratch. Reports from other hosts must be labeled separately and never substituted for the release matrix.

Evidence bundle

Identity

Immutable source SHA, release tag, engine and Guard versions, OCI digest, artifact hashes, schemas, and compatibility profile.

Resources

Whole-process peak RSS, elapsed time, CPU time, read and write bytes, scratch peak and estimate, exit class, and cgroup settings.

Correctness

Proof digest, conventional/bounded equality where required, official verifier outcome, crash-resume cases, and integrity failures.

Publication rules