diff options
| author | tv <tv@krebsco.de> | 2026-11-16 11:47:04 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-16 11:47:04 +0000 |
| commit | 3fee8e14e076bc0363558c20440af9394a695e12 (patch) | |
| tree | 09c456022746f23d1273de101a1d2b25b397c1da /docs | |
| parent | 9fa62c47e4d50cb143473002c4d55482d0aa5bed (diff) | |
federation: a dropped version refused however it is written
A node refused the changes its operator had it drop. But any member
writes a version once it passed, and a change writing the dropped version
anew, by a lagging node by chance or a listed adversary at will, was none
of those: the node took it, as it changes the version the node reads, and
a node its operator was moving across a remake stayed. The node refuses
any change writing a version among those it dropped.
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/federation.md | 10 |
1 files changed, 5 insertions, 5 deletions
diff --git a/docs/federation.md b/docs/federation.md index f70003b..0511fe9 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -295,10 +295,10 @@ any change, with everything built on it, as continuum drops a change its node to 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. In that epoch the node refuses the -changes it dropped, from whoever brings them, and writes no version among them again, -though it holds the votes that passed it, until its operator says otherwise. 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. +changes it dropped, from whoever brings them, and any change writing a version among +them, whoever wrote it anew, and writes none itself, though it holds the votes that +passed it, until its operator says otherwise. 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, @@ -718,7 +718,7 @@ What an attacker does, and what happens. *Unit*: the judging, with crafted chang | 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 | 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 | | 79 | 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 | -| 80 | 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 | +| 80 | A node whose operator had it drop a version is sent it again, written anew by another member, or holds the votes that passed it | It refuses any change writing that version and writes it no more, in that epoch, until its operator says otherwise | unit | | 81 | 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 | | 82 | 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 | | 83 | A party taken out and let in again within an epoch | The list it wrote before counts no more: its list's `since` is the version that let it in | unit | |
