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
9cb271a912a6dc8538b3ee14bb662d1767817e45fc44a83af5966bf89406a2de
2cc9778f7fb3920146af9b5c7c58a66b501a02cebf2adcfe05cf937a7c1519c8
66f27348a911df8cad0713189d8f037963300bbd416a358abfb439d2bde8df24
b326b566899116fd7a97332d593225fc6d83948a6f4a34e0cbc14b73b40592c4
50448eaab577037fbbcbef6664fda224b0e63cb4c4155d401af2323171df91ab
b881d329291e3ee84a29209a4f3fcce588080656765b9698b16d9a48909c4baa
64c62cf6bd696cbcaeaf38a3b007f840277426cee4740ff30edfb6cf11c77e45
9b74d52cc791c7301b5cbc16e7e33369209f0873ed4ea6e8e2c922c1f9c04b12
82bbb0baf0d14514204b18dd7ba1bef414bd931e7509e89a146ced9eeff6ca2b
88be805a224c1eb95ed0ff11c4db3c860ac125afc03fe6392c206116b98df55b
88ac0944d63c57f6933ced50d2489f31286932509324b8dc2dbe8ef07c0ac573
353b6bae963f86455b88ad0c71be60410215fcf8056b9ae867d1b71196bf5eebTrust 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 970384 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 4fd45ba210d596da1b044c03286be105ab4ab5bbcf16a2acca8bc50feb35c7e3; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 4fd45ba210d596da1b044c03286be105ab4ab5bbcf16a2acca8bc50feb35c7e3, and the block's
timestamp proves the page looked this way at or before that time.