diff options
| author | tv <tv@krebsco.de> | 2026-11-15 18:57:48 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-15 18:57:48 +0000 |
| commit | 767364b2906cacc15699fead626b552617aff111 (patch) | |
| tree | 0b56dc1b7ec246e9cb7953b2c3dc4d7c7a6b1f1f /src/access/token.rs | |
| parent | 802a590ac477124c39068cd7caf094a919a2dc5d (diff) | |
federation: the highest number, a double vote answered by a fork
The current version is the written version with the highest number, of
two with one number the lower hash: a number is checked where its
version is written, so this is the end of the chain, read without the
versions behind it, which housekeeping may delete.
A double vote both sides built on can be read one way and then the
other while votes cast before the sides met come in, and what was
written under the version not read ranks with the other's, a thief's
key set among them. The parties answer it by forking without the party
that voted twice; a report of one comes from the history, never from
the document as a whole.
A node's party is its operator's, in its configuration: another party
listing it changes nothing. Replay goes by history and by the version
named, deletes what counts no more beneath a new holder's chain, and may
leave out a `null` once a later version is current; housekeeping may
delete a `null` once all it covers was signed by keys its party dropped.
The federating change is the one the policy's writes lead back to, and
one beside it is refused: a tie broken by hash would let a change made
later to look as old take its place. A fork's first version names the
highest at the fork's heads, the fork is named by its genesis change's
hash, and joiners are told whose keys the fork changed.
Leftovers: the keys a version sets spelled as an unsigned envelope;
client advice out of the rules; `null` at a proposal's place gone;
literal rules before `{party}` ones; node lists in stage 1; rows for
what this opens.
Diffstat (limited to 'src/access/token.rs')
0 files changed, 0 insertions, 0 deletions
