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
36d45e9056c1b15f61b19c7a33d19d304bb1209bc6097853c314c48f1e95f9b5
79f2a51f1d1160a2b24c209dec55ccc77f75a31b3a80357649fcdd8ce4527072
aaf1a14e285363798ee72aa7902b9ccdfe78ab5f2e1451c4dba650de43e2949c
b8c4f58ecd1f699798b56d58a101bd4cb9de7cfe28e9906ebbf68e3cf6be115f
eee2215d84f8b504013605e3155ff6c5b2108617aff7cc352499bdbe83bbe456
a767647c56a433ac75a5541c148e132ae631f525d97f19c5cb1124c04559f409
9642a494175e2fef27dec83fe500340a4edbbd59b8e8873c3f52fa0423bca93e
b335c4d5dda7cfa3c00fa98d67c64aee48b30b3fee632b2f76db15749a82c62c
577ab48bc7c8766388261d778d8fb44abffb0290f9e8d086891b5dcc388c07d9
5438eb43f4e2dd11a81705d698f89c71914bd7869cc58f905a81b77283f2b14f
f52858f1633dbeaaad1d5ff6a5d2d3eb3218f66bed80e539365b45fed4be8e7e
b68fc9f2bb5efe7ebf9f4842e344bda6210d99a532b3233fe6d43577faeb172b
c2825b772b1b31ee195b0a6a33e437adf0d7a15751c19b980ade0069ce2d3ff2
1246035ae0103c0a6727c54ea57882c8ed52782dc4b90c5b493a4278c70e5872
fcd2bcd0a2fc5b380d01403ce1fcc46a71dbfa740fd7d2c3a02fa2fa3ced1474
97dbeffd4e1af6827c9df0c49cbd2f9bd6c8875d1e94c3ecebe063b1226babd5
ef7347b5ec754b54bf9773c791884c967689e7ce07efbbf0e650b48291473324
71567e9eeb6a64ee558ed6d7cd96df99f03762aac550737f98a4f9c937a7dcee
27e5a5119c0b1160551b7b1e073aed14e5d61f781856ee935f978a491ec73620Trust 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 966720 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 1c65d4f202a60ee44512e4ede001e0f902fd42047c1e8bc5bd7eab5aa4e7a85c; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 1c65d4f202a60ee44512e4ede001e0f902fd42047c1e8bc5bd7eab5aa4e7a85c, and the block's
timestamp proves the page looked this way at or before that time.