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
79395cb3bd6543842b0e3705edf5cc576cafad3b57bc99129b7b754454012327
014337b39a42d5f10648e138d2e8378fef6279b180e22a61aa3513e94d8653be
4bca3862b0717437cff9724ab756cc36111aa1dce4c5a7540072f9e403978ac0
f8c8c6e17844be53898487f0f7db5d898605496648e434f576144457bd5e2c76
1df05fe896e12f36bcdc6a03f00b1516f8fc28d9b0f81fdaf850c7d3d6916861
75ba6061a005e3a0f045102a088a8c6d439c4eff27709f6023318b4fa53c85db
be1d7f910cf51dbce80d33b8be10acba880e400b3e9b45c6ece48287131add58
d03d3ec9a1828b3586991b851c7664ba4a19fd2fe50231408c55cda8854ce59b
97e2a3fe6a3eb0199fb429a2f75a4d0379aa197c3f1066775132b03918310b23
2d8da347259c7fd779d9d66015290bc3fca7b7ad17e417572ed752b0807d6c9d
2eaa2da4f6ba5d2964426437c48034c07f14bd3331ae9305f8b6615956e1bff5
374b6cdd2e0e6d102a07545fd42203360ba43a4a6b667e95f6fd714650eed90e
14fc086e4d0b94eac1f37a925061f4eb11f6d5c92ae42dc1c2e0c2024cf4ea32Trust 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 962061 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 b6838e9b7d9bb63b4991603891167cb57b0a8ad70fc3702725482a9f00aebd43; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / b6838e9b7d9bb63b4991603891167cb57b0a8ad70fc3702725482a9f00aebd43, and the block's
timestamp proves the page looked this way at or before that time.