Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
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
c14dc70aba73b606f4a9dfb142f859f592d1575fac6c71e2df82d2aa75bdf2ff
d37074c8f4e8fcded8e967a198db2ac32a812353b6ef777f6caf74718d43702d
8738b2346666f95ce32c7a0ecd5c7def3ed7db59766af869a7027b78a59ac3fc
9977c706ddf3214da7fd345ba4a29e072ef98caee60f8be17daec8935d68e151
d55a1fca85d8d59550ba683f4cc6affa91ce2af61b7643d344b363450b87feed
9f93b92753e77349f259c8a951d472624b1e8d3b6fd22bb3769d41dddc1f8736
a4c6fd331f51d9fd4081225f8dc35df23eac23f28603c7fa1a34e15c6214cbf4
e985bde45ab37aa481f03fbea170c330ba3ade129edd33d59839d8bdaec4669b
8829d9d4dcb8c3dc73cb0085f1ae3a05286280101b0374346bdef53edb404a00
fd2f08fef83dc557db4fbb7ad2891cdac2123d5463e54f6449a327cccba0b108
eb9e351b6b2c9fa492a8994fcc459baedd36e00f809d2bc7c328e178656de013
2980d17cffcc7a16bd836bc687a5e12d96e8df09382e4106532789d8f31e66c2
e24b80db8ab2fef6b27d24f331993f134b354df6e0d532042b3f9d8e4a0555d0
84bd730d712592c7cd9dd03e51ec04290c8a1965e809ae581baf3a2d291eaffc
a864e77e4f9bfc7d38a79fbae4465ac84e9600eb30d0f9f30bcb876262f77894
9aa8a91bf32262fc4b3296c4b80f987b4c9d4e47200350afc1d44746f68312eaTrust 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 962296 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 b49f236a02e0766e114bff3c71cfc9ccf9a4703e3c615800144dda60c54f28d0; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b49f236a02e0766e114bff3c71cfc9ccf9a4703e3c615800144dda60c54f28d0, and the block's
timestamp proves the page looked this way at or before that time.