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
b422ba05367a37db6df4ef55e7e05d00fbc1d8f917c47e5a0fed405c58526e17
2c7fa605f8a9249350f8bd7553dcb8e94d878d216de5d0b4f8a949586c9572ab
882c8df513bc223fdcc673b19f5f800cd264d0a127d199b47d104a1a7364c433
40f611a1488ff7019a2680e5c8671607ad088262c2b2e4b2086e048942b0cf0f
3c3ba1cbd7e7adf1a4f075be273886edbd504826d9c4f5851860018a133c1be9
b1d36a3b6a990bc1df45f9807dea19e6abf0fd52294a89185921b819daa82a8f
551b52f306756b1cef94a08b318b79d4bffdfd9c0991f4f66afa19a9c06cef33
d8dd483e9d47581c0c06612d8002af2b321ac2bbe255332273c762e79452a444
d66804e2d5660177e50ff4be7177db34c2c338c6c12d0103abfdb7d3cdb0e1d0
aa3f28c6eb6ab64c9ab2553a3634596dc6935a9f25008726715d2bbb5b398634
0abfe3a14e88849def79bd813f05a9eca75ce598de9ec5281dcbdaab23a52ebfTrust 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 966285 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 489fa575ee9232f410db661808ed033d7f49c8c4e38483a2483362a5332ccc33; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 489fa575ee9232f410db661808ed033d7f49c8c4e38483a2483362a5332ccc33, and the block's
timestamp proves the page looked this way at or before that time.