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
e1daf159092833aec47a25047e4d7bc171c3322e2b69d68b8857ab5921d494db
bb0fe35d16eef5ddb9e4b40de343e4af867271daf114483108649309e74f194c
c5e44ab1ab57bb484ecd4de7744980fb0b92834dee9b9f7165271631bba9de48
8796753f9a2873831268957e30d3569be021bb3f209356404d1393895a5468b3
16cc15dac634c039933ae76c41f0021e563e42f388a03729d66ca3000ce32f86
1ec1773f7a51c0f96f7f1c38e53d4d6487ded458ced0ca9a47d382aaa9edfb6f
b81eebdd246dde278cc8c4c1f231125c4b4313f41710d0baf49a57755bdd0f4f
d13e6721da87689bfc1e75d59103d489ab0e181bfdfb6c29fb435eb23dc2d18c
c5f5b94761c26f34d5c08a7392281bad498d37c48e36ed35ee5ee4cdf467b77c
e1739496f3231d96728f727fabb57be1e5e7011caad3e6198956940fb9cd371c
2fda0ca153b4e4f70c8d8097ac8300f399558ec344f9215141f3b2fb237593e5Trust 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 973925 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 9ae3f1c43ae9e26bf90bf448d45f3694ff20d3b9846ec87931d2002c83264468; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 9ae3f1c43ae9e26bf90bf448d45f3694ff20d3b9846ec87931d2002c83264468, and the block's
timestamp proves the page looked this way at or before that time.