DukeInc/Kez
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

docs(rust): clarify central-server claim — optional, not nonexistent

Browse Source 
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.
This commit is contained in:
Tudisco 2026-05-24 15:22:27 -06:00
parent 636dd9a3a8
commit b8a1306faf
1 changed files with 5 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

7
rust/README.md
View File

@ -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.
---