Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
48d0a2ec373fcdcff14982926c9367f99fa1cfbcc5e89835817d2ea3204e35c4
72325143a2d6d42f5456e4e9c1d658dabe022b44cefaa68cb592adf999c864d4
8a26de546ed8077f9c390197fdbdd64b136018b382e5b0876782e3fc5961225e
925860e350b04d0daa0a40f239d54ee7af4838155f6f223c411353ee0be26008
853ed49f93e4ad0ebce5cb46514cb9d84cc3e3bb8b13de79fc693a56c33525c2
35d5d245f74a11332c300a3518e38d375df0749fb0154f197785f7e31a084468
2e453d10ed750f529b59d263a95fcc42fce8731cb9c651135ad496396a8a3a3a
fa35d491d3a3e9161540ca3e192e10082b71159c7e7e7574b23a05d5be87784c
48d6973d9ac4bac9fc172825ae1bcde9dbbe81050f2919dd1094ef86fdfb3650
95b96b14d259be2d4283ff00b37e4219eec9a14b4427aa94a098fb5dc1bc3004
48dd32eb9b69260e63aed01b4f56321d19df9595c1710210f17f264a14af4e2aTrust 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 965621 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 78a79651358cf50ebbaaccf495122085141cf729dd93d12839c182e8830abf55; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 78a79651358cf50ebbaaccf495122085141cf729dd93d12839c182e8830abf55, and the block's
timestamp proves the page looked this way at or before that time.