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
d19155e72003230fdbc94efdccaf6d30a7b73148b88457e0ff9eed2c8dbd2bd4
c7ee770ed2ecfc682693243f90ffdb73a797572a7cf222b3d93a2ccb6c467982
f9302ca192c37d7984c192813bb3d0882c8da002a6e370e857db367d35009f76
30c693691fcf5e50ffed339afe4f46c9e86e2c3d59e13a11ea9241de14a41252
d04a0eeda87901cec8281013a41ac2db4d6b5bfbe1866ad017d62251cc67d38d
d02a7c35bc99d49421dc07fa7bb4a320f5f69967fdf5c5dfb753f5efcc2921c9
ae69371c18750c8bfe947d5e17634d604bbbfa181d803573b3b6f3d936fbe164
d8bff802392bae5e93a2c897fe8dd8d793e575584d8324d90e3eb63d10b68d48
3d8b80325724c0fa29634929429c69184043f9488d3aa1e0f492efcef814a9e0
72bf1edc0993cf0cb718daa26157ff6eb345b325d060cbae336d450d91f97a77
89505093b2cc44a9a17b0319111a1a918375a756d300304f79fbe607f8c48173
9a70a89af0a6051ea4550e41f02ca184cae09b91dadaf60ee09c7d987f825eac
f40e33e4a91f177ca3379997d967615ebf0803c069994d75c8e322881afde512Trust 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 971238 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 8b391673e720e7158fe57aa2bc561028c0b9d867e533079619f7105b7bf960c7; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 8b391673e720e7158fe57aa2bc561028c0b9d867e533079619f7105b7bf960c7, and the block's
timestamp proves the page looked this way at or before that time.