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
04f49d0c4a3641d1396eb80e58bb71ee97a570f164730a926886e5f6e8f8f5ad
45a37f6cd92549bd81e2df23b71fdba654a84c104ea8b2c2ebe13aae68ee4fee
f0c031cb6ef42ad08fd79a90042eaf2f9e0a0e6ea12be0b832f75619912bfb90
b93f6946f303e895bad8d7bd85688b4ee52d4553b87ab7ebed52f2c183be9856
f2dd166ca9d1982eaaff07bea69209ae553ab6ef6515664603d2922d8aba041e
c7dc94bdd28c08824cb8f31f4a5c53d38410993240c445d684c2692a3c8aacc5
013836c52c35fef92ee423798031236da4c1338647669907d498a8853084a9f8
2f52792941c528734bc98c6411519e75a80647f368226586eec06ec6c0e1e4f4
1ae066722377a69b3c75558e45f9829d8557f0a52cb6c4091eaf22d8bcfaa465
e1926ce20a839afe917b6c28368f9eb4d4c8873eeb5bdc0b639840c41c628b05
d21f7cffabcf18e0a122a4eabf582dd50fcc45e85a77b958e5bcda3c0ff64b3e
a60b66f80c4bf15b136e79acfd7b11cca9903101de4e28dcb48bd9fa56993365
c2aa5605c0c79dcb8dd7b84731c60dc79a3f95f85fb4c8a0fba915f8032c147d
dfc24b023c0438f235c83e1ecf472b4daf7056bb6a46098498a7ed1ce9192908Trust 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 967999 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 3cfd2ff002d3b1373253111bbaa2786c0d67489afc8df72fd2a4b3fcff75e219; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 3cfd2ff002d3b1373253111bbaa2786c0d67489afc8df72fd2a4b3fcff75e219, and the block's
timestamp proves the page looked this way at or before that time.