diff options
| author | tv <tv@krebsco.de> | 2026-11-19 01:48:57 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 03:18:49 +0100 |
| commit | 03744437a5ffc36fbb5e973a0ddfd6b91945b212 (patch) | |
| tree | 227eb42b4e7cac546b857cfacb79ab890e8bb137 /docs/guides/federation/proposing-and-voting.md | |
| parent | f24063e90d02ef76d87401d6e74cf8c9f489ff7d (diff) | |
federation: votes on the events proposing a checkpoint above its heads
Anyone could propose a checkpoint's version again, by an event beside its heads. A node
voting by itself, and a party's client, built a vote on every event proposing what it
voted on, so every vote was beside the heads, and no version event written on them was
taken: the checkpoint could never move the store. And the voters' rule refused it once
that event was held for a while, as the heads left it out.
They vote on the events proposing it that are above the heads it names
(`State::proposing`), which `GET /events/counts` lists as `proposals`; where there are
none, `none` says so, the node casts nothing and the client says why. The voters' rule
leaves proposals and votes aside, as they lapse with the move.
Row 70 is tested (`federation_attack_70`).
Diffstat (limited to 'docs/guides/federation/proposing-and-voting.md')
| -rw-r--r-- | docs/guides/federation/proposing-and-voting.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/guides/federation/proposing-and-voting.md b/docs/guides/federation/proposing-and-voting.md index 0f303ea..2bf0dee 100644 --- a/docs/guides/federation/proposing-and-voting.md +++ b/docs/guides/federation/proposing-and-voting.md @@ -65,7 +65,8 @@ version must (its `number`, `changes`, and each `since`), whose checkpoint, wher one, names none of the heads of the current version's checkpoint, as such a version is never written. It says why it doesn't propose one otherwise. The proposal is on the current version, and its hash is the version's: the node shows it under that -hash (`proposals` in `GET /events/counts`), with the events proposing it. +hash (`proposals` in `GET /events/counts`), with the events proposing it that a vote +may build on: of a checkpoint, those above its heads. Several parties proposing the same version make one proposal. The key a party proposes and votes with is one the current version names for it, not one of its key set: the client checks that before it signs, and records nothing otherwise. |
