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
36fb60c40c6a51e333fd514905b3cd1bd743285861cc0a2943c8c7ec1489bd2c
6919488371bcf007a763d25c28809c3824b45d06ec449e305596f6e340a2c483
6884cbba7cdcab2231af7ee2516ca79c0e3f106f66aaa20b043aec80d57eec62
37f6cde7cc2e8f895c9a7388991835f2254a5458abb6ee5bf328c5c7aeb702cc
0666b54c5d606cb6ef9f8724147c25f7323e1d45551f1f164310e548f9e4e269
ecd3d3b84827896e65976b85ba5e600a050ceb4fa7beaa704eec1f6067acb191
fcfb3564e8d26a289c5e2219a43d2a2b479501a2af7bf5e02d14eaffdfcccfd3
5f47d74177bb3996ecfc6bfc9c6a863c5a89d86b958c9c41e7598b506bdad64f
4196ea0a75751d53aa83e9af0ad7fbac79f48ea8cb429e3d20abcfe613505ee9
7d343eb84ef19f85dfa706890ad89500d444571619d8d860aa6122f457198f9e
b4530d3282cffa874c746f1f15b55b6f87d909edba506bfde18c8d9c100248a6
f66aa94737d08c5727b6509fe96b4a1050c4c4c303b6c669ba2341577b954363Trust 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 969991 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 fba2fe843c9825c5bc6b243f2ed6bb97e5eb03c21e4cdc01e55c38fffb788b74; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / fba2fe843c9825c5bc6b243f2ed6bb97e5eb03c21e4cdc01e55c38fffb788b74, and the block's
timestamp proves the page looked this way at or before that time.