aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 03:12:03 +0000
committertv <tv@krebsco.de>2026-11-16 03:12:03 +0000
commit109b4669c3709f3326e0ab1b7740a1fed92818eb (patch)
treef04cf59e33d60ebb09007e01b5316c740d47e55e
parentab9e29c9290dcf7faf535b554932ee32a793119c (diff)
federation: the old epoch synced with nodes still on it
A node leaves its epoch only for one it built itself from a base it holds; but continuum stops syncing the old epoch once it switched, so a node away across a switch lacked some of the base and stayed until its operator moved it, on most remakes where nodes come and go. A node syncs the old document with nodes still on that epoch for as long as its own setting keeps it, and a node that lacks some of the base syncs it from them, each change judged there, and builds then.
-rw-r--r--docs/federation.md13
1 files changed, 9 insertions, 4 deletions
diff --git a/docs/federation.md b/docs/federation.md
index be2251c..e4c91cb 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -461,9 +461,12 @@ snapshot is a function of its base. What a federated node asks of a remake:
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: 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, and
- how long a node keeps the old document is its own setting, not the remake's.
+ 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
@@ -627,6 +630,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang
| 63 | An honest member writes a version valid where it is written, on the side a node doesn't read | Refused, and reported apart; its committer isn't refused as a whole | unit |
| 64 | Nodes reinstalled under new IDs, their old entries left behind | Each counts no more, and the next snapshot leaves it out | unit |
| 65 | A fork at heads holding a change sent to nobody (a version written without votes, say) | A node holding the old document takes the fork only where it holds the heads' history, each change judged | sim |
+| 66 | A node away while the others switch | It syncs the rest of the base from a peer that keeps the old epoch, builds, and switches; it stays where none keeps it | sim |
## Roads not taken
@@ -737,7 +741,8 @@ On a federated swarm:
3. **Nodes**: membership by the node lists and the party a node's own entry names, a
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; replay of versions with the envelopes.
+ its peers' word; the old epoch synced, while a node keeps it, with nodes still on it;
+ replay of versions with the envelopes.
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