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
74f70d07342a8371a5c7dca3d71e9fa9c2846cb4955da5345edea048c370f854
fd008cf4693e3942dbaa44faf464904e12f79eafa172827aff581b7276933610
85c5561c6756a5cfd3be7d41eada0705de7c87e314477e0402203237947cfdba
dddd382e413306d948fc976d7b87613ff7c931321658b45fff969a818e291dca
321b1cceebef2708f979618f617d49cf667f639cb098f8a9fd3169c4892356a5
30352e9442df356381a3462f2d8c6b889319e689ae7c5bf950af91a6c5bb058b
c6e94213356903233aed7939ad1827a0837be128c249ebc08d7047172e7c4965
49dc8e0e3985ef62aa45ad4935c3ec5cc013b73105479be37692d8f6dce11ca4
86352ee2f66575805c13e797b01fe2b656e52da1ff611aa234340a98f39c86e4
a505c6edddf7c7382396aea9845eeb8d6d422bbaa5fae65aeab5b9f33e3a8df5
59ab9993c2d3ab8e248735c9fb873839d21ea6e819d8c9b8884991170c9c0056
ec5b4cdfabbf2349df33bc601014226c624906840920cfc79145e72163d96900Trust 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 974522 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 0a38e41fa2785b0a99569bb8320821d4f2cb29fd1d1942898af18b145919ca24; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 0a38e41fa2785b0a99569bb8320821d4f2cb29fd1d1942898af18b145919ca24, and the block's
timestamp proves the page looked this way at or before that time.