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
4de8c0866586dd897570a1b5d720e43324ba63c98bc6346693cf72b5762679c0
869ae9be12e48fe297396b2d93060630ffdd3b24970155aefd93419c9a5c71d0
e5cf3530ae58fd9e9b16648cd5053f0d8d589747f63be6f5b6eacf952a85f11a
9c1a61a53acdf2fd3331ba12ed02f52568adfa1b729dab25ade064965827ab8c
e8d8b53b2cb71ff4d77eb7040ea514e5fb04dff680ca4d6a3e6182e3ffc4ad3b
ac4d21890dcb506ac18648ce01cbee09dcb772c6d28e3f7be16489c33af31fe6
c271344dab1f84f2127fbe5ff2093e79efbc98f36d0886b610dac6246208b466
ad6b29966f925ccf033156a1c6bfb5d24df40b3b37e85cedb23fc36a16398cd3
3a36b269563e9efcc10839afdb512d1e30e771e82b0c56e7afb1b45bbd0f91e1
5015b89c87924c0cdf6d903c739ab5e2b3792b75800c8030f38a890a724cf95c
86b06a54f1d06c3d45bf7d22d8c04da9813aed33fbcbe09e304c9267e9491ba9
a117fa0819fb12b6bbbe16c17dd5238ef27b46cb796a91af7d4d4d3a924bed1eTrust 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 962855 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 104a064505dd3db09facfe6bab8e554686eaff94d282159a742dd3c60b9c95da; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 104a064505dd3db09facfe6bab8e554686eaff94d282159a742dd3c60b9c95da, and the block's
timestamp proves the page looked this way at or before that time.