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
1d0baf06528defc0f1af95bf4f69a43129bfdd4c36193cb10afe5446fd285c4b
6898265ee2a590645d09da9da90539ef0975f37e95d657e38e6de962bd5f73d4
7a061e11a562568bbf865634b75df6170385e93d8984b5ca17e8c4edb8aff2c5
15f8ad42ba1d979a5f73bb14244e41d4c4bc6ca3e878ddf00520d8d992e8fefe
6ec0f14a89943adafff703f40f5b273ba1a4ef8017d9cb3ae27fef6bfb7c1061
5076880716345c02c89df277538f07813339499207b3d8c6239ee04c92c2e23e
65b120e24aead957286658cbe960b50286add14bfaca9c9db43d2a5937668451
8a3d8f65cf75a463d040ecd8bafd3b683adcde82924255f0a9fb60ef6bd74b58
48cc28106dee56a6c1449ce96e0755cdd997e6ed51ba8ccf17b913c70aa15b1aTrust 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 963869 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 47af26e38861f4b54df029e59de37c1f4867135fffbe419865db2c62ecfeaaef; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 47af26e38861f4b54df029e59de37c1f4867135fffbe419865db2c62ecfeaaef, and the block's
timestamp proves the page looked this way at or before that time.