aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-16 10:39:47 +0000
committertv <tv@krebsco.de>2026-11-16 10:39:47 +0000
commit3f503ae76e1ca324c9fe2f6a2ff2c9289527ee6a (patch)
tree03359a4092493ef643c12f94a1c046bc02ebdca0
parentc8663d869be0ef719cc234da51d8f4924ef0d864 (diff)
federation: no remake followed whose coordinator its party no longer lists
A node taken off its party's list is a member at a history from before: a remake's record, proposal and decision it writes there are taken, and every node listed at its base follows, the snapshot listing the node again until the list that took it off is replayed. "The next remake's base" could be its own. A node follows a remake only where the coordinator's party lists the coordinator, as the node reads it when it switches; and what a node taken off its list commits from a history before ends with a remake whose base holds that list.
-rw-r--r--docs/federation.md15
1 files changed, 9 insertions, 6 deletions
diff --git a/docs/federation.md b/docs/federation.md
index afe48d8..53da9da 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -78,7 +78,8 @@ Not promised:
nor that nodes follow one remake where two were decided for one epoch: each follows
the one it holds, until operators name one (Remakes);
* that a node taken off its party's list can't still commit at a history from before:
- from the next remake's base on, it can't;
+ from a remake whose base holds that list on, it can't, and no node follows a remake it
+ coordinates;
* anything to a node with an empty document: it takes the epoch its peers give it, or
the one its operator pins (Remakes).
@@ -512,10 +513,11 @@ federated node asks of a remake:
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, and so is its abort: whether one expired is no node's to say,
- and one its coordinator leaves undecided binds nobody. 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.
+ its coordinator's alone, and so is its abort, and a node follows one only where the
+ coordinator's party lists the coordinator, as the node reads it when it switches:
+ whether one expired is no node's to say, and one its coordinator leaves undecided
+ binds nobody. 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.
* **Two decisions for one epoch** come from a coordinator that wrote two, or from
remakes decided at once. A node that holds both follows neither, says so, and leaves
it to its operator. On its operator's word, a node builds the remake named of the
@@ -674,7 +676,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang
| 40 | Different changes to different peers | Honest nodes agree once they sync, but where keys voted twice, a coordinator decided two remakes for one epoch, or a writer forked | sim |
| 41 | A party withholding its changes or votes | Not promised | — |
| 42 | Flooding: namespace, proposals, history | Slow, not wrong | bench |
-| 43 | A node taken off its list writes changes at a history where it was on | Taken where valid there; ended by the next remake's base | unit |
+| 43 | A node taken off its list writes changes at a history where it was on | Taken where valid there; ended by a remake whose base holds that list | unit |
| 44 | A token from another node, even one its party lists | Refused: a node takes only its own | unit |
| 45 | A party lists another party's nodes, or one its party dropped | Nothing changes: a node is its own party's | unit |
| 46 | A party lists many nodes, to be every node's neighbours | Each node keeps some among its own party's and those its operator names | sim |
@@ -714,6 +716,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang
| 80 | An honest party backs a second proposal once its first is dead; another party later signs `true` on the first too | It isn't named: its first proposal is dead by all the votes; the party with `true` and `false` on one is | unit |
| 81 | A node whose operator had it drop a version is sent it again, or holds the votes that passed it | It refuses those changes and writes the version no more, in that epoch, until its operator says otherwise | unit |
| 82 | A key its party dropped wrote, from a history before the drop, ahead of the party's envelope; then a remake or a fork | The snapshot or genesis keeps the party's value, as the federation reads it | unit |
+| 83 | A node taken off its list proposes and decides a remake at a history where it was on | Nobody follows it: a node follows a remake only where its coordinator's party lists the coordinator when it switches | unit |
## Roads not taken