Live demo
Disclosure
Burn Protocol
Registered copies burned, receipt to prove it.
The problem
/ 01Disclosure hygiene requires proving that the registered copies you control were destroyed — without claiming offline clones or global erasure.
What it does
/ 04 01
Registers a contentHash with replica locationRefs.
02
Burns registered replicas with a receipt.
03
Second burn fails — burn is terminal for the registration.
04
Lists and verifies burn receipts (metadata never reveals payload after burn).
Who it’s for
/ 03- Compliance teams attesting destruction of registered copies
- Records custodians managing replica lifecycles
- Auditors verifying burn receipts per locationRef
In context
/ 01The destruction counterpart to the Vault and Dead Drop — minimization and one-time handoff, then attested burn.
