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
82ea870b4952f1c855dfd522ced45714341cdbc5d48fca680a89bcee5c7eed5a
0f2bf49b25735192081a8ee8f24996b7cf6ac384a0c540ae436e8916b9288934
10623cfc4188f5ffb67660a358ca0574d920bfbf73ff91ef74b46ea8f8e03365
a18cc8d9c9b7dc740fce08aca9e2823893707a08e652b4fcadf01a7e11f245c7
3501634f605264abdf6a4cb08a6f41da9cadb6ce5e34c7284fc1d0b2012b87a7
0dd42d6497c80aa8effd64cef86b94ba31fbb28ec057af12f79702c9bf298172
59cf0227b549bc2d63f3b11534f78e09aeddc466c2f739bfbbffa307b46237d3
e9b39cd3d2433fe260f9276f4ebb7e1b49c142f12f9b0c9e433140da25dcac7a
140c1149859b78aa110efe307ffd3b4db2a4e18f942950eb59d53f773b0857f7
e54b2dee8b1e0845bd1ef7ad3c68d0fef2feceb28b444fb016ff71b116d67d76
bb71e82f7959ca35c38a5b9bc893e1303c2bd1c39497cd7896574022f0a83046
12526a358ebcb53042de69baa7d91353d4ebc3506b41fbbe2fc6796dad5ff9e8
2b97cb011fc4037bd4586f24b6b25d0328a7e577f6dc6c2b2040d76104e89488
a7f8e462eec7f3db11af584acd33c1e5b966ea89c5c5022f2992d92a5e4bed68
c32670d0c7309344043c4d9b2b97dca98494c9c6f8bc4ce3630676e62934dd27
3e5897cb5a44e862524768e5aaf7b471087e1b623beda8d850fb3c2f95db8164Trust 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 972208 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 371524ee470f03fae67697e49a95f33df2811894b2455d5adfa49f3dc7c8246f; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 371524ee470f03fae67697e49a95f33df2811894b2455d5adfa49f3dc7c8246f, and the block's
timestamp proves the page looked this way at or before that time.