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
59f61041a4f1120a64fe9c81bb7e645fd0e22a5fd8434d906003acbebc71e66e
95320ac523cf06e32438935e95288cc5cb4a017d4db9f324e54dae73ae58ed39
f40a4ec72fa1a134c978aabb692b84b1deb53b0d69b3a38906da1d4e2e5f97a9
d6ae2b7194708c17f1065db333e50ca0dcd3e715b8f423622cdff794effd77f9
f5f9fb4966107825fd8878c7464ea3cb28d53f82c2cead53467bcb657a0dc1e9
1cb16cf0bd293b008850845259a423ae6bcfd60a3e5558ea7ec6af35bf0f7a67
739319c25917d5e315dbad6d1a6385276611f93802bc58046cf2c5667ff8e8d0
cdf5e368e78dbab087619465beee0097ccb813ee31acd7890f8736f5c18157ad
264b443bd5a86d1cfbd34290ae1095da2131fe5cce4b3e86123f11c7e5e867d6
d93e9df7e0a70e4376b9cee5ff74377e7b98552da92b84d8704d8881486ff32c
572acf641d4b6caf883a30d9f85b677086e0557558ad81dd1062079ddc254aac
4982bffd7b699106923d58727b4f4ad5b786fa71d3d68d765b3c5e47a9d29fad
252201f3c358ac6c6b963209b877a99f8c41f79430100d94848b1913b601f20aTrust 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 973671 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 a895df3190408266dbc2cff9af2a3dd6b6e6fd7b9a49ee35a0b7e098219e16c6; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a895df3190408266dbc2cff9af2a3dd6b6e6fd7b9a49ee35a0b7e098219e16c6, and the block's
timestamp proves the page looked this way at or before that time.