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
daaa4256a5fb1e765575b3cd3baf312a91d63d16143282bc10cb34f5eee4dfb3
c1878a991e55fc5a5ee7030a9c5d63ebb17cbc2068019fcc26464436c69be79c
044ca7da0478f6439e6543ff6df425b997e359c0c007ec4782436786e00ff6e0
ddf07f17176f5593eab45a2d8e3f76de982e94d79063814d6453958326405aee
182fcc47ec437894d1c2e07e05d9fc3e59b721d66e5bc78fb85694babf0b6d35
117d0855910c7a8fe6fe204f76f1b3ca0880998e9ad123213ca09a5f68462efe
d9119712ddf69a9c69f47efea824fae0f2716b825bcd90216d051a9bd4e404c2
f3ebe2475b0b7c26065fd9c74cd1c121fd718b9cf0bdc91f9d25aee2009d83b3
4431d78340cf9b9eb4f3246a18aeddb95abfd337b01f7ee993a25fab4f65cbb2
fd91301df11b9288d1d0e6a157a5e6f4c2d600f4a15f7d95e42b664533494971
c7adef2321a1a128f4a1d87b60423a2fdb1f62e53d079cd59b0241d8c37d59e1
ef856604b38df4f1eea0f2b7c1ee11621fca073de0bad4f5e34f1e2184d95717Trust 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 971634 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 43eb803ec32c0e23d3d3b4821725dafb9d7826d74dd4a59bd5c872f2e78f07bc; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 43eb803ec32c0e23d3d3b4821725dafb9d7826d74dd4a59bd5c872f2e78f07bc, and the block's
timestamp proves the page looked this way at or before that time.