From efaf79e7fd55db2b9704ccefedde33346f874a1d Mon Sep 17 00:00:00 2001 From: tv Date: Thu, 19 Nov 2026 03:56:57 +0000 Subject: vote: a node proposes a checkpoint at the heads it holds A node proposed a checkpoint at the heads of what it held for a while: every event written in that while, and every one built on an event beside those heads, as one party writing now and then on something old makes them, was beside them, and refused once the store moved. A voter whose while was shorter backed none, one whose while was longer backed it and lost those. It proposes at the heads its store holds, sorted: what was written before is in their history, and only what is written while the vote takes its course may be beside them. It proposes none where they are more than an event may name: under a revision with merge events, it merges them first; otherwise, what is written after does. `--store-held-for` keeps the voters' rule and how long a new proposal holds back a checkpoint. `federation.md`, the guides and the options say so. --- docs/federation.md | 71 ++++++++++++++++++++++++++++-------------------------- 1 file changed, 37 insertions(+), 34 deletions(-) (limited to 'docs/federation.md') diff --git a/docs/federation.md b/docs/federation.md index d10a220..30bff6e 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -462,36 +462,37 @@ than it may name dependencies. The current checkpoint at a history is the one th version of that history's chain that names one names, or else the root: a question of the history alone. As the version naming the current checkpoint is among the next checkpoint's heads or in their history, every later version naming one names heads after those, and a -node starting from a checkpoint holds what judging them reads. A proposer names heads it -has held for a while, by its own clock, which judges nothing, so that every node holds -them. A party's client, and a node voting by itself, back a checkpoint only where -everything they held for a while before it was 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 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 checkpoint refuses -nothing that decided it. A party's client, and a node voting by itself, vote on the events -proposing what they vote on that are above those heads, as a node shows them, and a node -proposes a checkpoint on its heads: so their votes are above those heads wherever the -proposal is. One proposing it again beside them they don't build on, as a vote on it would -be beside them too. A vote beside them binds its party as any yes does, until the move -refuses it. A node that takes the version moves to the checkpoint: it builds it, forgets -everything before those heads that it doesn't keep, and every event not above them, and -refuses such events from then on. Judging an event after them needs nothing it forgot: the -version, every party's keys and node list, and the proposals on the current version with -their votes all count, and are kept. A node starting from a checkpoint reads what it keeps -as written under its version, as it holds none of their histories: each was written under -that one or an earlier, counting there, a kept proposal is on it, and a later `since` that -leaves one out is past it. A node that can't build a checkpoint, as it was away across a -move and a remake after it, or as it joins, takes it only where its operator pins it -([`store.md`](store.md), [Pinned checkpoints](store.md#pinned-checkpoints)). What it can't -check of its heads it takes on its operator's word: that they are after the checkpoint -current at the version naming them, at which that one is current too; so it judges that -version as every node does. +node starting from a checkpoint holds what judging them reads. A proposer names the heads +it holds as it proposes, so that what was written before is in their history: a node +lacking one takes the proposal once it holds it. A party's client, and a node voting by +itself, back a checkpoint only where everything they held for a while before it was +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 +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 +checkpoint refuses nothing that decided it. A party's client, and a node voting by itself, +vote on the events proposing what they vote on that are above those heads, as a node shows +them, and a node proposes a checkpoint on its heads: so their votes are above those heads +wherever the proposal is. One proposing it again beside them they don't build on, as a +vote on it would be beside them too. A vote beside them binds its party as any yes does, +until the move refuses it. A node that takes the version moves to the checkpoint: it +builds it, forgets everything before those heads that it doesn't keep, and every event not +above them, and refuses such events from then on. Judging an event after them needs +nothing it forgot: the version, every party's keys and node list, and the proposals on the +current version with their votes all count, and are kept. A node starting from a +checkpoint reads what it keeps as written under its version, as it holds none of their +histories: each was written under that one or an earlier, counting there, a kept proposal +is on it, and a later `since` that leaves one out is past it. A node that can't build a +checkpoint, as it was away across a move and a remake after it, or as it joins, takes it +only where its operator pins it ([`store.md`](store.md), +[Pinned checkpoints](store.md#pinned-checkpoints)). What it can't check of its heads it +takes on its operator's word: that they are after the checkpoint current at the version +naming them, at which that one is current too; so it judges that version as every node +does. What a checkpoint loses: what counted no more before it, so that a key added back, or a place given back, brings back nothing signed before it, and a party that voted twice on @@ -499,8 +500,8 @@ a version behind it shows only in the votes kept outside the store: a client kee own votes and the nays that freed it, not another party's two, so where keys voted twice, whoever saw it keeps the votes naming the party (`GET /events/{id}`) before a checkpoint leaves them out; and what isn't above its heads, which its party signs again. Few are: the -heads are ones its proposer held for a while, no voter backs heads that leave out what it -held for a while, nodes build on them while the vote takes its course, a client writing +heads are those its proposer held as it proposed, no voter backs heads that leave out what +it held for a while, nodes build on them while the vote takes its course, a client writing once a checkpoint is proposed builds only on what is above its heads, and a party's client signs again what a move refused. @@ -541,8 +542,10 @@ as it judges any vote or proposal. The design has two in mind: revision it follows never: its party's operators vote on that one by hand, once their nodes run a continuum that knows it ([Changing the federation](#changing-the-federation)). -* **Proposing a checkpoint**: propose a version that only moves to a checkpoint, at - heads the node has held for a while, once conditions its operator sets are met: so +* **Proposing a checkpoint**: propose a version that only moves to a checkpoint, at the + heads the node holds, where they are no more than an event may name (a node merges them + first, under a revision with merge events, [Nodes](#nodes)), once conditions its + operator sets are met: so many events or bytes held beyond its checkpoint, so many versions since it, or so long by its own clock, by which nothing anyone judges goes. One after every version ends, at the checkpoint, what keys voting twice could grow beside that version at a history -- cgit v1.3.1