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
968566f73fb30fc2c897768a0c581e98a12a674e09a7cba907c324f189b57d5e
3ad4a6e6fbdf282d3b09becc134c9d058c3d20332b03c7f2650c02e33564a9cc
e032fc36bcd7bef738685b2c5ffee168be074acbc039ca9715d27011ee5dab7d
7cdb51922815b947a84c191a6c78fe9b58cc9060e1ec736b53e6d9605d318081
acf0b2a26af470e7b080c18c943da5fecfc5c0bf333c38c9fc214bd01f56c628
5d96404bcec7c060456824fe67a1f1378ca8e9dd58c829a3cbcb33b5d7131111
65045e24929c390ac7a1407285b86637dc9d26e972d3617c39fd551ffdb7694b
0f6592533a9bd7be3b397e2065259cc822d2971d5752d88e352c7813a1faa6e8
924cb1dc4c17b9c03bbe43793922cc8a05916a561f9c9ebbb52289933b0061fd
c8c127ef7eb40935b7201cebf70b7db49ed1716efa86183a14c0ad7ba8de62cf
f39ac94fb15f17a3151e7ea311eee8ec53be43264ebfb451c30ce506dde1c651
0be874694596bd12564f9462cc0d897714cf0a75f11c203ad5a98aa5f27827f3
04fe894797ec2b50cc9200c20902c23d51d61299d407c037e348d3579467d181
59f47677e79fa093dc0db244fd0d2059173502f83d4d835983e3ace5fc875459
faad014ca2d2e5369f8ba255fda7b355852fe98e0eaa1e389ab6f1c6a69661fc
2fb7eec3ad51b2938cceb91dc7e126897a6845e1711ea98a7c11755efbbb2e06
1c80c4e91e7510b8df96d647f41364848cd7d442ecf72a0b5051532494ea5bec
*
36600cd731cee39d001186ae8ff3d39885eae1c6f21a3735fcb5e85acaba8de9Trust 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 973592 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 94476a652594b15d1bf9007dc8084ae4dcc85f40e507aa84b8e9fcd7346fe522; it binds the URL, capture time, and the HTML hash.
The linked transaction's OP_RETURN carries bsv.cx / web1 / 94476a652594b15d1bf9007dc8084ae4dcc85f40e507aa84b8e9fcd7346fe522, and the block's
timestamp proves the page looked this way at or before that time.