diff options
| author | tv <tv@krebsco.de> | 2026-11-16 16:40:11 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 18:01:47 +0100 |
| commit | 1ef097ecbb81f1478cbb9ca13b4c263a56315ac5 (patch) | |
| tree | 34420a00b80df52b746c913da6a22e4268055064 /docs/federation.md | |
| parent | d7b511e7cd23a7264b8f02b5ade29bc5674b678f (diff) | |
federation: checkpoint heads at which the current checkpoint is current too
A version names checkpoint heads after the current checkpoint, and now heads at which
that checkpoint is current too: the version naming it is among them or in their history.
Without that, the version naming the current checkpoint could be after the next one's
heads: every node that moved there holds it, and one starting from that checkpoint,
which can't check heads before its own, couldn't judge it as they did.
Diffstat (limited to 'docs/federation.md')
| -rw-r--r-- | docs/federation.md | 17 |
1 files changed, 10 insertions, 7 deletions
diff --git a/docs/federation.md b/docs/federation.md index 63c4ccd..98d2eee 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -396,12 +396,15 @@ its version counts as written: a version event of it that comes later is one the 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. 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 +checkpoint, at which it is current too, 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. +As the version naming the current checkpoint is among the next checkpoint's heads or in +their history, every later version naming one names heads after those, and a node +starting from a checkpoint holds what judging them reads. 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 @@ -673,7 +676,7 @@ crafted events. *Sim*: a simulation. *Bench*: measured, not judged. | 67 | Events a side writes after a merge's heads, brought to the merge | Never taken: their history lacks its root; their party signs them again | unit | | 68 | A party's event spelled anew by another: its `sig` or `key` encoded otherwise, its signature's S not canonical, its blob naming another key | None: `key` and `sig` read back to themselves, the signature is checked strictly, and the blob's key is `key` | unit | | 69 | A node joining from the root is shown a chain old keys grew, beside the one the others took | It takes neither, and reports; once a checkpoint passed, it joins from a pinned one, where that chain is refused | unit | -| 70 | Checkpoint heads before the current checkpoint, or one in another's history | No version: a version event naming it is refused | unit | +| 70 | Checkpoint heads before the current checkpoint, or at which it isn't current, or one in another's history | No version: a version event naming it is refused | unit | | 71 | After a checkpoint, a party that backed a second proposal once its first was dead, the nays that freed it withheld by those who cast them | Not named: its client keeps those nays with its `true` | unit | | 72 | Two clients of one party back two proposals at once | Voting twice: a party votes from one client | — | | 73 | A party keeps a proposal alive that nobody else backs, holding back automatic checkpoints | The party a node follows votes it `false`, and its followers with it, until it is dead | sim | |
