Web-page notarized
A tamper-evident timestamp of a page's content. bsv.cx — verify any Bitcoin proof, trusting no one
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
5e73d5d2f5129f5cbc9e1606bd368a8cb0949f1923a379a1afc19bb8e4322161
bd824470d69f08acb3dff0bc3de38c7192fdb03eb06243ae0e236e29f489068b
fe34472040640545c1a82af1cb16084ffd4f3a93bbf291d3dd5480580e9e4538
869c213643eea5ce0b4e455af5547bffc5ce41cf2319886659dec4964e2b1bb3
6a4f7f4148b4830888a5dc1b77d367e7f83ba5d2c3a306d5271d0b0ac6dc16bb
f95ad00fc406add84a7c50c1510e8b1bf5bcaa32770e1197696eb00c84d8dec4
13017c5a84c60adaf17a86f537fb38e518e836878c5b9aed553c41793f4221a3
1afa7387f9d9c4d7f525900dbe3664583bb85046d857e246ef0c4e08f1cb1f0a
153558b28ec27938f57385506f94120b0584191c70758aace8a4853f96302ec1
1abb8c6f01d4e3ff17749cc725ab77392611a2d4e0a986639b38a40766c0cdbe
7256d8a6679721892ad9d7764d6e8bdf68dac597fe8fdcf41ec07f7ecf781a87Trust 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 963483 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).
⬇ screenshot (PNG) · page HTML · manifest JSON
Save all three. The manifest's SHA-256 is the anchored id, and it binds the screenshot and HTML hashes — 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 d7da656daedc49a374b600fa2c3617dc8f0fb01db8ba5e8e506f431299cc75e0; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / d7da656daedc49a374b600fa2c3617dc8f0fb01db8ba5e8e506f431299cc75e0, and the block's
timestamp proves the page looked this way at or before that time.