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
67fd6f8c795c1bc8328b7033aa30ebc950aaf66ed66ecb1fefdda3a9b8d05d6a
2ded03bbd9e8614c6ccd8ca6f06b074b6218366c38e8a897c850091eb71edbb0
a7c10e091b9ac3ab3ef577990d9c8310ce87880d4f117e94f1062a39571ee899
680b66592ec0ddf6fab9f2153ed59f1cae1da42f7b2bb286b635ff5af895052c
4feed4f33ac84bf8da9df97c850105b0fb485ded2f98db2bb753a27d1e4ecf95
89cd8b6f62af5d0323b593c240416afdfcebd0942ef463a02e0bb7d1ab12c51d
64522bb904c772cdb7b10e6f42415d294a82b8525f64a40adaed62ab3ecacd8d
da4c9afdb55b50f06e6be3994f2c78900003e9d7cc2564294085caecbb7cefe6
18438634eba2fbe82efadd4f6d30c63801bd4cfe2d7bc295aa667e745b3a58feTrust 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 963821 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 fe9593dcf9f40a8c288f1b9e17c634befaa3cb252bc555e079a09961316748c2; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / fe9593dcf9f40a8c288f1b9e17c634befaa3cb252bc555e079a09961316748c2, and the block's
timestamp proves the page looked this way at or before that time.