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
26a353a4254b234663dddf6016606976d5f253c0f6db25fb5f5ed6e7f758dd04
f66275dfc7dbcb03a47a3f92a9b43dd5d9f4365eca4efe1c9a84bb1f971a9cbf
67ffe2d399a812174a085f35a40a5a9cc73670d3158056e2ddf0f235520794c4
277f657deed04c8f0a75d57d4e5b4e38c61709a27e0a7f2cc4fdf7ea58b14d0a
2bd9df4416d9b3107ef4d734884cc46d5626ae93b80749ceee69f101c359d5db
baeab39000792143c03d402dad405f1215f334f972135269606baa7ee3b8c1f6
531901f240ca093616e94efe8f5ca7758715563937d7a329bcebf3ee76a04aa8
f1714b80e0a911aa241d5a2a80087251127931c26bd78d7cd22832b0f6c44d53
04cd92dc45130266f315cc32f9335cdabb75293a99b2f8460256f6094e82e02f
d1d66d47837cee0e59c86af15567832a595f9fc7df22fcc8f9b501722b503173
a6084c86b0e886744e0376ab25b5c3de3733af9fc978b65cc24332ba43af0dc0
c2482e49e290beff7c8853a511bf3c0053e51af07d2671bf56a74e59e88f6471
847df203022830fecd50b289ed75b9e103b67267c9e422557e38a03e9776e84c
7bd751b7b9eccd5a655bf46d6a3cf118b6be8da368e6f1497c9a1b21303641b3
8518a222ae6dd42a35350739684b0d93633fd0e26540a34c9cac307e9bbd999bTrust 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 965083 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 be4017770174b7a5edb3de95bc268b284a128233638bc7f547ca4c663473d0b6; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / be4017770174b7a5edb3de95bc268b284a128233638bc7f547ca4c663473d0b6, and the block's
timestamp proves the page looked this way at or before that time.