diff options
| author | tv <tv@krebsco.de> | 2026-11-16 15:41:32 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 16:53:12 +0100 |
| commit | 40db32407a341f8fec2795ffb11821842e79334d (patch) | |
| tree | 32e2029bb98bdd2ee7bab97568eebcc81f1d6a2e /docs/federation.md | |
| parent | 5e29e1150f5c70dfbcc1a5fdc7ad5277af19305b (diff) | |
docs/federation: a checkpoint's version, the current checkpoint, and joining
A checkpoint holds its version itself, the object, as a root without heads needs. The
current checkpoint at a history, which a version's checkpoint heads are judged against,
is the one named by the last version of that history's chain that names one, or else
the root: a question of the history alone. A node still joining is one continuum's
lifecycle has as `Joining`, until its first sync is done.
Diffstat (limited to 'docs/federation.md')
| -rw-r--r-- | docs/federation.md | 26 |
1 files changed, 15 insertions, 11 deletions
diff --git a/docs/federation.md b/docs/federation.md index 4cb919d..cc26951 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -274,9 +274,10 @@ refuses, with everything built on it, reports, and leaves to its operator ([`store.md`](store.md), A node's own); another node's refusal doesn't make it drop what it took. One valid at its history breaks no rule: the node reports it apart from events against the rules, and holds nothing against the node that put it. Of two that change -the one it reads, it takes the first it judges; a node still joining takes neither, and -reports, until its operator names one. Without keys voting twice, every version written -changes the one every node reads, or is one it took, and none is refused. +the one it reads, it takes the first it judges; a node still joining, as continuum's +lifecycle has it (`Joining`, until its first sync is done), takes neither, and reports, +until its operator names one. Without keys voting twice, every version written changes +the one every node reads, or is one it took, and none is refused. **An operator may have its node drop what it took** after its checkpoint: a version the others refused, or any event, with everything built on it ([`store.md`](store.md), A @@ -388,16 +389,19 @@ A **checkpoint** writes down what counts at some heads: those heads, a version ( current there, or a fork's), and the IDs of the events that count there with that version current, version events aside, as it holds the version itself (What counts; a merge's root keeps otherwise, Forks), as the JCS encoding of -`{"at": [<IDs>], "keeps": [<IDs>], "version": <version>}`, its IDs ascending, named by -its SHA-256 ([`store.md`](store.md), Checkpoints). Every node holding the history up to -those heads builds the same one, and its version counts as written: a version event of -it that comes later is one the node took. +`{"at": [<IDs>], "keeps": [<IDs>], "version": <version>}`, its IDs ascending and its +version the version itself, the object, named by its SHA-256 ([`store.md`](store.md), +Checkpoints). Every node holding the history up to those heads builds the same one, and +its version counts as written: a version event of it that comes later is one the node +took. A version names a checkpoint by its heads (`checkpoint`): events after the current -checkpoint, none in another's history, their IDs ascending, one at least. A proposer -names heads it has held for a while, by its own clock, which judges nothing, so that -every node holds them. It is a version only where its proposal is above those heads, and -a vote on it, or a version event writing it, is taken only where it is above them too +checkpoint, none in another's history, their IDs ascending, one at least. The current +checkpoint at a history is the one the last version of that history's chain that names +one names, or else the root: a question of the history alone. A proposer names heads it +has held for a while, by its own clock, which judges nothing, so that every node holds +them. It is a version only where its proposal is above those heads, and a vote on it, or +a version event writing it, is taken only where it is above them too ([`store.md`](store.md), Events): so moving to the checkpoint refuses nothing that decided it. A node that takes the version moves to the checkpoint: it builds it, forgets everything before those heads that it doesn't keep, and every event not above them, and |
