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
31f8dfe380b2d7a3e5dd2d4aafda454421cd011fbf914d2699896b4dcbc60c91
71f3411684fdf90c79a1712b7b0a7a55548ae29298040b5b270e72bc76214f7a
779f1e584578079e1aa0b100d6e925c129a220f31ca77308d33cebe627bc04b5
7374f21d6a3b5b114dd76d29d96a1bb90cc2a7af6807dfdcdc507c27cb1d5d88
65e8c340fd6b3b4e84362afe48ca84d19746fb3109ae07fd1e1274f42fd693ef
f9084e891b85c4f2e73bc766b80d41523ab4557b20a38dd21d3eeea54722ace5
be4bca0f66a3e8a86a121f307bb2c8016008656275296b0335426158ae9a7cfc
d95920b23ebe04ee9414de703b9d8527a4903d9432aa2da09f508a95427eb165
ed0af606c1620d36f6a8277bb83141306f56a4b6aaad2116597ffb059a5ac1c8
6eca8f966a4b1421fafb3825eb894ea5842f751bcb6b26608fa5fb05da79747e
9ba6a20528b3dc73231f35661875ac0630e75c1846cbe141422c86998fa06fb9
3028f3299a8c4cf379b0b5553c5b325adebf4916bce2f89efde7c4ab2725a2d4
da4d8db83be64d542f8b55f7126682c546ae6d55cc93e4cf8dec5c1d20c1218e
2a443213cf90ed67eaad9893133f1c899fff917659599eb5904cc570a5aa8014Trust 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 973396 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 fa517d58e3aba62fc4bfef9693d3fe09c902fc1adeba2dd2bc80fa77e8a6926f; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / fa517d58e3aba62fc4bfef9693d3fe09c902fc1adeba2dd2bc80fa77e8a6926f, and the block's
timestamp proves the page looked this way at or before that time.