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
fc5a4e0d4fe5a5bcad573a45dde94561cfdbda5bdd7fe3ee5a5e9ccb1b9f7d43
10dd23a8dc99dfb5a09da1cb7fb8ccdf2ed12746c62abe46b8b8c9b2ebfc0404
ec25f4f2bf62b20ca171396343d27f77225ea4ee515eafda69709bbcd21a8643
eb3ad206fa6451586a96b804fb2ad18067561a0bd166e9d9cfce53c901a676c9
2b07880d62d0b666deac068eac1bfa31487a2dbc20b84b140292bab3b209a644
c41e6488f3a2b00c13973ad3e2a744f1e6bc88ae92c45b04e3bf13154de2c00f
46c3e0b348c3996545d5db774fba58b3696fc1427fda0c198dc4c301782107af
f949e9a7316224b8e42be743fb668d1d540fe55b1ee199279f29038b172c3dea
977e01e80845f80b9ee7573d6790c3f7f2f1a8a12f5ebc5cc0e498801de698c3
628ed546945656845bb0d580b07ac086bb70980ac43023e72dca61db1c355437
893182f7d30b16edbf83e318d3bd56f2cf6e1e6ccb0faa07b1ae0b7c0072c574
525e195e1f52ea4a4acf952dc40dce7c54b53d87022070f7db9ba15efc3f4efeTrust 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 967658 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 2884c73750349c73fe369b3cfb73c83c84fe2ae44cb6b65dc836540d23d5ba1b; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 2884c73750349c73fe369b3cfb73c83c84fe2ae44cb6b65dc836540d23d5ba1b, and the block's
timestamp proves the page looked this way at or before that time.