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
171679739dbcf2b1016ad4a72b743a19cc65c0600ff739d9d1c7f2bcc8293610
863a2e2ea46c444ac683bf9ef0fbe15ca5c6a0118301f84eaf1f8c27c1716105
0ce47edbb00c5918af0b1cc1e079b15e2dfacd4d93dc31d45a02414ad853c8d9
5ab08a4ca257b0af959b7280faab258c186bc253ce9f01e9604b48ecdb33df81
c5e6b97fe4a5e0b3e4af58d07d14e298aefaa2b74ca89febe93c5080480b2ae9
de53f87f46ec35f145b1853418f2de8afabe3c7f937de2b8d03bf40d0a91ddc6
8714f899e14ee2bbeb5eaeb6815def182399891964119d54ebb4afb8e5a29d90
9c92feade10df310e814d1114436e9d0ed3954fa1651758a092425ba50182bf4
8da167c7e3e460fddd36adfa64513b082f5944146f0d79c86a70e4f634d5e9bd
5425bc7cae878b22a5e30a14a94e7a6ca20384fa37c35d4e0c414bfe0305f770
89783732396d64c7bdf0f577f380ea90965438da053160d779af3910c67f0dfc
f5088cfb04b4c916a5163fb3b81cdf2b95bbe371648623dd8a0b32fd699a9a8bTrust 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 971093 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 98d4e4e7080eabbadabe4a440b2077f036fc8a55061b52d500a23e67a3de5d4e; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 98d4e4e7080eabbadabe4a440b2077f036fc8a55061b52d500a23e67a3de5d4e, and the block's
timestamp proves the page looked this way at or before that time.