Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
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
17432c7fde267d31b918ad8ae09b0e207038d0b8007b9105b7399ad3d02643ef
a1c1a4e13979f4a3933f286e9fce1d6c9b710b794597ad8319813fbd951e8657
595d91511706263fd9aad839ecec7d9487e5ba3d841b1986e5ca155c6412a4bd
9df54fe297cad416f7e1275b9560e495246f263a0c477dd6adc38d9813cf900c
ae37cbfecbb7759cc186c11b426902c05fe8a1723c73403c9c4a7537fb52d74c
647ce564ba4ea01f6a82193174953a1827df42fa8857cfa8c612fb4b766f172f
05e8661342d4461cf71ef7dbe030fa424bd636c34dfd70a94356c75fec35d23a
6f68f4bb0c612b1e467f5d9f00eaaee61e039eccec595a013749e30ed713bbb6
a6ca01468258cb9c519ddc4b2a147f71b41e4a7c8896c5229aeb238ba4532470
07de314d9d1564903185c3cb6b4b2d9b8b5fd52e5088ef3ae41a4d4fe8d7f7dc
be89a88de3d37fd8732d40ed7517c32afc10484eb6e309f684733b9144168ae9
6c618bca8416178379bc13e67a2dcb8db6eb6d1c43b4c7f0aabd22d656edafd4
c91b3b8177480efa15857eda3322ceec555f85407fd4b25ef0ec14a2646cfba0
da53a9c52eae97cb1f98210cdaf2821ee68a1e8d6138e7b6ade1a867dcde2485
b46514acd6826126d6fd788f44ceb3368bc1a301f3325ae2d350a0d402caa067
11d171091b68a8045484b21bbe24d1bbaa4056d2ac1aa919e6d34c681344c107Trust 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 965995 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 0fd644b2329b4446af7c3c0ea0a18b1124e63a6364e395ae2669f8d8354aaf7c; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 0fd644b2329b4446af7c3c0ea0a18b1124e63a6364e395ae2669f8d8354aaf7c, and the block's
timestamp proves the page looked this way at or before that time.