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
887778ee0e4d19a81fc243fc1ff98bb14032a5bbcc7b64eaf66ba8b96700c4c8
a6d27d05e21f08ec2856256939f432f1283b0ce44c4600e3ca63e99ef9ec8bcc
91112e5e7368bc07c76d6de0aea26589a64b4ffa6659870e75d19cc106e6bf50
11f807594f91ebc8810575a2345b90efa8d4ac3fa57b8114fcc3492a6c167b6a
b1ae89ec0e21f5cded9b54e8fb30cb9c27f8655023f698f1d7c5a2092458c861
26c674a2f9c6504323cfec4a636d1ededbddf983782e6e1caed1ef457422be0f
5613ec55949213491f5f50d758e15a4ad1aac3832bbcada7d7f081a034a4cdfe
59532b4bcce62dc6e745028b7d5863477273feb7ae42b02575772690706fc5df
94c6704ba6e7a797f3549f86c173e9e21604bd28ded88b041a303c279aeb7cdf
efef94c8fe0f663062c98b6da086c2463912b8f32db9c8e88f0b520fa6a290cfTrust 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 962211 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 05ead1e2683b1ddaa3ae2234644a59a6ba69e41fcb18e09cd91a724b51836611; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 05ead1e2683b1ddaa3ae2234644a59a6ba69e41fcb18e09cd91a724b51836611, and the block's
timestamp proves the page looked this way at or before that time.