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
1fa0010ca5dd1f7fc1277e35e5c2807052499e7036cc58e6268445d6b4870c9a
68e21fd1624a6144084e2cfcc8433ad13fca31380e9f0d41c629e7467a2d045d
fa6756d33be27f3112a95f08b1a7cb340e03a64c56379b8a07638e8a773d23c6
0abe06dfbe7f858741b298e1ae52fc54d8fb08b1baed6c99d283078ccadf64ac
c5e1e126de1b1204fdcb2e2865d2f9964c34085cf2320be6845f6718f9d6a122
4ac040356b12555d58fa4d94f5bb9afb8def6f39038404498d40ccb0d4c59cbd
62f36c4dda59b9b3ed7e7ea2315bc47fc0965ecf88d98a431c950f6ec393ef69
d0ef79860c6949c5d26c1230e9179b11e99aa499374f8a1f111e850efd3c97bc
30071efee1b5390702d0c3cf7f5e82e11c0248f7bdea4558c0e71270f3a31015
8310380ce0c26f39f635443d36d8e4378268dbe148b8e824c5e88d4de9fd7537
529c0d1a3b5350656e7f45de0c35fce132b1adb8e7042bf097f7a760041f1ea3
d6bbb44492a45b79119c6abe8326b394fae628923bfc1e014f560df443879a63
c91b3b8177480efa15857eda3322ceec555f85407fd4b25ef0ec14a2646cfba0
da53a9c52eae97cb1f98210cdaf2821ee68a1e8d6138e7b6ade1a867dcde2485
b46514acd6826126d6fd788f44ceb3368bc1a301f3325ae2d350a0d402caa067
11d171091b68a8045484b21bbe24d1bbaa4056d2ac1aa919e6d34c681344c107Trust 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 965995 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 de2cf062b825def348340fc526499217d79ed41aba7732b83439f582b04fa142; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / de2cf062b825def348340fc526499217d79ed41aba7732b83439f582b04fa142, and the block's
timestamp proves the page looked this way at or before that time.