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
9f1cf25e15449657e55041e1ed83dd522f2c5eceafda64d95b5661f1caaf17d8
278a9a83ddd18eb02b02f849e17a374357bc08f23dc040df707f5d227d316fde
dde63100e606c01aec1bc70f4792dbddc529fa4e1e68f9ad62b6ede80181ef6a
9b09b3b019f7533380ee0981ad5a36f6ddee810bf25b612531cbc54f8494176f
b1700b2dbd54723e6bd5be213d8732771a495fc734fba11af40af0f3d6d03546
6ad99ac8a45dc2e49609944bf2c058af26766a0af0a515e0ba63dd94f767f75a
404a9811b50d1a89f5857214dc8f888dc053d39f0399832d5b97e11574db8741
a82bc6c13fdc494961ac005173af776ae0c9f08db03cab6abc4acf8bc6a30325
31b47f16bb00f397e337462073f1725dc277cb3496915dc6c4710b688d81bb3c
26673a0114a6bfae4d7739b06acdbc9b25ed61ca51dd311b39c5590a75f7c4ce
62603690e3da630ffe8d54e3e2273fa044a3eb4faa89d1bd1463db4d8004e322
e5f9a3f01a163002ed03edfb82b1c1060980ed626c4f34faa41df1489dfa2ff1
7263e90f822455544ddb1052ca523dcc484e617c1e92a559bc115a292b011908
136595d2fb1754c52593909ab60e51549f6d4e9de49de5e0db6c66ff8fd261b9
bde3e01577173b4b5069b1d84130943c6c7be9cf9b0d0f1f8b9e1dc4a5d2079a
d4019070e2ecbd86cf6adee49a9e2b2fb4e70497ff5d296c8a0bf120aa1af080
c128074099592da7f7b6db8b273d214b5182fd91f66cd853e94d5ae712e7506a
9591a80ea49a8033d701ce25faf83d3bd733cba6b5ee0abe85c2497baf2d07c2
b24af918c34dbf2c22aabfacb5542f86ceb11834430b0edef54ab13bb2f4bc26Trust 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 958854 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 b4f507e4d8ee177035f6796f19e83eedc2c5aa25b360c1f06b7dc46207e38be9; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b4f507e4d8ee177035f6796f19e83eedc2c5aa25b360c1f06b7dc46207e38be9, and the block's
timestamp proves the page looked this way at or before that time.