diff options
| author | tv <tv@krebsco.de> | 2026-11-15 21:46:38 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-15 21:46:38 +0000 |
| commit | acb8d25d510f3c04e8beb03ad5cd26556adfa8b1 (patch) | |
| tree | 0fe0c54c8cae8dcf5cb9176bf4c4d66e355687f4 /src/access/challenge.rs | |
| parent | 6ae5da042629d085a2410bcca68a4d697a44854a (diff) | |
federation: votes by their version's keys, a federation starts empty
A vote and a proposal now count by the keys their version names for
their party: every version names every party's keys, and the parties
are the names of those keys. So a vote is checked from itself and its
version alone, and a remake replays it as cast in whatever order key
sets of its party go around it; replaying votes before key sets, which
no order could meet where two parties' key sets and votes cross, goes,
with the rule treating two key sets at once as voting twice. A party's
own key change reaches its votes with the next version naming its keys.
A federation's genesis change is its swarm's first, so it starts empty:
content before it would be a change judged by none. A fork's genesis is
built byte for byte, so one version and one set of heads make one
swarm. A member's entry is its member's only, removed whole; logouts,
sessions and forgotten nodes are closed, and a write at the policy's
place refused. Rule 7 waits for what was written beside a `null` too; a
`null` housekeeping deleted after a base is back for an epoch. A party
signs its node list again with its keys. "Why it holds" says what a
remake keeps. Rows for what this answers.
Diffstat (limited to 'src/access/challenge.rs')
0 files changed, 0 insertions, 0 deletions
