Proof of Evolution

Nova, IVC y lifecycle state

Proof of Evolution es la lane async de Attesto 2.0 para probar lifecycle state transitions sobre committed checkpoint metadata. No está en el hot ingest path y no bloquea receipts.

Overview

Proofstream crea primero la evidence history. La lane Proof of Evolution toma typed checkpoint commitments, policy semantics, incident/gap state, witness quorum evidence y previous lifecycle state roots, y produce una nueva committed state root para la siguiente epoch.

Nova and IVC

Nova se usa como research direction para incrementally verifiable computation mediante folding schemes. En Attesto, el objetivo práctico es probar lifecycle state evolution sobre evidence commitments, no poner grandes AI workloads directamente dentro del 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

Cada IVC epoch referencia el previous state root y el checkpoint range que resume. Un verifier puede inspeccionar la evolution chain como una sequence of state transitions sobre evidence commitments.

Claim boundaries

Current production language is “designed for lifecycle proofing; cryptographic construction pending external review.” Las declaraciones más fuertes sobre externally reviewed cryptographic security siguen unavailable hasta que una external applied-cryptography review esté completada y enlazada desde el public trust material.

Current e2e circuit

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

El quorum signature message vincula domain separator, semantic schema root, boundary root, stream, checkpoint epoch y boundary, checkpoint root, policy id/version/digest, required threshold, witness classes root, incident state, witness registry root, revocation epoch y previous state root. Esto bloquea cross-domain, cross-stream, cross-policy, cross-checkpoint, registry/revocation, boundary y schema replay dentro de la relation.

External JSON/SHA-256/Ed25519 artifacts se deterministically boundary-verified y se vinculan en Nova con full-width Poseidon commitments. El puente es un first-class ExternalEvidenceBinding object con binding id, source digest, optional source public key, binding commitment y timestamp. Stronger claims siguen unavailable hasta que una external applied-cryptography review cubra la exact circuit version, vectors, release evidence y commit.