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
dc52e81c387661bde75a4284339d11f47eeb741cc2d7ccc0a924c2a392435d3f
7da9b7ec351c7baa480178283b9a8ed603fa623a6d4d2b76ac4546c6b1db4518
d7002e582599b8f75ddd62026018b30205ce15d73ddb85c552f217baf953dc74
bd58d591846d3353753d280d24290dec9eb4e0d8c7301421d292d902eca10204
ee9aa767defb705cbb84e6c47b529a4984d7a118b50a0a6a9e84a22cce2075ef
06a8c4579c6af2c75acb136b545491408745a10083dae6dc1e9948199e07c7ac
1db030342856560f8c1a0e69023e70cafb5460375d02ee3882c7f68e370eec7b
b6bf123d61a3c4a7d8890bf536b349aa5113196a8b1d462fd384d172ddea20b6
9ad183e3f34fceec55788ae6c814bd594bfa21be7452736908c2c9e0e130dcdc
76dcc399f60c5cc1eeb6e208730a5c5ae7b4285ec0840245ac151aad483be8fa
ba52b4c80028f0b052c646912b313446f5b168bf3f113d075e732559269075e4
e4111ee7a70c4ad42d251c6f05911a28aed9b09bcc3240cf9adeed04259d7f56
5fa2e37fd6e487885f4e6db1b8fb8b82cfa136b6991bbaaf2833260ffdfa0040
f59c26fd354432a17c78e98f37e9c33aec43efe5220de2ffd7a1161e572c50bcTrust 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 962164 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 08aa76750ae8350d734a1ef128a93f9d58ee95a6688ec9f032722677746a3e26; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 08aa76750ae8350d734a1ef128a93f9d58ee95a6688ec9f032722677746a3e26, and the block's
timestamp proves the page looked this way at or before that time.