Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — foundational services, anchored to Bitcoin
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
d6fa43f45ee47e5918226d8bdcc90c5a1e8b0b5ba8f51e9d413f6e4fd491219e
3209a6c0179b243261a0fc8a4b5022b31a73127c49b67593cde771142e4c4e71
c1f191b37c84f949616db70c42ff7fe95784cfe894fc276673f8e8d1e08920d3
5a92b77fa61ca07d0fd41519efbb146c7d1f08c9b26a9e19101ac09a5406fe86
1babef2a35a0b3ac2dcf0f24f91ed1ce43861aa74fdb68b969ffebcea5d2de75
f10cf00b76a26c781b70b141e7d1d032f9ae159811eb903b031cb96683023a84
36eabe2e701356dbdc82382ced3a2f114e8b5ec8e430efae36a270df9736eb02
f48fd71c2dd57cfc93c5b16a1255aecbef1fd87656e651c298a99c6a163755e9
88891582eb01bf9a09e45951fe3d6eb3517a5b81b7d75bd7877eeb4e2dda6928
ba3bcd8fcf035feba81a581ecddb2421fe728727d23b57805c51ab7d10e57b0cTrust 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 961878 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 8d113539c33dd648542089f0afc22dec028d3ee5213b5e4f3901a47d5630a710; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 8d113539c33dd648542089f0afc22dec028d3ee5213b5e4f3901a47d5630a710, and the block's
timestamp proves the page looked this way at or before that time.