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
529430c1a28d1df8808f770f2817b525c37044c8806750c7da8394e345e94d69
aef4cb71a73a5f234d7bae9b20a056117dd4abb24c818b87155272eee0b77e64
43897507a4f73800d7999de17817af3cde4bae66a201c0e1303e9799cfcebaf0
502d447445ffb3ba64fba2849386e27f86ceaf8a25153a477cf28d6709f10910
48a6b20cc096b104af248265d3c1546bc423ff211f8745f8484e6f4a399ad0a5
75c4459cdcdd7c61a2362053d30796adb8c735ae007f7e29ec85f7a8ad7f7fa0
28c8b08535a8a57c174145a47d9f338017cdb186df40849af3f4c67cc3890dda
6ca0dec748604ea0cfcf4c8291a60b841672be67088751d34cf2b680f4c0f959Trust 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 962235 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 d774745b40288690e0278c5116c988f369707ccfad04910dbab641cf8e5cbdba; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / d774745b40288690e0278c5116c988f369707ccfad04910dbab641cf8e5cbdba, and the block's
timestamp proves the page looked this way at or before that time.