diff options
| author | tv <tv@krebsco.de> | 2026-11-16 03:12:39 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 03:12:39 +0000 |
| commit | 677dd5efd58796212839a43e87555746f9b21abb (patch) | |
| tree | 3100589d27ff26458242ce6221f963372b35480a /docs | |
| parent | 109b4669c3709f3326e0ab1b7740a1fed92818eb (diff) | |
federation: no version replayed across a remake
A node switches only where the version it reads is written at the base.
So a node that switches took no version written after it, and what it
replays names the version current at the base, or one before: the
replay of versions, each in one change with what it sets, after the
votes that passed it and whatever names the version before it, was
there for no node. It goes, and with it two `true`s cast at once,
replayed one after the other, undoing a version that passed.
The version a node reads is asked as it reads it when it switches: one
it takes while it builds the snapshot leaves it where it is, as one
taken before.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/federation.md | 44 |
1 files changed, 25 insertions, 19 deletions
diff --git a/docs/federation.md b/docs/federation.md index e4c91cb..22cae30 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -460,13 +460,14 @@ snapshot is a function of its base. What a federated node asks of a remake: * **It builds it itself.** A node that holds an epoch leaves it only for one whose snapshot it built itself, as continuum's node builds a compaction's and checks it against the committed epoch *(checked: `remake::switch`)*, from a base it holds, where - it is a member and the version it reads is written. Never on its peers' word, however - it hears of the new epoch: a node that lacks some of the base (it was away) syncs it - from peers that keep the old epoch, each change judged there, and builds then; where - it can't build it, it stays where it is, says so, and never rejoins an epoch it - refused. A remake's decision is its coordinator's alone. How long a node keeps the old - document is its own setting, not the remake's, and while it keeps it, it syncs it with - nodes still on that epoch. + it is a member and the version it reads is written, as it reads it when it switches: a + version it takes while it builds leaves it where it is, as one taken before. Never on + its peers' word, however it hears of the new epoch: a node that lacks some of the base + (it was away) syncs it from peers that keep the old epoch, each change judged there, + and builds then; where it can't build it, it stays where it is, says so, and never + rejoins an epoch it refused. A remake's decision is its coordinator's alone. How long + a node keeps the old document is its own setting, not the remake's, and while it keeps + it, it syncs it with nodes still on that epoch. * **The snapshot** holds what the old document read as at the base, but for what counts no more by the version current there and is or names a version before it, a party's `null` naming a version before it, and the member entry of a node its party doesn't @@ -478,11 +479,11 @@ snapshot is a function of its base. What a federated node asks of a remake: one reads, each in a change of its own, judged again in the new epoch, the other writes with them, each after those its change builds on, clocks only between changes neither of which saw the other, as continuum replays under a strict policy *(checked: - `remake::delta`)*. Versions written after the base go with them, each in one change - with the key sets and node lists it sets, each judged by the votes replayed before - it. Votes and proposals go by the keys their version names, which is replayed before - them, so they count as cast in the new epoch too, whatever key sets of their party are - replayed around them. Whether a place is held already goes by version number, then + `remake::delta`)*. No version is among them: a node that took one written after the + base doesn't switch, so what it replays names the version current at the base, or one + before. Votes and proposals go by the keys their version names, which the snapshot + holds, so they count as cast in the new epoch too, whatever key sets of their party + are replayed around them. Whether a place is held already goes by version number, then `seq`. What the new epoch refuses (its key was dropped, its place given to another) goes to the quarantine of the node that holds it, and its party signs it again if it still may. @@ -549,11 +550,11 @@ long nodes stay together. parties fork. 3. **Remakes.** A node follows a remake only where it built the snapshot itself, from a base it holds, a member there, the version it reads written there; its peers' word - never moves it. What came after is replayed in history's order, each change judged as - every node judges it: versions by the votes replayed before them; votes and proposals - by the keys their version names, which comes before them; envelopes as chains, from - what the snapshot holds, by version, then `seq`. So what counted, counts, but what a - remake can't hold (Remakes), each of which its party writes again. + never moves it. What came after, under that version, is replayed in history's order, + each change judged as every node judges it: votes and proposals by the keys their + version names; envelopes as chains, from what the snapshot holds, by version, then + `seq`. So what counted, counts, but what a remake can't hold (Remakes), each of which + its party writes again. 4. **Carrying on.** A fork is a swarm of its own, named by its first version and the heads it names, its members those its lists name, joined by its operators' choice only. A party nobody follows carries on alone. @@ -598,7 +599,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang | 31 | Two members advertise an epoch ahead, or offer a rejoin | Not taken: a node leaves its epoch only for one it built | sim | | 32 | A remake's decision written by a node not its coordinator | Refused | unit | | 33 | Two envelopes at one place beyond a remake's base | The chain to the one read is replayed | unit | -| 34 | A version written after a remake's base, an envelope written beside it | Replayed, the envelope first, as it names the version before | unit | +| 34 | A version taken while a node builds a remake's snapshot | It stays, as with one taken before | sim | | 35 | Two envelopes of one version and `seq` at a base, a write after it on the one not kept | Quarantined; its party writes again | unit | | 36 | A write after a base on what the snapshot left out, or naming a version before the base's | Quarantined; its party writes again | unit | | 37 | A node with an empty document handed a made-up epoch | Taken. Not promised | sim | @@ -671,6 +672,11 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang keeps every operation, so it shrinks nothing; and a place it empties reads whatever its party once signed there and anyone puts back. A remake's snapshot and a fork's genesis leave it out. +* **Versions replayed across a remake**, so that a node that took one written after the + base follows too. It needs versions, their votes and what names each replayed in an + order of their own, and two `true`s cast at once, replayed one after the other, can + undo a version that passed. A remake racing a version is rare; the nodes that took it + stay. * **Remakes of other kinds** (`replace`, `import`, `strict`), followed where the new document reads as the old one did. A snapshot judged by none could swap an envelope for one naming a later version, and a node would take it on its peers' word wherever @@ -742,7 +748,7 @@ On a federated swarm: node syncing with members only (a wire change), neighbours by party. 4. **Remakes**: compaction only, each node building it from a base it holds, never on its peers' word; the old epoch synced, while a node keeps it, with nodes still on it; - replay of versions with the envelopes. + replay under the version current at the base. 5. **Forks**: a swarm started from another's document, named by its first version and the heads it names, and the check against it. 6. **The registry**: the rules for krebs, the tool that signs kartei's entries in as |
