Proof of Evolution
Nova, IVC, and lifecycle state
Proof of Evolution is the async Attesto 2.0 lane for proving lifecycle state transitions over committed checkpoint metadata. It does not sit in the hot ingest path and does not block receipts.
Overview
Proofstream creates the evidence history first. The Proof of Evolution lane then takes typed checkpoint commitments, policy semantics, incident/gap state, witness quorum evidence, and previous lifecycle state roots and produces a new committed state root for the next epoch.
Nova and IVC
Nova is used for incrementally verifiable computation through folding schemes. In Attesto, the practical goal is to prove lifecycle state evolution over evidence commitments, not to put large AI workloads directly inside the ingest path.
State roots and public inputs
{
"previous_state_root": "sha256-hex",
"semantic_schema_root": "typed-commitment-hex",
"checkpoint_root": "typed-commitment-hex",
"policy_digest": "typed-commitment-hex",
"incident_state_hash": "typed-commitment-hex",
"witness_registry_root": "typed-commitment-hex",
"required_threshold": 2,
"required_witness_classes_root": "typed-commitment-hex",
"next_state_root": "sha256-hex"
}
Evolution chain
Each IVC epoch references the previous state root and the checkpoint range it summarizes. A verifier can inspect the evolution chain as a sequence of state transitions over evidence commitments.
Claim boundaries
The current allowed public wording is “designed for lifecycle proofing; cryptographic construction pending external review.” Stronger cryptographic-security claims remain unavailable until an external applied-cryptography review is completed and linked from the public trust material.
Current e2e circuit
The release-blocking attesto.lifecycle.e2e.v1 Nova
relation proves Attesto-native Poseidon proof objects,
policy-bound incident-gap semantics, schema-root binding,
boundary-root binding, and a configured 2-of-3 witness-quorum
relation using circuit-friendly Schnorr signatures.
The quorum signature message binds the domain separator, semantic schema root, boundary root, stream, checkpoint epoch and boundary, checkpoint root, policy id/version/digest, required threshold, witness classes root, incident state, witness registry root, revocation epoch, and previous state root. This blocks cross-domain, cross-stream, cross-policy, cross-checkpoint, registry/revocation, boundary and schema replay inside the relation.
The release guarantee is one end-to-end binding relation. External
JSON/SHA-256/Ed25519 artifacts are accepted only after deterministic
boundary verification and then represented as first-class
ExternalEvidenceBinding objects. Nova constrains each
binding's full-width Poseidon commitment, so no external artifact can
influence lifecycle state unless its verified boundary object is
present in the e2e relation. Stronger cryptographic-security claims
remain unavailable until an external applied-cryptography review
covers the exact circuit version, vectors, release evidence, and
commit.
