From 03744437a5ffc36fbb5e973a0ddfd6b91945b212 Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 01:48:57 +0000 Subject: 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`). --- docs/openapi.yaml | 8 +++++--- 1 file changed, 5 insertions(+), 3 deletions(-) (limited to 'docs/openapi.yaml') diff --git a/docs/openapi.yaml b/docs/openapi.yaml index 57ef132..349f943 100644 --- a/docs/openapi.yaml +++ b/docs/openapi.yaml @@ -1529,13 +1529,15 @@ paths: What counts, as the store reads now (docs/federation.md): the current version (its number, its hash, and the version itself), each party's keys and nodes, the value at each place, the members, each `[node, party]`, and the proposals on the - current version, by their hash, each with the IDs of the events proposing it - (`proposals`) and of the votes on it (`votes`), the parties voting `true` (`yes`) + current version, by their hash, each with the IDs of the events proposing it that + a vote may build on (`proposals`: of a version naming a checkpoint, those above + its heads) and of the votes on it (`votes`), the parties voting `true` (`yes`) and `false` (`no`), whether it passed (`passed`: two thirds of the parties voted `true`) and whether it is dead (`dead`: so many voted `false` that the rest can't pass it), and why a party's client backs it not (`none`), where it is no version, none changing the current one, or one naming the heads of the current one's - checkpoint, as this node reads it: one that passed all the same is never written, + checkpoint, as this node reads it, or no event proposing it is above the heads it + names: one that passed all the same is never written, or, no version here, this node stops at its version event. A passed proposal is written at once, and lapses with the rest. responses: -- cgit v1.3.1