aboutsummaryrefslogtreecommitdiffstats
path: root/docs/federation.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-19 16:21:02 +0000
committertv <tv@krebsco.de>2026-11-19 17:36:20 +0100
commit602718835d034ef0a96c8ca29e47f06ce37008dc (patch)
tree99a1ffbf50a4f59b3a5078dafa8c0cb3d192632c /docs/federation.md
parent9784111bd3b95be5352669b74e174920c101f349 (diff)
events: what moving to a proposed checkpoint refuses, shown
federation.md, and row 68, said a node shows, for a proposed checkpoint, what it holds that its heads lack; no node did. `GET /events/counts` now shows, of each proposal whose version names a checkpoint, the writes, key sets and node lists the node took that moving there refuses (`beside`; null for another version): neither among its heads, in their history, nor above them, as the move has it, which their parties sign again. Proposals and votes lapse with the move, and merge events count for nothing: they are left out. `Store::beside` finds them in one pass, as the move itself does: the two share `Store::above`, which the move computed inline.
Diffstat (limited to 'docs/federation.md')
-rw-r--r--docs/federation.md8
1 files changed, 5 insertions, 3 deletions
diff --git a/docs/federation.md b/docs/federation.md
index e13ff8a..df4501e 100644
--- a/docs/federation.md
+++ b/docs/federation.md
@@ -483,8 +483,10 @@ itself, back a checkpoint only where everything they held for a while before it
proposed is among its heads, in their history, or above them, proposals and votes aside,
which lapse with the move: a move refuses what isn't above its heads, and heads a proposer
made up, built on little, would take back what was written since, a key set dropping a
-stolen key among it. A node shows, for a proposed checkpoint, what it holds that its heads
-lack, as for a fork ([Forks](#forks)). This is the voter's rule, by its own clock: nothing
+stolen key among it. A node shows, for a proposed checkpoint, what its parties signed that
+moving there refuses: writes, key sets and node lists it took that are neither among its
+heads, in their history, nor above them (`beside` in `GET /events/counts`), which their
+parties sign again. This is the voter's rule, by its own clock: nothing
more is judged. It is a version only where its proposal is above those heads, and a
version event writing it is taken only where it is above them too, and so is every vote it
is written on ([`store.md`](store.md), [Events](store.md#events)): so moving to the
@@ -815,7 +817,7 @@ yet*: what would answer it better, which isn't built.
| 65 | After a checkpoint, a party that backed a second proposal once its first was dead, the nays that freed it withheld by those who cast them | Not named: its client keeps those nays with its `true` | unit |
| 66 | Two clients of one party back two proposals at once, or its operator votes by hand beside the node that votes for it | Voting twice: a party votes from one client, the node that votes for it where it has one, through which it votes by hand | — |
| 67 | A party keeps a proposal alive that nobody else backs, or two parties of seven or more, to hold back automatic checkpoints | Holds back none past a while: a node proposes a checkpoint beside a proposal it wouldn't back that fewer than a third of the parties back, or nobody but its proposer; a new one holds back for a while, once a version for its proposer | sim |
-| 68 | A checkpoint proposed at heads that leave out what was written since: a key set dropping a stolen key, say | Not backed: clients and nodes back a checkpoint only where what they held for a while is among its heads, in their history, or above them; a node shows what they lack | unit |
+| 68 | A checkpoint proposed at heads that leave out what was written since: a key set dropping a stolen key, say | Not backed: clients and nodes back a checkpoint only where what they held for a while is among its heads, in their history, or above them; a node shows what moving there refuses | unit |
| 69 | A key a version names, stolen, writes its party's node list at a history from before the version naming the party's keys anew, beside the list the party writes under that version, several, for the lowest ID | The party's counts: of a party's lists, those written under the latest version come first | unit |
| 70 | A checkpoint's version proposed again, by an event beside its heads | Voters back it all the same, as a proposal lapses with the move, and vote on an event proposing it above its heads, as a node shows them; a version event on votes beside them is refused | unit |
| 71 | Merge events under the base revision, signed by a node its party doesn't list, by a party's key, or spelled otherwise | Refused, or none: a merge event is taken only under a revision with merge events, signed by a node its party's node list names, its `merge` `true`; it counts for nothing | unit |