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
22d3aa455bb54f0d63348dcad9f6b4e416c52d19dac9b5c38edc3c2ae0405001
86d0204d897fae97af11da5930e5b8a4a882de05a456fbc36a8b368216943575
181c2458b7011259fce47a1e3aacf4f84853b556e728675e199ee7a0b7c3cd9f
c3d900fc318a653320ccf9c5e5ad99049a4102768cfd6c0bc50c239d2ecefd4d
e81a93bf63f8a0791935a23cea2122ff76a86f5ae365fead7204d68bb2153f33
12fb9f2bd5d8d56b9aefac2f35ce24fea1de2aee7a551638af8185b5edc6b10a
418654a3f61f23cab18f061454f056810154898aa6026791260870760529e6af
90ba7b8ce0f43c68cbd610b555a2cb9ae332c181a8b1bd776f8f00c9253ce4e0Trust 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 964021 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 b023598127989c7a2e820a721a0407d3df70be7f324e2823e1c9e0941d9c8844; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b023598127989c7a2e820a721a0407d3df70be7f324e2823e1c9e0941d9c8844, and the block's
timestamp proves the page looked this way at or before that time.