Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
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
b1cd41c1f7963454b736a34c6c0b1e3a49d7fca86f915dc2a8d61b380a111c9d
9fcd6ad4e6275b604288c5d69826ef8a407fcca10cf7ee5fa79d602fdde35715
023c5f0a3aa87e80268d4a02ac17cbe880657fa32f447f9f97bf6d5a7db0149f
c6ac0c6603b1d2c2b79321da139501eff298596d75c9491903b3eb8fb08fddc1
087425a0a9327f895717d6c90731c0313c2a23687167482c9ce03e8169e6f03f
8478eb0033821c9212d66de964338eb80773e3ead2f40f6cfa6c93b9ede239ca
7075c66118b34317f2005fc410a4a02b94e7eecafdeb0dd8d87383798fc8c008
04e8f585ab1ec9d3eb288b3c657198a8c140470f6b612514fb9207d11ba3f46a
4a97eb3b408954d9ac15009e084149f552a9738b5bb3939854d24c0270997723
ef328ac16215fc4935d428b547f7b084c5d8148d3b09a4732b37ae5854b8f1b6Trust 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 962984 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 0cd209d450d76f3b70cf2097fe423e5f619662b3f1d28bd4cf1e635ba7845ec0; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 0cd209d450d76f3b70cf2097fe423e5f619662b3f1d28bd4cf1e635ba7845ec0, and the block's
timestamp proves the page looked this way at or before that time.