How anchoring is positioned
The anchor points at the proof. The proof does not live on the anchor.
Proofnet BTC records the identity-bound proof natively. An external Bitcoin anchor is a commitment pointing back to the record. Revoking the anchor does not destroy the proof. Losing the anchor does not erase the identity state.
{
"type": "proofnet_anchor_commitment_v0",
"attesto_reference": "attesto:identity_binding:sha3-512:e5e1...e4d4",
"record_home": "proofnet_memory_block",
"record_home_required": true,
"external_anchor": {
"chain": "bitcoin",
"commitment_digest": "sha3-512:0c0a...b78f",
"optional": true,
"replaces_record": false
},
"proofnet_pq_algorithm": "ML-DSA-87",
"canonical_digest": "SHA3-512",
"public_safe": true
}
Order of operations
Identity, then record, then optional anchor.
01
Identity bound
AttestoBind confirms the upstream identity state and produces the canonical binding digest.
02
Memory block written
The accepted record is written to the Proofnet Memory Block ledger as the primary home of the proof.
03
Optional anchor
If the customer requests it, a commitment digest is prepared for external anchoring.
04
Replayable
A verifier can replay the identity, state, and binding without the anchor ever being required.
Anchoring is a commitment, not a storage decision. Production deployments keep the proof inside the Proofnet record layer; the anchor path is an optional external commitment that does not change what the verifier replays.