Native record
Every accepted attesto becomes a replayable row.
The row does not need Bitcoin to be meaningful. It carries the canonical attesto digest, accepted state, validator result, and export packet pointer.
{
"type": "proofnet_memory_block_row_v0",
"row_key": "identity_binding:keri:sha3-512:6c6a...",
"attesto_type": "identity_binding",
"state_digest": "sha3-512:ef6e...",
"binding_digest": "sha3-512:6c6a...",
"validator_result": "accepted",
"row_commitment": "sha3-512:42aa...c901",
"external_anchor": "optional",
"public_safe": true
}
Replay path
A reviewer can verify the same accepted state later.
01
Accept attesto
A verified identity binding, provenance packet, contract receipt, or transport proof enters the record layer.
02
Commit row
The canonical row digest is computed with SHA3-512 and linked to the attesto digest.
03
Seal memory block
The row commitment participates in the Memory Block seal as Proofnet-native history.
04
Export packet
The proof packet can be exported, replayed, and optionally anchored outside Proofnet.
Positioning: Memory Blocks are not the same as rowblocks. Memory Blocks are the native Proofnet record layer for accepted proofs; row commitments are an internal structure inside that record path.