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
d803eaeb57329eaaa043f261f2b628ba0b63a45adce2a14dfc1909b0775ba4ea
c6e5f75959da8c6f72f310846ac4fd5965ca7f5f9e1bc6c4612553705d39716b
5abe23e44e3aece6a5d7fb314739c4081b7330d68436bc5ba103fe1f474ae499
a776a7f490424f1ec46ba1f881ae609ea25c360300cb341aeb6311e4176a1275
ebea27436823f19431b8a00f7ee30367b6cedd17206136cfc51ef815e5a9ebcb
ce5209eac28155111c88da18d6315db9b5218a5d63e3f0ee5658c12218db38d7
ef45573a0978da7566b9aa2ff9ac0e699d952ff186997807ac25c481879760c4
8b97f1a964a91c9cf23e10164fd670fb7a58d067023031d5c47226a955c9d690
ab9974475876409bd9ceb04dad8ae4a78019139f48e5078e85dd074e4ddf2008
af2c321d7aaf3a98d8600a3b2aa422dbcf5b82d8bd55ea565fc17c34d2459bcf
c9e3817114bafdb5853807426def9d8bed73f1a7f7aad4476828ded035b32821
0fb279e45edbc83155dc7f34819d86a17749d7c1b88b2ee1d132a39a606066f2
8cf9b6c03c2fc833bc037db2f28ea6ae15cebc575f3f71900ce05eb836f5a821Trust 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 971206 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 dda54d16d99ab701dbc85c258ba3e9b2b70a1991f2d722ec0618a0197f49c54f; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / dda54d16d99ab701dbc85c258ba3e9b2b70a1991f2d722ec0618a0197f49c54f, and the block's
timestamp proves the page looked this way at or before that time.