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
06842333f63e56034ba2b36390f0c6aae565705665b6fa339e7d6f85f42cc90e
d3ef8b3677eaddd2f06124141a1ab72d480a9d459789b31f249fa21baf208464
8e2edac69f97bd900d01f7b095247f7a9e54bbd59466cd6f7fba7cba0fcb8c84
4a09b018552364874008026afe0f67f389c14abf9141ca55a242e4ac2da8ade5
950fd4a7dbdfa614a5a6b81efd75cf92bcef098571f01fc671872ae398469f92
457db38b1585b0c17f8da4cb5502f3cdf2face861356de2dd13bef313b158e1a
7e962c78d5da84d5a5258841add3905e9e0ef91712fe17810d7bb2e3907fb02c
779bad124bae071be687c08b4ba59fe785aca77b9604594de389e8f5cbc4d3e4
939c3a77b16197cf7903fd245705b5249afe65d8557aef12463800f6fdf25d80
e976d4c8805cc2803c773c0b3072be6f39c44190e5560ebbd09b5570fea2c283
c783802542724d380747474d438129155ccab07582f6f6d92c9041dfaee7f707
a47c418b1371680c03c5bbd1be1f62cd9eb3936043adf0855fc53bc58f192efb
4979649898bffe7a42e85c16e0fc06d931b96eda6e5fe4f95cd68467d107e3e8
513d884421b2548d20a7ccb326b20139557eae40a4e7e56fce33fc204d2eb8aa
9f69f92656f41980e6c4214148f161863d0b45223c2fdfd696ac6db6b79df97c
91e507590ef51bbca3f50c66ddcfd720e0bf1f8bafbe1e6a11df5452650277d0
62131cf2fe63ffab8c58d8588e9f18dba5effad70e35dd07084ce8c4c8578b52Trust 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 964915 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 68a7580e88591201d7725a3dbe400d55d7c484448dd6f1981349bdc23c88590c; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 68a7580e88591201d7725a3dbe400d55d7c484448dd6f1981349bdc23c88590c, and the block's
timestamp proves the page looked this way at or before that time.