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
57f02d2ad920c370b5ac64f6a3195095407838a8463ad3aeb04112f8fc184bea
5d4172c85268e096501bb2162f4a81ed0ff2d79cce1744fe6891015c0f89d310
c15425e5010cb30996c1e4d5420d4154b0824319148beafa7c9fa1fa7b71192c
2ada7b39a994dd6ec7cd7aefc1f19be68b9710efc7b2ca02a36a302a9d6ec2e8
cae16b876ab499654303bc905d8f87396219ace4b8639d7a323722a00b521c9b
abf12401ae3a1125345f0125fe16e3eb76904533ce374319738f08812e67945d
bbd6871265ad999f6f1aadfe6a1cd2e20e22919ca83c633969eba6c06cc71d66
25b45c1e68ef67e158ff79b96a80944d1a8953057870de7e868572a8a5978149
ccbeec5dcdab9aec4730a8abf217c2005d353c6d2d9aacf7e16e352c13c447dc
85b2084ca5baed36e000df44d19c4340cca555de8e89ba9576419f2fc606b27f
d132852196f50f3b5ae409501667501f5216d13e11b6b8d901eb73ec9c55064b
*
7acb60421c02b57e4c3b86bef2c0c74851e9de0ca17b6fb31ce0d10eaf6b93f4Trust 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 970099 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 b341758791f8bc7daec1e7cd91e4dd40ab02c2da9f454c538c504a2d438b5e1d; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b341758791f8bc7daec1e7cd91e4dd40ab02c2da9f454c538c504a2d438b5e1d, and the block's
timestamp proves the page looked this way at or before that time.