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
4ef694116296d86fdd7e580af8ebb9dd3bc0a0798dfdf2f80feb9028d05a072c
e64756f031f85a496da73306d88430497eb7f437dd4d3e24d6f69815c938ffa2
7fe3484affd4f95ee52a0731f3125a25fe370bd22806045fb86e2543a4cbc20f
6023f608f20a3d4b8c4355c2beb318429cdc1c1049de6fa5a545391f1b85c8d2
00409e340b0713b100e3c3fc567e1f5a934c764445ab5bd3a71b93f81f3bf414
ec956463269631de63e0d2bc2bb1d3237df85400c10f44a716f1d9afeaec288a
959630ed4deee96167bd37048220a6a41bad3985f78e31a5b5cc4dbca3b6687a
7ad43cb7d6fa979209b3043111aa294ceebbcf3bb4026d4f05211472c561ad70
e1c43b382a9469a8b51b864d29c8ab02df399e623ee747d9721678290d34cb33
8d8ce35d99fe5f4bd72da4b8b2a49ced437b27ed5cd021c018e1e89ace35e936
3e5a58d8932b6ccf6a65c159b459678b05981e06c39f3c10ab8989007417d76c
e98d01ec1a57aa46ec7a55e4200636879b4ae3615b4b9133e63cda103fcfc1e1
d894c6d537c64979e151c74ee338a754b0a600391b553ca37aae9bcd041ae73a
bf6cc7c4e3f7bcaebca4f031bca459add8b743dda91aa79f4ff04d9d6c5e1b78
12966377ab82c4d11a3ceeecdd868616be8b3c9c0d16fd96e1b730a077f1316b
5c058125e777f9dea3c0b551f41fcd3bcea95135a1dccb463b3256d55f7acbb7
c452a16b03df5fe6db501506e2f2ef8b998a441dc9c688f328ac31a5d502bd24
8b036f24d3219b53adf4423be665ecff6bbb7c806d6a1ab87723bbabb0ffd3a3
ee01a27b4d838af1b62ffb32048db04243187eb36a1ba218ef6d079243e262e9Trust 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 964700 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 97722f9e9051ad7fa0c2f6bba2e990f1cb71f3feb5b498ae542e130ae7101920; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 97722f9e9051ad7fa0c2f6bba2e990f1cb71f3feb5b498ae542e130ae7101920, and the block's
timestamp proves the page looked this way at or before that time.