From b8a1306faf5e80c59dc679904277ba794ce03e92 Mon Sep 17 00:00:00 2001 From: Tudisco Date: Sun, 24 May 2026 15:22:27 -0600 Subject: [PATCH] =?UTF-8?q?docs(rust):=20clarify=20central-server=20claim?= =?UTF-8?q?=20=E2=80=94=20optional,=20not=20nonexistent?= MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit The Keybase-comparison line said "KEZ has no central server," which is misleading now that the rust-sig-server exists. Reframe it as "no *required* central server" — the chain server is a convenience tier, not a trust authority, and the protocol works identically whether the sigchain lives there or in a gist / DNS / nostr event / well-known URL. --- rust/README.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/rust/README.md b/rust/README.md index 3349ee2..962be7f 100644 --- a/rust/README.md +++ b/rust/README.md @@ -15,8 +15,11 @@ is the Rust implementation of that spec. If you've used [Keybase](https://keybase.io), the mental model is similar: you publish a signed "I control X" proof in a place only X can publish to (your gist, your DNS, your nostr key), and anyone can fetch + verify it. -The difference: KEZ has no central server. The proofs live wherever you -publish them; the verifier just walks the links. +The difference: KEZ has no *required* central server. There is an optional +[chain server](../rust-sig-server/) for sigchain storage, but using it is +a convenience — the protocol works the same whether your sigchain lives +there, in a gist, in DNS, in a nostr event, or on your own website. The +proofs live wherever you publish them; the verifier just walks the links. ---