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
5785b29f4da9c4d7366243c3ffc4d989ec646f5bd444eb60023322cd93c43d91
cb8b63d6228ea6d04af0969c79a48e5ce09861d2c71a1c67e44dc5d345d119fb
ce487aee37b727fdd742a741e4ad2bdcd8f7b7e09b2941a46737813f6c0079f2
cfa730b38cff046ed6781db507c210c5953b9c226dd5d25c6a9bd59d2cc5be22
c5ac32f6dfc5229f2634ed3ff58017b4c4f150a699d5a4875f6aabce8fe27679
83f18b3ed07250103b7036def5286bde2066f64011aa5002028d87b72c52f6ae
33fad98b4c9e10d9ffadeeb5daf715f4d33189a96070c1638ade784a40ed6522
e34d3294639f585794dc7e5e12d523be21031155698ce3800da683600c2a6e4c
18d33c136226d1168935ec7711b74307a15060a4997a75e2906998a71ef4ce55
4d3e0622ce7a653e65531180dfab38a5633f1eadb803364613443e6c65584c58
5c3087ed66541466dc31ff65ff61e11c0b5c5b185e832092d3abc05975224be1
4d6aa16dcbd7794be6d95c35a55c2d9d9e22a4c3e50e186860559eb8eecf7513
f34ba3b71a9c68f52622e29b88ad378ac9aad70449ebe98ec630eb7320653e61
a3607cea2cd7f2b23fd18e20e0ade0d4c2c78ca8521d127eb6cb9f4e97389618
04e18f243041267ad3d540c5970d81dedd48ca0608aa02eb8e41d93d335c1d77
9f6fee6a649cd664951e901d7aa2061b8b54cbb25111475b4923a608bd5cba33
1bed115dc9bd0da783667403e0b0cd0edc50e3ce9156618de10ab914c435c02d
2c155f0bddf10db5e1f742447d6cdfd46ebf4b53d3121f95ec246077f8e2b65aTrust 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 963790 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 04ceed20674165717936d93d68344f2c4f1ec1376769ec5382d84c6299397040; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 04ceed20674165717936d93d68344f2c4f1ec1376769ec5382d84c6299397040, and the block's
timestamp proves the page looked this way at or before that time.