Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
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
ac606661dd8f666588c02bc37e8345447a1d382ebef67b6833fbbb1ea2abca3f
fe4079d716880281a42dcae5508f373663295e3346a36d6cc6ff9dc6a9c91f08
3f35aefd316c55ebb62c1ae0d82c620f675b290c91dbd29b30d0b81fe91c1110
45b80fd10a50b0a6df94f3f40fb674998a8100ddaf6982f3e08ccb59484f016b
aca4a3d22c55dc31eb117832f9cb0c6ae4a39e3788401880f1e8e4af5fe337c1
ad62441fdb286dda5eb2b6a927d8e67ec0c339c54cf812a02ad8bc3d7eac46d4
f1a751498bcc5dbb624daf14e67bf4b7596596fcdb0dd619a3bb945425209bab
565a3edd386a69603d5640a55b1851a6144c2269073fc7f1ea35e9fa5a2b30cd
90ec5cc07c54498bb3c4c36303db013746d1d6700e2f90859d087c9ea657b3b2
e42828eb420ac67a4c0b556ed14d8ea9d6054816a93706012670de287cffd6d6
8827c7c511853f9e05a9b590079b2e589f09762bdb185e0ccbfd21bcf1a3d89a
06a84b2ae3cd2a48e19167f5aea4337738dc19fcc5a1dec262a7b2c4ea0f6502
0afffe64639ca139e928b2736941b3e69e8f09e8e98203ce512a18de7a1289af
1911a992af83b55eb9f4dd7c69d5f655c68dd903342e80ca4fbc26a8da1804c1Trust 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 965712 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 3d619ba6d04315e3ee188a1af172ba9112496312d0b908a3516306754786a304; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 3d619ba6d04315e3ee188a1af172ba9112496312d0b908a3516306754786a304, and the block's
timestamp proves the page looked this way at or before that time.