Proof of Evolution

Nova, IVC e lifecycle state

Proof of Evolution è la lane async di Attesto 2.0 per provare lifecycle state transitions su committed checkpoint metadata. Non sta nell'hot ingest path e non blocca receipts.

Overview

Proofstream crea prima l'evidence history. La lane Proof of Evolution prende typed checkpoint commitments, policy semantics, incident/gap state, witness quorum evidence e previous lifecycle state roots e produce una nuova committed state root per la epoch successiva.

Nova and IVC

Nova è usata come research direction per incrementally verifiable computation tramite folding schemes. In Attesto, l'obiettivo pratico è provare lifecycle state evolution su evidence commitments, non mettere grandi AI workloads direttamente nell'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

Ogni IVC epoch referenzia il previous state root e il checkpoint range che riassume. Un verifier può inspect l'evolution chain come sequence of state transitions su evidence commitments.

Claim boundaries

Current production language is “designed for lifecycle proofing; cryptographic construction pending external review.” Statements più forti su externally reviewed cryptographic security restano unavailable finché una external applied-cryptography review non è completata e collegata dal public trust material.

Current e2e circuit

La relazione Nova release-blocking attesto.lifecycle.e2e.v1 prova Attesto-native Poseidon proof objects, policy-bound incident-gap semantics, schema-root binding, boundary-root binding e una configured 2-of-3 witness-quorum relation usando circuit-friendly Schnorr signatures.

Il quorum signature message lega domain separator, semantic schema root, boundary root, stream, checkpoint epoch e boundary, checkpoint root, policy id/version/digest, required threshold, witness classes root, incident state, witness registry root, revocation epoch e previous state root. Questo blocca cross-domain, cross-stream, cross-policy, cross-checkpoint, registry/revocation, boundary e schema replay dentro la relation.

External JSON/SHA-256/Ed25519 artifacts sono deterministically boundary-verified e legati in Nova con full-width Poseidon commitments. Il bridge è un first-class ExternalEvidenceBinding object con binding id, source digest, optional source public key, binding commitment e timestamp. Stronger claims restano unavailable finché una external applied-cryptography review non copre exact circuit version, vectors, release evidence e commit.