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
60396a01baae47d8f1918cd3dedf898964c08d69944b6238395e7d1780d9ab06
3ea196c6c967355f39103d90271392c6f27a4c084ef96155c45d56737763a9bc
e5daca5c7be8346b59d0f4c3ce9092a9aabf5e36ef6ba712f1dd26631c44b684
12ec14ea7db8066d5bb7bf17e061849353e6a1808a953d292175715733636ffe
15c01cf8432c3ee1a25969f211f861f4754c9a19483ec7d7cd6301fb47b433be
a0411493906c2dfe4acadcc725d19106040b11f49a427c4b5ac62fda48c2c1af
c3e3688b921220da367cfd3c11ad99cf12ececb68c1fd9d892ba3f7a2d675a0c
1c232d2e69e037e6cb83402da9088455cdacf6c270a9785d4b248a45033ec702Trust 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 962081 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 77c5b971df9e18a1160782a7efa25b73327f98888b5fd47e7005b6e104cde946; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 77c5b971df9e18a1160782a7efa25b73327f98888b5fd47e7005b6e104cde946, and the block's
timestamp proves the page looked this way at or before that time.