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
777847dd38f544ccce6c640ca3d5a36c92112f6c76fb7bb4e9e03eea571042ec
a755a7a0d9359e1cdc7434b945e61d9eb9c5e8f31c67b6c8fd7830f302074ac9
3253724345ff0fbe8a2de96061a03c488fa35225a13b8a270cb40bf10ac309bc
5f45826d01f7a9a8a6aff244d8e2d5287c1e026d47f53d9607ba6d34100f44d0
57774b216c2132844fa1f832531baae1f9937d73d5aec0837d36a58097413d00
8e719e569301212258f9eb3ba06e7d48de12ecdea3a9d0fdec4bcfa59fcd8e55
604a48b02526ff4b9c1ed4eba3cf10e01e817a8cc1c9d628960bdab90469a1e7
5f415db9df8efc2327d52d99108d1410c2e4ba40a85484b5478cf6b714fb242c
90bee833363b81bdb85a4d96be0c6fa1ec6a4c905bf3067e845a9ae09b0a8920
b36215618cecd53bb1bdf67af91ed26cb1828c5ed10509b271e83233fd58300d
87dae176bab870f252cb61d583bb6dda3a6b5be9884243497d283549ec419d5aTrust 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 965859 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 d6c25323fede3772f7168fb24c5d8a41507e03f45dcd7fb3ca2cf5055e26e988; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / d6c25323fede3772f7168fb24c5d8a41507e03f45dcd7fb3ca2cf5055e26e988, and the block's
timestamp proves the page looked this way at or before that time.