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
9f7834be39669c69ad9d72c524460ebcc60d0781625786b1ae54e61606017240
7aa9870c3f65b3ade73269352a5463be8ae51bdd9c0704c340cd6f2836701954
38545343f9d72232545680fb17c1800c0edd5d5729843515db81d0b3d5caa0bb
bd8790312941ba06ea8abc1365629865a7d473267e9f5152db4c69a7db6c0d41
57ed7d7fa7e7c8b7d7a6148867fa02f7df30bb7c8af93a1ba7bf762d8c11ded8
3cef53ba41c422cfb2393dabcfced09840996cbcd3f782c0a9e3c1a400255081
a16e44d9d24dde8e15a96b1447a68546053b7dbc256a43f40a1b188688cd9cef
64098762eb4e0251f7ed9ae96e956c8efd7d628891e9bdc01fe1d161bf9301ba
31b495298351fb637386e95f7c07401e52eea8d2774a576a60d294f8f6aa3005
b8cc242ce9ae745f549059f23cd6b7354045c2d583801e3a6839fc1aa55fbb06
f45bfe4a0239b149d44e1bab64c3ec76dcca56bb18e6d2043711af79b62d44f7
045709c546082bd92279efe77895e819213fecab881b12401ca7a2a98136d291
a6cf80569588162950d54cb59b9867a9e7d0fe51246865965324c810e6ff13c5
1290a81e31aa191da0341459304ab9cfd3ab1dd7ab13ebdb525ef39711f80fd4
97599afe97ff1d78896cb9b5bb35912b532d5d243d3e60466b8b47b2dd3b19af
375497d2074922c448126fbec8624438f7407ccd2ccbf490c87027cde5279240
c7cf7978cc56a043ace0bad5bb9689a3cc0945c616007fcabcb6dc33b3a115feTrust 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 965202 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 a170f75685fbd7821daf3ad4a792b696935a79b66696188ebb74d4063ff9f272; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a170f75685fbd7821daf3ad4a792b696935a79b66696188ebb74d4063ff9f272, and the block's
timestamp proves the page looked this way at or before that time.