diff options
| author | tv <tv@krebsco.de> | 2026-11-19 14:42:45 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 15:53:14 +0100 |
| commit | 33be6b959c9777c40ca2b16507e9f4f60d6d2d44 (patch) | |
| tree | 9939a86e950edeeac619798f46a6c42c3bc9388b /docs/guides/federation/voting-by-itself.md | |
| parent | a67c96469d2d06e85c4be69a725af7b93fb023a2 (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/voting-by-itself.md')
| -rw-r--r-- | docs/guides/federation/voting-by-itself.md | 6 |
1 files changed, 3 insertions, 3 deletions
diff --git a/docs/guides/federation/voting-by-itself.md b/docs/guides/federation/voting-by-itself.md index 73e9df8..ebde0cf 100644 --- a/docs/guides/federation/voting-by-itself.md +++ b/docs/guides/federation/voting-by-itself.md @@ -79,9 +79,9 @@ while before it was proposed, proposals and votes aside ([`checkpoints.md`](checkpoints.md), [Backing one](checkpoints.md#backing-one)). A vote by hand through it keeps to the same. -It signs its votes on the events proposing what it votes on, of a checkpoint those above -its heads, and its checkpoint proposals on its heads, so that a version event may be -written on them. +It signs its votes on an event proposing what it votes on, of a checkpoint one above its +heads, and on the nays that freed its party, but for a checkpoint; and its checkpoint +proposals on its heads, so that a version event may be written on them. ## Watching it |
