Web-page notarized
A tamper-evident timestamp of a page's content. Pay-per-call — bsv.cx
Rendered page — archived HTML, sandboxed · click to collapse
Html-only render: no scripts or original assets, so it may look unstyled. Not the live page; not endorsed by bsv.cx. ⤢ full screen
WhatsOnChain · Banana Blocks
SPV proof & how to re-verify it yourself
000f7c84a38a2813109cbc7d44e19c4f99ac982a7f57396c99ab83a3b9186c14
c12282f2c71af950f3ef9321ddd7272b2990b7ab949baf91d1cbfc6be3cf9538
559b23f338dff6ed8c75be5c0f420fea8dbda719da47633596f2b1b2db5faa98
52515a2a02068257cfae1ff184a3e160c41e18dd4397fd78d7af5afb0bc9f2eb
cde57396816ccbec220a2dc9580e05cb1fe14ccd167940cfd46e32f994ee071b
655dd8eaf9768fb45cccda38a1a2ff02fe8f1ffbe6d02637b360023b1bad1920
f3183ed6e5e94ae1e4f2faab96cb95bda1f468c4ee7a5d48073b8cfa3033af5b
9aed0589767a2ac15bc8f7a99a2e91fbe92c7bd8d4a1ca482e1a097a27695192
9c9b2e4665e1977e3b3c2be6ad5dd400a42e0de9820238cc4849a8983e3deccc
68922e08d3191c62ad360466a29b9693313fa6bc3b8605976bac952d301af55e
17e51c953eb208b9a25c47fc7761e0d0bc3654c2878a589e76bc4de964ff266e
0579c2a19a9f3d06342b2001a2aded4dad71ff114439c47c0cab434ed02028e3
36cebaaa8aa954ff8599a1c1675331af8430b5b962e0062821a7e898bade3bfeTrust no one: double-SHA256 the txid up this branch — at each level your hash goes
left when index is even, right when odd, halving the index each step —
to get the block Merkle root, then confirm that root is the header at height 966160 on
any block-header source you trust. We verified it against headers we run ourselves; you
verify against yours — no explorer, and no bsv.cx, in the trust path.
Prefer to check it against a second independent source? Paste these fields into
our public verifier (POST /spv/verify) — it folds the root itself and
checks it against headers we sync, so it can only ever make a bad proof fail.
Or take it to your own tools in the ecosystem standard format:
BEEF (BRC-62, tx + proof) ·
BUMP (BRC-74, path only). Any @bsv/sdk client verifies
these with no bsv.cx-specific code — Transaction.fromHexBEEF(hex).
Save both. The manifest's SHA-256 is the anchored id, and it binds the HTML hash — so from your saved files you can recompute every hash and match the transaction's OP_RETURN yourself, with no dependence on bsv.cx ever being online.
Verify it yourself: the manifest is the exact JSON whose
SHA-256 is 23a056684a3444bc5d7868b8abb4aabab2beee1839a3427ac373a3329d52dabf; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 23a056684a3444bc5d7868b8abb4aabab2beee1839a3427ac373a3329d52dabf, and the block's
timestamp proves the page looked this way at or before that time.