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
c2885fa0b38ceb4b138d54da64bafe9f0047408ade468cb6a7eae47e7c91635c
02891dc39210bd48ae55b136cf270422c2ee9f21b74121479422bc23039eb2c1
54eb12a37cca5ab2c0e36763b74bc82590d28d9ee1915e3c0430da67d395b1d8
8337918025e40ebbac0b74f03f5bd594ee1e610f1744364ab492c20f34e83eb0
948383a207723271580e9b0bac463c9621a62abb6357484b9f6396668ff1c7d9
c9776cdda04930da0a2228f5ed922718401982e4d3e955b2a3a8fd70f6363a5f
d5579c356f1b091dea823405f8b8ed376574dd81ed3893ac6d98afd70e348085
dc8e6c0948078f73ad40e686c89d7c152dbe1b1616df6eefa50d1a7b6f282827
9ba02bffb5002f517fe4e3e3c4e5bfc61d8b83a05d8175eebe1914739a284296
192c6ecadb013d71540c11342f3b54beedd1f10cbf685b6546432f354d3df7f4
96a36d2b5bba59df70b88d03cf45133f1b27464f7fcdba7a674cc3e2090f6361
809d9f95d2fe18e059055e8a8c414a723f2cc2294919f929703e7f6f2ecec9daTrust 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 971691 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 00d88d972030825b6b947ccd3502f15b76524c5387db17e6b0012af48831a95c; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 00d88d972030825b6b947ccd3502f15b76524c5387db17e6b0012af48831a95c, and the block's
timestamp proves the page looked this way at or before that time.