diff options
| author | tv <tv@krebsco.de> | 2026-11-16 04:18:21 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 04:18:21 +0000 |
| commit | ed6ad252be5e3b0c355ab6a508e1e27e207d4c6a (patch) | |
| tree | b134b6bf20e635e6f8ff70fba68f920ed5dc6e18 /docs | |
| parent | dabebef65ee6c9bbf9f4483ab5c18f006d928291 (diff) | |
federation: an operator may have its node drop what it took
Where keys voted twice, or a writer forked, each node kept what it took,
and the sides came together only by a fork, a node with an empty
document, or its peers' word. An operator may have its node drop a
version, or any change, with everything built on it, as continuum drops
a change its node took and the rules refuse (`drop_taken`), and take
what the others hold: no peer's word moves a node, its operator's does.
So either side may join the other without what parts them, as the
design request asked, without a fork.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/federation.md | 24 |
1 files changed, 18 insertions, 6 deletions
diff --git a/docs/federation.md b/docs/federation.md index 04c8995..93fb41e 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -69,10 +69,11 @@ Not promised: remakes from committing, makes nodes slow, not wrong: denial of service breaks no promise here, and the others fork away from it; * that honest nodes stay together where keys voted twice (Changing the policy): each - node keeps the version it took, and one that had taken neither of two (it lagged - behind, or joins) may be shown either first; + node keeps the version it took, until its operator has it drop it, and one that had + taken neither of two (it lagged behind, or joins) may be shown either first; * that honest nodes stay together where a node commits two changes under one writer - and number: they are apart until a fork (Where Automerge sets limits); + and number: they are apart until operators have one side drop what it took, or a + fork (Where Automerge sets limits); * that a remake reaches every node: one that can't build it itself stays where it is; nor that nodes follow one remake where two were decided for one epoch: each follows the one it holds, until operators name one (Remakes); @@ -284,6 +285,14 @@ rules. Of two that change the one it reads, it takes the first it judges. Withou voting twice, every version written changes the one every node reads, and none is refused. +**An operator may have its node drop what it took**: a version the others refused, or +any change, with everything built on it, as continuum drops a change its node took and +the swarm's rules refuse (`drop_taken`: the document as it would be without them, the +node's own writes among them to its quarantine), and then take what the others hold. +No peer's word moves a node; its operator's does. So either side of keys that voted +twice, or of a writer forked, may join the other without what parts them, and without a +fork. + **The current version** is the written version with the highest number: the end of the chain the node took, read from what the document holds without the versions behind it, which a remake leaves out (Remakes). @@ -566,7 +575,9 @@ long nodes stay together. splits the nodes that took one from those that took the other: a node holding one can't take the other. Continuum refuses the second as forged, by whoever brings it *(checked: `Signatures::forks`)*. No remake brings the two sides together, as neither - builds from a base holding what it refused; a fork at heads both hold does. + builds from a base holding what it refused; an operator having its node drop the + change it took, and take the other, does (Changing the policy), and so does a fork at + heads both hold. * **History.** The document keeps every operation, which only remakes bound. ## Why it holds @@ -687,6 +698,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang | 76 | Two thirds back a proposal that is no version | It can't be written, nor die; the federation is bound to its version. A node shows that it is none, and clients don't back it | unit | | 77 | A party's vote committed again at a history before the nays that freed it, its clock set between, then a remake | The replay refuses it at first, and takes it once the rest is in | unit | | 78 | A listed node starting a fresh writer with every change | Refused past the bound on the writers a node starts in an epoch | unit | +| 79 | Keys voting twice, or a writer forked, part honest nodes | An operator has its node drop what it took and take the other side's; no fork | sim | ## Roads not taken @@ -802,8 +814,8 @@ On a federated swarm: within what a sync message carries. A node that doesn't know the policy stops taking changes. Until stage 4, a federated swarm takes no remake. 2. **What counts**, read by the current version and the keys; shown in the API. - Reports of the versions a node refused; a tool reporting, from the votes, a party - that voted twice. + Reports of the versions a node refused, and its operator having it drop what it + took; a tool reporting, from the votes, a party that voted twice. 3. **Nodes**: membership by the node lists and the party a node's own entry names, the party shown in the handshake before that entry exists, a node syncing with members only (a wire change), neighbours by party. |
