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
06a1720ca6e7ae2fb8aab42e4cd4d20b8253acf07c2890f9fca9178283620696
259bb04306233c9da7a5f42fbe2c836026f06a053fb76e4af19b89463c985880
f646a30ac245b5f5ddef051c93a642d40669d9d639b961dd8600a5e849aa29cd
ebee61fd172bf965e98fad5ea10c381e3e1459eb8cb054aa7b7a7948cdf1ef70
f30865cd0c3fe8b20045a9354da8cd94831405f497f3e992c13d37c560aff0f2
fcd742a5acb6b7312bda90a786a94d1e46c9c6367c169cb83e0a821053da799c
2c237dcb843d82667c6a19fadb0e7fdf5bb671cf3c24df02aa7e2e5ed0919e3e
d67ba95fcf6658712979ea3a8126f4b0d483fa5e4a3a98390a0bf20c2f26a7b6
acb21c39b759dc6e5cfe6ee625d6669d77bb61b45842d5ae5e95ec57038a274f
8c32eb16de0a7974da62190f5693a7a0d0a61ebbc62bac05a9c4fe59cc7f75e9
0d0c83d36cee2177b9c6ef04d736d5ca87c80dcb2b9bda993ed774a147feb695
323c04bbb7224ab3d78219a5ef0843ced368526ad8b757a15b14f1ce5c056fa9
9a123a338a61efe16d3c2cfbb0e6929439c34debedc161696738f05781b12939
9cb37f1f19138c53e2b51f064af491ff4d67ca4346d849d97244664c2b6e3bd2
f8c9cf4daff4a102b5207a509f8184621220f98e081fa0a5c48868544eb4e6e8
2a05a419001c45763d578e1a65234c8ea579fbed0fce14681f8f5a2d5a7d4421
0d2e44d9676c6637113467636399d66a8ccfe83e28d0696d062ba8a4499d24a5
2a3c81c6ae2e9b7400a03b38de9743e716c6c78899aba0e8d02537a8c38342b2
2fdb52cd0a29343be94bfc8ab8908bfdcb254b4976c5d7426783ae2b5dfdf0e6Trust 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 973444 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 eb0ccec890f4161ecd1fa54204d723362e8830b4bcb33785b6fabc184063b30a; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / eb0ccec890f4161ecd1fa54204d723362e8830b4bcb33785b6fabc184063b30a, and the block's
timestamp proves the page looked this way at or before that time.