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
e0be6a1560a45d60d28cbced3bbdbdd9ebd2932fdc7da90fe6831c93c7683293
baf85627541325625ef2a4c0b3d9d2b1d67581ad199dc0aa63042765b6f49712
730115e4ca774d2ae59c139a3032f8d747d718430c7d8d1f325f7fbd2eda455d
73549c0045e54079c5abd3b8ea7207d979c4f29229f89bff83f09969588bf308
3b01161566abd159c1540f42a8751e334fe61b8f8ceadc42375f916f7d4f5d1a
4834827071892b3ecb12e0ca18161b8b839a86993411e9fb789634a1137bbf70
bffbbebd037f56fd029b1b356252b5621170f01d2b2c914d11779f75c5275aae
585d6221f712dd046367fb1b246e56ed21651cb19fd820b0adeabab50b55585c
8a447fc3bd72bd6bc97157bfbb250b059dfb2d8002fba7afb1ed906293052e31
0ed50e6312863ce464a7e930bd4c0736a5ef71478eda4aecb2c88aa554a94458
89cd9c38b8ca175ba37c8f321aaf817df15a30e4776433d2ed7e30637b8e828e
fefb6d113de9f5cb4aaa602aa391076f2bf4b90e5d2197fd25ce5907ba7ceed9Trust 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 967132 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 2da95a1ec444a621f20838af4f2985a3e4722e35ded9f71029ba122190f54a5f; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 2da95a1ec444a621f20838af4f2985a3e4722e35ded9f71029ba122190f54a5f, and the block's
timestamp proves the page looked this way at or before that time.