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
85b0691c5de3422e9bb83292c30658456cd9a240c8095dac1003f3f9fd4bb4f6
a1b9c3aa29fd08431c2c19a0f818b89e0bd8ebda7a6d6498a308a63bde5a8b38
d2337bbe30ec879fa95f624adaa6bf1b3b95c53b4d75f379c0350c12ea1535a9
81ccb86f9608e48fbb739281cf13c4eccee47e97cb6d98eb4172fc896f5abc31
053ccb8b0fe7aebf40b9c95d4d58a2eae81cd21788a5b782c1d270696b6b49f5
4be6a1da53d0e71feffca25e9fb69e3a52b47eafa44d6cd4bbb7e0033c66b622
7527bb7c5fc6f2e3d807f8a1e0ae5608a67ed2bf8bb2db3c0fcafa117b3d36ca
7e9a13dc2dbd05ce826c6518b74357ae7762548e81ef19be49ffb3fa8d2bb4e5
f99b9ca5260cd6051d72910b7fa2ed728b3b605928e590aa62e3330dcaa9be9d
d3be339bdc7aa05011be48fed832a2cae32523dc9c0636f968e6873c38fcd5d4
8565c0fab3074f01b8ffa7cf10db68e0f08178b1fa980d833b00e8b4b74ab5f2Trust 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 967054 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 b9f1d73e34c745bd13355e0325721e6bc83f89ff255e4dada9c347b948a0e32a; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b9f1d73e34c745bd13355e0325721e6bc83f89ff255e4dada9c347b948a0e32a, and the block's
timestamp proves the page looked this way at or before that time.