Web-page notarized
A tamper-evident timestamp of a page's content. Verify any proof — 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
39d59ea652553f471eae43f369f0b4170de4ac69c50a0b2376ce25bf56f44cd4
68c942627901d50ffcfb2050065a1c846871d99e32c9dc516e3d856df947f256
7228d0efe7e032d09ec9558ca05445c9d9e850c276dcb1c18412d0b984d37027
e68ac7450bba3c5bfece477b932ef72401a458c92b263e8a9d40c117c5e7aefe
b2208fa7946aa4f6f57551bf758707822ac8aa89d2235c05841ad41960a02e98
7d8fa6d331bfe803103600081a089a317bd68e6307da8547f3da5d87855e6df7
b6243a3dc6e46537204ad5055e066ba25fb6249342eeee258ce76c9e4eba223a
023a24843eafb006ee675290e2cdfdcff72599545b4f49293bed054efaddb2b1
73a83916cd3d6e1ef9e9f8cb0c11e10cbc79b283381d7c8b28837895a3f7f4d8
7396a079d63d4be7214d05bac2a6c389f7774f7d5cca05d9f963ec14f11f494d
1cde4383006819c58949d1e6d9c921c5d36db09555f8b2966e775a9ef7f8b113
d6b042d2715872cb1234165014f178ed8d56cabdb2bd4f26617c034941eb99a7Trust 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 962879 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 a9ab5a81c99d5370a00b7dd7354687369eb0613bff031678baa201cc46343b57; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / a9ab5a81c99d5370a00b7dd7354687369eb0613bff031678baa201cc46343b57, and the block's
timestamp proves the page looked this way at or before that time.