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
ee91ad32ae68cf474948c82a27ed80d2a3ae8de7974d4255cae5eb7798d5e4e2
e6f4537b58fedcc7082c2a1bf3c7ce12e9eaab3203b456ccd1172e0202879a12
de8c2d163ee96ef96f233b94d95dce434cd8113343ad875b2c10828590c41d16
218ebd3c43e15d9811cfda70d510ff451ee0c22a4f39db763858e0f1ce1fc7fa
fd0ea078b32a38e6e14097089bd936280958a07e7f1cd158944cc7705a244bad
d3dda1d454345e302a4165d42b79211a115bfc3f782e5411efcfa6ef0a3039c2
0b089eb315bd84e6d5b0c50cae0c2029e2bad7f425bb7ace5cb8e0b2c008557e
51a78c182ed539230a057d16b319eedb6bbf22d1e81df25460f703f38e4d4504
e0bb51b4bd2173abebbda813cca736e1b0e55d190fd80a4db24d7276ab6dce8a
37f191305dbd3517b3c5048704f6e8c9ab64a9dda4f4eaee3a108c03b8805384
6f24ff3a7170c2526927655a863ab75706db8e5fb592a41c709a84842104b5a9
c089a229362a3c64e34722131dab19785b53f88f3ea2ecf6402d8abd9f5bee63
caa7689e643403763c77b68fdfa06593ab4232e2fc1ca3a878971fefa7a7bd97
c1312a65ffa3747ffe4dcdef5bddf2282ccdcbae90653d4ad7e2838585e1ca9c
f0e2374e000ab8aff277d4254e6cb4ba8fb7d27d0ef0be577b528075cfb47f57
d4b4cdff692bdd49a7fb10b8dd50fa59d8ba123ec31370e57329b8c9de38fac7
9d0074a868502c8210313e9959cb0c854b6c21cb4a22edef4c18ba2b2419dd4dTrust 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 972770 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 682a72c35f103f7573294b1e56f5172e9ba51e1aa070fefca02795e210b31f63; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 682a72c35f103f7573294b1e56f5172e9ba51e1aa070fefca02795e210b31f63, and the block's
timestamp proves the page looked this way at or before that time.