Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — foundational services, anchored to Bitcoin
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
40913fc1355032b6d50253fecff5d1ceb0732dbbf9ca5fb0fa1d14b00ab87f4e
de6390a1c6ea941e998bcdcdcaf27a6008a9e24092eba1a2300b3635eea8a287
7a00c53a2bf8a29d2a3eb7c20ce7aa8aa80f636f546e26626653ca7e309c6f9b
5481920a0a7d5b58d54624e6f6fbc612a43f6077ce5be6ede4dc3605920f78a7
5273addb055032255fea7ecadfcac02ce702fb267e610f548ab4c0f4942cd3d5
71ce85ae9c1e92859ab6febb2566f15eb23578d3d69cb810df47f6628b6481cb
52144d66e309ea50214135be2448c773b026ba0ad29bb7c8f58ee53f9da3d9b5
6b1bf8b9781821a3ecf3599b92b10b37db3f9f4143d32a18f28fbbc1ca088ee3
a438a4ddff56307ece72aef6ed5957b36e3f5c9fdbe7b2271a4d4aec8c0df997
654899b6914067281dda01ac926bdf064565f259989a70d2f9ccc79bdb5ca6b5
6acb86a9e5694b14cbdd7aacbd968a7ca16439a0a4ae7307ddd25241cfabb559
7fd040f667f01121b741db3cc8457823333281a9024bcb8fd624037a4fb943c2
33a4b7c76c58bb7b0058281f89d04d3f8e7507a2db940278770b60cae670182d
70247ed77ed8152b9260af2c55da25ef1c79adf308a9f79416462e7d96789c4e
a0c46bcd674b85e328b414598e349e8dc800c615fcca7f1a58af2063d98f441c
8738ff87850631e85c3f2b6fc12bbd3866470ea88f4eee67290872b0a0898f62
d524848e2d2fdeb4557a894566ec3a77654539904ccd1c8cbef01a581a727f48Trust 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 958853 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 a824d61fbf411a639386b2f4a8495f9935f3cd9247a1e844d674219fdb0277b5; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a824d61fbf411a639386b2f4a8495f9935f3cd9247a1e844d674219fdb0277b5, and the block's
timestamp proves the page looked this way at or before that time.