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
6bdebd1d88d29075aab12f4570db21ceb5cec9df1e2e98d5e9ebf0d0cb569076
b474cd31a9bffe56afad4070054ae7bf20bf9adb02c581dfe6d813cb18f4f04d
bf0f4838461a6e7253f28b70fc8033cacd752b171688d5a04b8b34e652866666
38f539d5db244b265872cad77cd7c630cd987b33d25b397f75e87a866633e1a8
67075b90b7896939b7085f2a3f6b3d275283ae831c5ed88a701d449f64c778d2
e3eb2f32f175425c27d4150d8db669c0401ddcad0907760d33d9eb2ce1f10d11
28ed19c71389a15e52e48d4eb45afbf3f52201d0f5db9bc47ad580cb7fdc3c67
43f256c8c10c0cfa259254d5f9ec0b3cadc5bf1bf522f66c27cba4f2c08a5ab6
f74ecd7fe65018449a0255cdddf6c2972f57ed3371cfb9b4136b6924d625a3c9
7485640d71cf572e44937ce964e5a20131a04682fb90e9b6e22e44c8f5f17f4a
ea53e8cfa679cf4c6809ca1b01a12c126aa69c5f54bac86206f89d06786026d6
e13ba9717f19f05b57a7cea3cccf582a0da2d0fc5edcec2fc5e2df54723a0002
28fbee840b68d568fbca32e2c84696c3f2413470f7f75b8608ea51fa12511ad4
3ed2f5a75500a60a9188294abc5da6c5e377cbae3ff4879e9faa4ecdcb33058a
adac882625f9b9bd36344daa9b8ef30c4eb1139122cf0dac74505e0466cf6031
4a5cc85905247b7d8612dc44a3d2a561f73694567dbcf66ad6a76adf7fd6b978
3cb4016f41f4ddc0d9eb5244ff10134159f85e41367218c729ccbd2de1629fd5Trust 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 966076 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 bbc412a5e96d3e0ec62e37e18cac71de959e7b04bbc6b607c15effbe69a8b496; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / bbc412a5e96d3e0ec62e37e18cac71de959e7b04bbc6b607c15effbe69a8b496, and the block's
timestamp proves the page looked this way at or before that time.