ImmutableProof
Design constraints

Evidence should survive disputes, time, and company failure.

ImmutableProof is built around constraints: deterministic verification, frozen semantics, and minimal trust assumptions.

Frozen meaning

A proof created under a protocol version has fixed semantics. Future changes cannot retroactively reinterpret existing proofs.

Deterministic verification

Given the same proof and protocol version, verification outputs the same result. This supports auditability and repeatability.

Offline verification

Proofs are structured so they can be verified without reliance on ImmutableProof services. Verification can be performed independently.

Billing cannot change proof

Payment affects only creation of new proofs and exports. It does not affect proof semantics or verification outcomes.

Goal: reduce “trust us” to the smallest possible surface area.