diff options
| -rw-r--r-- | docs/federation.md | 10 |
1 files changed, 6 insertions, 4 deletions
diff --git a/docs/federation.md b/docs/federation.md index f1229b0..0ddb4bd 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -3,10 +3,12 @@ A design, built stage by stage (Stages): so far, the store it builds on, held in memory and in a swarm's document, members by the federation and the store at a node's API, as [`store.md`](store.md) says; the federation as its fold (`federation::fold`), with the -byte formats; and a party's client (`continuum-party`, `federation::client`), which -signs its party's events, votes by its record, signs again what a move refused, and -names a party that voted twice. It says how a swarm can be kept by parties that don't -trust each other, for a first use: the krebs registry +byte formats; a party's client (`continuum-party`, `federation::client`), which signs +its party's events, votes by its record, signs again what a move refused, and names a +party that voted twice; and votes a node casts by itself (`federation::vote`), following +parties and proposing checkpoints, which back a checkpoint by the voters' rule, and +through which its party votes by hand. It says how a swarm can be kept by parties that +don't trust each other, for a first use: the krebs registry ([krebs/kartei](https://github.com/krebs/kartei)), today plain files in a git repository that one maintainer merges into. What it is for is narrow: to hand out identifiers (names, addresses, keys), and to give every party a namespace of its own that everyone |
