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
3c288e46964d03fac773973c12d94f73ced55c71208bcb59a8f7d5e3ff098e2b
b69ae345d88c902c53f9a50425967617df265b4695d21ce42282344baf4ead94
8200456b16f6e981f94bc9e856e3310a33cc631b252a78d83817a1dea9c05d0d
8bbbc44eceb07b6c38677139c138f56b65329ae91df1cdc753d712b422ad38a0
71dca0f8d8455cc8311b9d6f84049ccb310f5b6fd951cc4490cc573d146a0106
bd3038e7c7a6221c47e0444a40ab6a7bffa3574a22b0225d1e4402d7bd5d05b9
eeb4ac5663d0d062db53f61018c88f915ee85e8788acf5ea765e088c50b383ab
b4a16fe7cc94f0e45b30585578774f0ef18fc3277a943939b559cf171f6897aa
02ba727a915a8f0e54200ea146fe3a2229f7a17becc867c853594773ce63bad4
bbb5ef293e5ca2bdcce762359cc04552b3ed255e33cf07dadf6edb86fab63ce5Trust 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 969092 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 c73f02a137b59301cc8626adb93d6bedbc162d10c96c21d3b1a07e5628877bfb; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / c73f02a137b59301cc8626adb93d6bedbc162d10c96c21d3b1a07e5628877bfb, and the block's
timestamp proves the page looked this way at or before that time.