aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/proposing-and-voting.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 14:42:45 +0000
committertv <tv@krebsco.de>2026-11-19 15:53:14 +0100
commit33be6b959c9777c40ca2b16507e9f4f60d6d2d44 (patch)
tree9939a86e950edeeac619798f46a6c42c3bc9388b /docs/guides/federation/proposing-and-voting.md
parenta67c96469d2d06e85c4be69a725af7b93fb023a2 (diff)
vote: a second `true` builds on the nays that freed its party
The federation takes a party's `true` only where, at its history, every other proposal it backed on that version is dead. A party's client, and a node voting by itself, built a vote on the events proposing what it votes on alone. A proposal made while the party's first `true` was alive, at a history holding it, holds that `true` in its history, and not the nays that ended the first proposal later: the party's `true` on it was refused, though its record cast it. The compromise case: five back X, Y is proposed, X dies, its backers back Y. A vote now builds on one event proposing what it votes on, and on the nays that freed its party (`client::building`), so the first proposal is dead at its history too. One event proposing it is enough, so many proposing it again don't push a vote past the dependencies an event may name. A checkpoint's vote builds on its proposal alone: one of those nays in the history of its heads, named, would put the vote beside them. A party freed only after the heads were named backs that checkpoint not, and its client says so before casting; it backs one proposed after. Row 74 is tested (`federation_attack_74`); federation.md and the guides say so.
Diffstat (limited to 'docs/guides/federation/proposing-and-voting.md')
-rw-r--r--docs/guides/federation/proposing-and-voting.md8
1 files changed, 6 insertions, 2 deletions
diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md
index 9b50e09..e91806c 100644
--- a/docs/guides/federation/proposing-and-voting.md
+++ b/docs/guides/federation/proposing-and-voting.md
@@ -93,8 +93,12 @@ record before it sends the vote. It casts no vote that would make its party vote
* `true` only for a version changing the current one, whose checkpoint names none of the
current checkpoint's heads;
* one `true` at a time: another `true` on the same version only once the proposal the
- party backed is dead. The client fetches the votes that made it so from the node, and
- keeps them in the record beside the new `true`.
+ party backed is dead. The client fetches the votes that made it so from the node, keeps
+ them in the record beside the new `true`, and builds the `true` on them, so that the
+ first is dead at its history too: the proposal it backs next may have been proposed at
+ a history holding its first `true`. A checkpoint's `true` it builds on the proposal
+ alone, and says when it may be refused so: where the nays came after the heads the
+ checkpoint names, back the one proposed after.
A `true` holds the party until its proposal passes or is dead, and only other parties'
nays make it dead. Where ending it would take every party yet to vote, or more, and those