Three proofs your own browser runs — trusting this node for none of them. The burn key falls out of
Bitcoin's own math; the donation is confirmed directly against Bitcoin (mempool.space, a third party);
the journal is a SHA-256 chain your browser rebuilds from the raw bytes. If any of it were a lie, the math would say so here.
Proof A · The address belongs to nobody
Is the burn key really keyless?
Every donation pays a taproot address built from Bitcoin's generator point G, hashed to a NUMS point
no private key exists for. Your browser recomputes it from G. (Full step-by-step: the burn proof.)
Proof B · The sacrifice really happened on Bitcoin
Did this donation burn real satoshis?
Paste a donation's Bitcoin transaction id. Your browser asks mempool.space directly — not this node —
whether that transaction paid the keyless burn address, for how many sats, and how deeply Bitcoin buried it. Then it
shows what this node minted for it. Bitcoin is the witness; the node only gets to agree.
Proof C · The whole history is untampered
Is the journal an unbroken chain?
Every event's hash is SHA-256(previous hash + the event). Your browser downloads the raw journal
and rebuilds the entire chain link by link. One altered byte anywhere breaks it at that exact event — and names it.
These three run in your browser and need no faith in this node. The truly complete verification is the second node —
it re-derives the entire cascade root from the journal and re-proves every Bitcoin anchor from its own bitcoind, so it
can prove the whole network to anyone, with no operator alive:
For total zero-trust on Proof A, run the math offline: node apps/kray-net/burn-verify.mjs. A doctored node could
serve tampered page scripts — Bitcoin's record and your own machine cannot be doctored.