Local proving · bounded resources · ordinary verifier

Keep proof jobs moving when RAM runs out.

TinyZKP Guard supervises supported Plonky3 proof jobs on your Linux machine. It preflights RAM and local NVMe scratch, chooses the appropriate execution path, and resumes interrupted bounded runs without changing the proof format or verifier.

Your workload and witness stay on your compute. No hosted proving, usage meter, account database, or TinyZKP control plane.

One narrow job

A memory safety net for proof infrastructure.

TinyZKP is for teams that already have a supported Plonky3 workload and a concrete OOM, machine-cost, or restart problem. It is not a new proof system, hosted prover, or generic ZK platform.

Preflight

Know the resource envelope first

Doctor validates compatibility and estimates conventional RAM, bounded RAM, and scratch before expensive work begins.

Execute

Use RAM or SSD deliberately

Auto mode keeps the conventional fast path when it fits safely, then selects bounded execution when the estimate crosses the configured ceiling.

Recover

Resume an interrupted run

Exact-release-bound, checksummed job state makes interruption recoverable without silently consuming stale or corrupt checkpoints.

01 · CheckValidate profile and paths
02 · PlanEstimate RAM and scratch
03 · RunProve on customer compute
04 · VerifyUse the ordinary verifier
Technical differentiation

The proof remains ordinary. The execution becomes operationally survivable.

What TinyZKP changes

  • Resident-memory planning and enforcement
  • Checksummed external-memory scratch
  • Deterministic checkpoints and resume
  • Machine-readable reports for CI and schedulers

What TinyZKP does not change

  • The supported AIR semantics
  • The released proof format
  • The ordinary Plonky3 verification path
  • Ownership or location of customer data
Claim discipline: TinyZKP does not claim exclusivity, zero-knowledge privacy, arbitrary Plonky3 compatibility, or production performance beyond published candidate evidence.
Two choices

Free engine. Paid operational guardrails.

The MIT Community engine is the evaluation path. Guard is an organization subscription for qualified releases and the local supervisor—without usage charges or hosted operations.