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
2e0ac6cb7220ac9c73eca5b0e48314098b4e4dcedc444af89bc290a7ea569e4f
c5dc9d330a56858679c9e60ed4d05ec0aa5064cbfc525d31cab63eff2e3bd189
097729aee7dff76cd5fa26447e584b067fd60a38f47a4bb446731f893d76c099
605b43d72a2acf1b2d04cbc54253411eb98e62c97ec5b2b36a1f36e08d7e037a
339954d30c8473ed804593e1b0423a5c4b83fd88bc5d8f2fab088341fc74e687
4103816689b40ed02f40bb1a59f95171c539608af003e70c9dc84e0688e5759f
0a5ecee8e01ba9f86b2cc97ca1353d1b6cb8ee09338a3a606c106f9a3754d21c
089cac08892285cf4dbd15e8553c56eb51454a6509d687d8c57ce2a40d9c7192
2088c66606faa6b53d57cc02d1d03aff3299fea3ac6864cedad4e5793a25511c
72b96b7aa84e32c1a6390ef57a549a4f5716b72e51f173939a110463a605205e
1a9dc5f5c95296f67e76f508fe97dfb1921dd0ab97e928b252d6b51f2384d405
929476a697d54dee59165ce53dc7a62a94988456810cb52abdda61c34eb1c691
4023e69f43ee41f0c02abdf05b021ced5bbd9ddce1db3ca7ac2b2ab98c3b9354
fd0d43bba33e526a39b75473b7fb6de080835be8090294bfd6d764e5f1040204Trust 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 967872 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 055d2cb8f2d537d5916b6ced930fe1ce3891ad489385b677b53e530418d641e7; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 055d2cb8f2d537d5916b6ced930fe1ce3891ad489385b677b53e530418d641e7, and the block's
timestamp proves the page looked this way at or before that time.