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
e6100177d6f927dfa59d0a82776f4174290df05508b18ad53396547bf7eb491e
24088a737e5c98ad17947f57b3f99022a74e95f30b49a71b128b1a07e371c77c
1c643516995efcb8cb400a85db25575f17433bc05512ddf40a14839c76301aaf
30e4430df54e921389b51e8aa8ce81c6f1fb03380ef73423890eaeaae69a7e22
65b52549fbbcdfc3bcb81d4977266d24881c1ad83f7b60e05fb913a95157afe1
22c0e0fa41c6e1741f474495df67a43be7804a6eb314aa56efee12120259d685
9fb8165e725c87310b3d71b720567167007e1cf3fc75728583cdece2cd64ce89
c41be2f2bf0747ed1407774b9506c130c0616204cefa8737b95ae203c93e5301
87a61f57ab67af26069d766de702e5f33064a7c68666dd45145f4699f6aa1876
8cf65df4c106c22b858de4debbc13235ae474e7a44076c9848642143f68a80d5
1d182635d62c5adbd22fc04b1d7790b9ad2dcd19439fb4ec776f9cdd237e03fc
eb85fa003b31271d97dcf918c104011b7057a45611d3092012e90b7b4f2db66bTrust 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 971183 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 ded513a3462f39ca5c01b7771124958e697b783662d5104a68d6aca1c2d140c0; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / ded513a3462f39ca5c01b7771124958e697b783662d5104a68d6aca1c2d140c0, and the block's
timestamp proves the page looked this way at or before that time.