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
e015ecc50443b7566e728fe368bf3fc20302d55d0bcd0476283410db0c60cf07
5e6df4b6564551567072a1d094936b5f5f8ab0eeb16f9e2e96b5b31eda3d48fa
bfce835af5133b9912c2c8250c17bf7feab796dff2549f43fb3a917b0c0a6ae5
fa630b034530a2357ebf1625023504166b29da621e4e3fa7dc64eb1d2b509f22
edbd6899ab33c215de8968bf5e5d86a798c21f3075a7e3c13eadff2c157d4787
b521c0a99953e2a0d01b071f05e86a4925f593e8574f388e6c962c2475e796a7
d0d5cf6c4dd5d19be7e43cd68935dfbb2eca04217f600c5bf7cd0fa90ec36894
b14a5fccf545fa8a7a19c9fc98f6e961a2ff224653ea8c163e1f1021785c39e6
e880a5b2cba5f14bf50a4df8dac2d5e75b08ed6b522185ae6208bcbace385a71
0889424b8f476147169989caedafcfdd8031f5d04626a6fc0d002e8f2af58a4c
7997edf372f400df29688b3342b43965948570be6716c4ce83e0a34183641b32
abc2daad23e261f6b6fa92ad01265589a4eed477180ffd737f461c02a0ba56ecTrust 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 963916 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 6f9ad1503d52224217aea05b7c9026200a34def788a85e3fc28d2aac506bb370; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 6f9ad1503d52224217aea05b7c9026200a34def788a85e3fc28d2aac506bb370, and the block's
timestamp proves the page looked this way at or before that time.