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
f38d52cf6add1891e2bba7647041efe3ec835010969b3fe9275c983ff0ca141a
3a013c14968a4ffb7e81e0bf8fb75947bd15498618801b85e484c0f1bfb0088d
308f311146de0ba3f4b1a45cffc1425ead4592c9e474a14df91607b53892a233
9174bf5cb76635e1d8a373187b578c17131156be85bc9de7a04d49ac5a9fa038
58ba1630e06e3bbfdf6ccd24aad7b9fa387ba74fe465faf94c2ba4367331e9ef
0cb8a5f0dc119d02eb97152154558061e616d92dccad7d0d8dac140df63e3190
599fefee077e9ffa673a5b83cf8792457f00cf771363268a27c426b15cc06f82
363f1fdccc1312bb18e72812c7b02b1037184fe1c817f6e2aeca56310e00b339
384e3fb9b45a68cf03998a6f781de0d29d8688e05b8f64e07a6643bea3918452
04d227773043d2e3de54c04df9460cff47034dc63245332c64fb5bb73a0b37ed
04ebdd833ce73809eeca380deb597995dee867b392e74b93e5fef0ccaad8a513
b4f0773a4200669c5737e353141c96eac734c105d2c3e11548cc104a44bd13fc
7cd40929c654c8c6b4700c7b9b33ce0e540ea84649cfc9d49d8921129f19fb24
e6a6afd1595ac3db4108466fba483d638ff6bcf24011c4b312ab2d84e9b52a57
b4a7f1308bf3774b061fe39b050db5f7f28565fca0bf340b1e2cea93d184e6e9
7819d2a6247bcb07fd6f0f27f6c19ca311e27340bb660812e70fd88a33d874d0
755ec26d0698e5793ace24f7e63ab67655fbc44cf3a17651d4fce082117a276b
12a5b9c6d37d136ead52f0b6af83ffa2a74379ba49c84e14d2b150aba4393e9dTrust 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 964330 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 d13dc2362baf6fc1ce3d9376322c9aade7a96f0b34d755e4a581b54555059ad8; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / d13dc2362baf6fc1ce3d9376322c9aade7a96f0b34d755e4a581b54555059ad8, and the block's
timestamp proves the page looked this way at or before that time.