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
a5a8d5fb567eecb8093eaa7dc06e09448462bd7bf9186fc8e48e8c624965b0ce
d98caf85564dd3faa47dd8504e9baefbf29f9d07352f8b44b5af81abb1a5672d
caec5a99ae69c46185ef582bc1cddeb08cd0c9b7af19d38ce343fcee0fa8bf99
d16fe6bd42f5e7040b0be00d37b27efbddfa9b2f2a09e85f4fbe37c2bbadc868
1df0c1f4980d9c3adf09251baa27b8596be8631dd0521e159a324ad6b7becd3d
5103b9c0115f450ba8b21d36def422228f7552927acbe502c15672ac1a21bb52
53bf344dc4a34a07b4fcb6e30c100d4c4e82d2ff19d11fbeab3252654b9d8db3
6cde94f516c4a79d02c3183be2583194b4473db6ad7c16d1e37b47c3dfe760d3
00e9835217581fd17e0fbc9fe1a790fec97b0a5319a67811ba49b38ec659caba
e5d55c702bdae30fb972313ad8865b4e2f1f37304fd6b73de9bb61fdc0a54dfd
6dee5516171b5142e9cc2eaf2b353a9d8e43fcc8b36db7d6827aa8133be3d1dc
b70f14635d92a2784f4f3af707d77d1137eaa8dbbba550ea8527355be62eba46
c4c4cc02e2b828347e2c4ae94fb64ad972210d56acb11bb76e38b65f3a9342b4Trust 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 967637 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 bbc38a0a28e0dd0ce9aff4c1815b923b66d3274268b2f989a34b8d880ce79005; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / bbc38a0a28e0dd0ce9aff4c1815b923b66d3274268b2f989a34b8d880ce79005, and the block's
timestamp proves the page looked this way at or before that time.