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
8f7d3f2eeba623586f07ad6c7edf6999406bcbbaa4890ccc6c7cc3e16a09b186
a6b92cf7dbb2b991887b854ffeb889c6a707b4acea4fda86461086acca667560
f570beb8d35e2ff9f9a8880fc3a950afc618ec629690126523928d890e9bbe99
ee4da515d3c61e58fcf0acb20f36c16725970596f7cf1ccc7f7dad69d03cc7fd
71109c63bdb27dddfa627d32620698d3fefbaa30a820a6b27bc6c59436443df9
93441e4baa2ba475dd385db68f85cd39192a523172c7fcf98e7d4a03a3fafb72
c2ceb81ce40bf594fcf08861aff64e6a142e60bca579f2856e6c66ff0ef99885
3f53e129e6a297184ed5e264a7ff7e01bc3bad3cdd5f977e8dfc8ac263c92221
eac39f1161e67adfa36bb2ac02df1d8fec479b5280847d5683ee4e646e6de921
4b71244effc9e4721762fa0e71db0cf4ed4d6b12069e986770e83f26fc7738fd
d1faa8b7ba5dfe3b8a3e173d0bfd972648daea535d8aa66080ac4eeb44896d95
70cedd361be56856dc8ebddbc3c7bd5fea75e2a614bf9692a28ca2b9d4205da0Trust 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 971121 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 ee4c8de11b0d9a5ca11ddd7871d29f0cf1a11a52a6f4bb884fedb9d1f7f2cbe5; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / ee4c8de11b0d9a5ca11ddd7871d29f0cf1a11a52a6f4bb884fedb9d1f7f2cbe5, and the block's
timestamp proves the page looked this way at or before that time.