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
b237a982516c8a0ad65d8a56b91a7190a9490f7cf4316c33641d222fa15aaafe
08da89b3cd72d58f2b72256632328e2e95dd7ffeeba7bbc3bb7b7792f7992bbe
b9cd0e37d2a48f5db941bed2c2a92d6310d334340bdf87ae88193137dec1a3e8
d8482b85b68c18780f44aa26d5168822e94c2ea3537af23dc16d7a70866c02e6
27534b300d131a9bea5d32e59388266b4c58794c2a3e8d90099c29b54bffba51
898d0a5a654fa0eb4f419ba325882da903ed1e7604d16c4576152feb080c0ad1
d86158936a57857fe8109eaadbc50695dd99851ba754a2004240cb3ece63669d
5ccee37cccc594d14ffc1f1fe3f3385937f77550625f89feb87e3d51ff8c836e
b90dd8d84c0a1fcf1adecf2dd17beab407b664e6c3193de1bc51e556f10327bc
aa254bcecba7b6b30ad48f4e5d041b9e27b74a76a435464b8891b9339e6b42df
291ada59509c415cfa4599c3ab0d88a70b466c7bca03b85bcd97519ed9d39dcc
fc3f4d13e03a544329384c49f71d72118d336a26b85b5b7e6811cf7696f66d96
4ba577fecbc9d7c30bd2dfcc0f5cb2b0a5385e08b861e51e5de2d3e8007af273
52d6fa825398afbe8ac7c170c71ac3d06a3f5be1a7928aaa79358d0b35940976Trust 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 971162 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 b2f148107100c048522b6d43668ff0b632d46f08a0fb2b5b9c0a518ea12a0f36; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b2f148107100c048522b6d43668ff0b632d46f08a0fb2b5b9c0a518ea12a0f36, and the block's
timestamp proves the page looked this way at or before that time.