Web-page notarized
A tamper-evident timestamp of a page's content. Justice Department urges sanctions for database analysis critical of its noncitizen voting claims | PBS News
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
e6ebf79527e6da81dae3f841b216f6d9f7212b580fe4483f94e9d12711b145e0
22cfa7513245e8d244c048cc932d185889d5bad59969d12effeacb0e7951623a
e50a92f3286fcfd2bd594fcc2cf7df846039f85ab935c60e4b2e01281b63a6ae
104624905cc90d64861feaa0f79e8e46eab05d952c5fe8730eda021e18a0584f
162653148c46c737cfbca70de1c7454d7581b23c18e52aa4cc059fc08aa38626
1a38ec6483ec77c6909e295cfabafaedd15023ec329ebad5b7db7dc7a4b96437
5adebbc32bad5a25f6d7eed3534e034750eb688396e6f36f5a516db72caf9dd9
25b41d774182829609b98bd9f8963d272d5867d9fb01c25fed6823eb17d30bb2
b5a0869186a41dd38e575e3393241610dc1a523a875c80bd2824442679883bed
146f6529ad1baddd50aa2e8ffdf0157e8e4fa46e0cf06c31b6a4d2030e22e184
22e1ea6aa4853f5943278198c057fe38f68a29d389c64fb015c8713c11a615bf
e59d9c2e489bd6b3d0aca9d381f5b045007bdbd2a25a176c741b8a8fb8b3082dTrust 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 973751 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 16bbc1f50e759279ed2bd65d41d528db763f1fa0c6ee3c24c25a753140b2edf0; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 16bbc1f50e759279ed2bd65d41d528db763f1fa0c6ee3c24c25a753140b2edf0, and the block's
timestamp proves the page looked this way at or before that time.