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
87b48ff1abf0ab47a39213e0f56db8ed1a7fe3b5028f7bbf93a099639b1903a6
7432004303d8e45c8ce2561fe5c3782b7c065ecf74bd0b26e796488c7c2e5f5f
748c098744b5fe3269541e7f73438050d4439b349cb514e47427e263efe31516
b911601537b293c9969e3c360ee7b59eb6e67158a205278d315b6410f7362100
a23a21d1134802ccee0471540a6b87b1baaf97db1a16f22a5e364b896fb8866f
8b6fb6b571c330d7f764fd2aee70b08c9e323fce6143268a2b4b514b30190558
04c576ca9a428a8dc2754584b5f4b47ef642f7264d1b06991b54751bedecbe72
aba0420dd9efe397feb982cd33713d546f044714dd7993bd0098510724902a96
7904be41859ea641ee1d81a23f45cacdab65382d4c25d8d49fcc42dffa81aab3
ad816b9a7261b3659cecdc288205c13fbd7775dfd68fdc6bf1ce68ed404606f3
30d08406f8ccf599d64b1723236d2b8a023d5d8be66079802ee05ff8bbb66530
3f5b81ef28e3b9255d1790c2363895158450984db0194023555df12c22d01ae3Trust 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 969324 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 56e3181497d69f197dd5bcca55ee8c5c354cce9bdf31244085d63dc276387862; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 56e3181497d69f197dd5bcca55ee8c5c354cce9bdf31244085d63dc276387862, and the block's
timestamp proves the page looked this way at or before that time.