Web-page notarized
A tamper-evident timestamp of a page's content. Israeli PM, central bank lock horns over sanctions evasion
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
04ae2326f43ad44d1dfbc990d865def07db8ddf61b345a61e50707f5a748acc1
83a0dfdd539d631bd760e2a922d84080a54f99d1c499b66bae87eef96b1cf00a
6570c6c65f576793a0ea9bb9af21a934ee4dfcbdbd221059e3dbc98475b3c314
ddcb11ca0d4d88aeff773a8e16d252b6be9f68e1b92b0905b5f55afaa460d447
d691a1d7f9f605bd0a37867c8a9a0224d94fe129a175d01360f8e79c6a64dbb1
7a486df0f9326f44735a5b6e9431e0cb3397a14039136114e38212748c51581a
c45a6751621cc22b28f4df11edb3dde8550e3e6eaa6f7f9db8ffaa60658a8aff
ba06a73441ed454b8d13063f0aef7a5f12616ef22cfcf015b9c2703eaebb3b77
112637c5d3515639abd223ec7e41d61ceb770dfd53f6a9414c3e6c811b15bc53
1a80b12f3480f611690b821163caf4c2bb32214390f0c9534c1f409e5925b234
a37ad7b5eed310552ca52a67b2eae6e5904657175be61cca011b95288d10c81eTrust 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 973977 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 d87b6e7dfed54a70c816beb605cca14117393a7965fe550c820a48e3fe718db5; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / d87b6e7dfed54a70c816beb605cca14117393a7965fe550c820a48e3fe718db5, and the block's
timestamp proves the page looked this way at or before that time.