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
87c9e323f7f9094e7b51e5c53528646b0c16f487c2442e7c204d9ae4988e8019
08ad91979f074567ba3b14c161d25b02619dea195a16226602c2304f6aec15f0
c7b030f77b72d688b27a23b404735249f208171a5071a18d65fcc7cb4a559f03
de5f547ef4f72c170db90c211054200b5dbfd0a06e3bc670813d7b1a34c627f6
3f95c18ab0f4b33744c875cb80fcd048184d4be6b1dc8bec5e195d7022fed88e
2a5a8a4e8af75f952280721cfa916e68696a5e74430605869b012842b21d814a
2f22ea321a1d2d2c0f9b20b4e7e281fb7b0e9a79ad10e8f8e8f1b6e26faed089
cdb2dc9ae55829fe67c378f877235faac6cf1d113b081899cadb908927a99c7f
350fed0fb7aa1ac0819435a8e59dcc4b233651a7189790efec26eb2ac7fad0cc
fe083c4fa1954376d6750fbfd0db344a94e070abfe65f8a17ec9a489aa30e025
0ca2d3f22c3c86f526c3b2caad44e3d77a9f6890f6b7af186a7ac212f298fde0
c5c35034cb3ed2daba2a2f666644156549bf3b4050fb9f881d00f6a9cdf6133f
3965501c5ecde6c27f84d3a13cc6a9e5f5c821f6fe05f1906137b33a6af9eef6
2ec56eec6e5af21a17e9af35ad1e24597d93b2bbdfd3d0be04793c3f50f4656bTrust 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 973787 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 d2c8c520327ccdf465da113d7a69335449003821d88d32716ae78d5f509a8997; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / d2c8c520327ccdf465da113d7a69335449003821d88d32716ae78d5f509a8997, and the block's
timestamp proves the page looked this way at or before that time.