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
1b8cf186a150434ee3f9d9ba0269a67c1e918215300dd26a62625ecb9d12239a
2e26f47c906892034c00361d686575ce0bad02cf98ca3a293eb8fbff238deca7
09a6efeecdcd778a15e978c389f17e208126e1e29016d42a1e4e672dd775f3fb
92e5dfbff5bba017a3431b577c4a245227519c5385241b92474b7ec6b3113d23
b4a736b36396986036db382598937ccb578b4e12d9c399f65846a7bc686c8f3e
feedab28908e4fa6d77488809f6acfdd1c950f6e1663328ec60f01def0d4a9e6
c8d0aaaf408c7532ea17c4fe54eef822624eb91ecc9e1b602d45a2823f5ce86c
79eeed5c5db2a0485423e539db4f55104bda0040aa0f10c0114fe7da09d52da4
8178a0c2e9c2a889d223de91b0f4e5fe73a840c0540e9ae824a2bc6568e1202f
331b7c227160b2d9e62f0a1e2b69b88ee13b8e440949c988a225094bbc9a31cc
c77405016e2bff162801a153a45eaf858379a66cc037ed8eaaed5e3f49ad5007
285b98a5f88bcbb773a2538fb27abb6e599e3fad910f367211d9cc8341033b46
a2653d5c3491cd3ad6edcd5a28e140efa2c93e41c629b010d06bc7258c171e6a
70e7d35e8503cb998cf03a208de724aa1dc2bf7c4e1292a5c70587957b85c375
06c01fa133faffab86fad45332b7c661ad748c29bbd70025d38e2739baebc1f0Trust 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 967851 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 aad470a30ef4bb96df10e23274baae2bb71f701c0834e4b34bb1ece03eecce40; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / aad470a30ef4bb96df10e23274baae2bb71f701c0834e4b34bb1ece03eecce40, and the block's
timestamp proves the page looked this way at or before that time.