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
2cf3d176fb1c9740560a9e56f2b98c94efa62faca53e8d865de96e42c980debf
79c381b6be2bef9148411bdd239ea80d0bb591dde66003f59d9afeadc006d191
0c6e915b5507c229ced63d7d704991283337e297b4d776ff3def61d6aeebdfb6
9e7e349bedb8a21a3649fbe5830f7d538392c6f854c0cc6628aadf839a808d5b
c56f62f5f5270429ea8275350a54370e19ade3976f1bbeb671b1e38bebf9628c
398128f48ec777b497c691801aa48371e411a7dd8a1c3c1ea03f7efce9d87e54
dfc93e5a47d3a126778603825c7ad943141f773ba44083eab711dd7720b90e14
e7c5816178c11da93e25c5eaa52e2525dd8d13d558c8a1a69710dcb5c4b70d82
0caa9b529e36e1d6257e2edcc1cde0ada891e1101747af170933b518b0e0352a
678696de7e4c5b339bbc305027660e98ae9541e2095abd50087ed80ab63b5a96
4bae2f47fcdcec7ae9ad1657dbd65571b16388a4d22139f4e7b506cae11af410
f307b4fe5474bb82971c13a6398a7fc57ee526733fb14bd099f127b779effa17
7bcde9b54cb8c59878b459694d7afa2684a2a0a42b9469f686da2dc20fdfed48
cce3d751cb55ca4ac32252477d2beb2d61107e6d5fd775a4384efd62698da0d0
24437289ebbfefeff2d1cc6fad9de50fbe17d353de62843bcfe09caeace2de3cTrust 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 962917 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 206ef2292b77faf281697b9b6ce71d4afef1495f51f81aea1f7b54e77192d48e; it binds the URL, capture time, and the screenshot + HTML hashes.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 206ef2292b77faf281697b9b6ce71d4afef1495f51f81aea1f7b54e77192d48e, and the block's
timestamp proves the page looked this way at or before that time.