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
b657321a5c769b8b9cf75b8b5d07b9e6e30413e34b2a45b215071fa8a0327727
90fb8a5e7234f84e6ee8f95e4f67733d615a5c9a209bdeb09fc8a8cb0652662b
31fbed6a13fc22f7486f38e4d09b0b4cb0d71df47545e6033ce3d66679de42a2
6b27587a60157c7d960366211d867e979cb3e42f9cfa9e69815d922ccb0e0788
101c619a40f9ee47e86be3a9e5ce9f21909f5c20e43fd2178ffe1f23853e058a
b4d500750ac32b0428b0a169a6793612ebf10bc37aa589d53697ac8a6b67fa9e
245dca411050de052c0ace7f109f1c860e9a6e1da111f1d655a272330a249695
822855b81a74b12c840458fb50605e0db4b69f252aa16aedc5f6b2fb62749fb5
c40188405e99b4a7dc5a7bcd60a5ca71f11e544aaa86c4e882afe0f1f1291011
9a66ece2f84174c1ae7302f221318196166510ddb00cbc5d04ffb6c04698d822
e1ff76dce26f39e78248cafd69735e52246be71af4606a053faf53d2139c4c98
4c0d2fde6b529a1a026cc691fb969b173ceab572f96568aac5d3e3ca547f0fbc
156a7267a1e6e0200f4735bffc333c501ee12369e559e94d1153b5b5b4ae1fb9
c7b808546ae85e6302c593c3d897e64af9fa94175e5a664d0de04553861e6461
5c4f2c0c8d27547a0bf726af621d28c4b067035c504ce1c95b28e181b3313f8a
4a75747c1c180226e598eabac59b870ee8008c642f7caa54042bcd127d7d9de0
ef8015312834fb168b8551869be8cc4aff59943f578d209da504ec201a9cf328
cdc49fac34ef8d6a1fb0ddca103371fdf4ef5a024253c84d0c6ea01ab7db61fb
e172578f7984c1423427181918ce05033e447b30a8a662ec1888b7a26bdba6f3Trust 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 972062 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 89c9a8b10e93b80f374ffef014af7a214dc373b33024744a014fbbda7cff54a7; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 89c9a8b10e93b80f374ffef014af7a214dc373b33024744a014fbbda7cff54a7, and the block's
timestamp proves the page looked this way at or before that time.