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
6d74f49a501664d337641b66cf2c198f35f18a3cc963ce2e67c0972fb3b75b38
78287939e08543fce687eced1bae5e19527ddd3d641b060bd65e5c3f5bd55436
ae36d28590567827b54f0bdcedf3c528e89a69a209bba187ad871670ba3baa21
3197687548a8417c21ee490bda1b39d417e2ff4ab2ee90719d4a9125e28ef28c
17de9a242dbf1708a4ff917dda735218b28071a71654c835a1580f2574fe842a
5c0ca32db4a6dd8231b4eaf44ede0c506e2934015071d989206c2d5bdb3b5b01
5d9801a481d5e5665adec3197baf67fd0eb167749d0acf6367b5030541e3836d
aa899734b0a294c7c7ad54509a62eb0fbb6e1840734bc512db55bb08a60b746e
59e76699d9bf27311dc003d352fe2ae329167a7ad6576cc3ffafec67be43735f
06ef95487abd93cd71725596cfec95f89e53becbc78cebff9c92a5cfbd9430ab
42f40675f9ce8be42607da7477f1d256c6e908988cf5433532bc820bfbf96e0e
92f2408c1a25343e95583b502cbbd90d226cdfb092011e423c797a4b9494cd16
bd4ba3a456baca34923fbb5a41d77acd701f0961d62c88e2c6ea0be827b62ee5
*
a07c53832440c2e36cd7c83a9f5df85a89d6e0311a1f308fb89db17cf773a591
*
d456cb5f74e948f95875b44a46094f259f8a3b43eb5ccac576750ffed1183971Trust 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 971021 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 d9012282d63170a683826671d29e29b1148b4ae052f7221a9d2a98e86f3a0560; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / d9012282d63170a683826671d29e29b1148b4ae052f7221a9d2a98e86f3a0560, and the block's
timestamp proves the page looked this way at or before that time.