diff options
| author | tv <tv@krebsco.de> | 2026-11-13 01:11:23 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-13 01:11:23 +0000 |
| commit | bf65523f14b8c372e71e829819f7d3152127976f (patch) | |
| tree | 91a8ff1c6671b3ef641c91068baa622c0844a774 /src/identity.rs | |
| parent | 5b43b3ab2b0ac2a1849b6a5db5a16eba6975b9a8 (diff) | |
federation: one base an epoch, sight decides alone, lists of voters
The design after a second reading against itself and the code:
* An epoch has one remake: a voter's node records one base for its
epoch and no other, and a later proposal is taken up only for that
base, those voters and roots. No node that switched moves again by
itself. The proposal lists the voters by their IDs and names its
coordinator; nothing after it is signed changes the list.
* A voter votes for its epoch, in, out or gone, and the nodes of one
that is out commit their records and nothing else. A node takes up
only a higher number than it took up. A record is read where it was
written.
* Of two claims, one signed in sight of the other: sight decides
alone, asking whether the other stood where the claim was signed.
Late is asked only where neither saw the other, and a claim late
against one that isn't late against it is late for good. A final
claim gives way to none but another final one. An earlier claim
comes back over a later one only where a root's node had seen it
hold the name before it went down.
* What was given up or is left out by a cut comes before nothing, so
a stolen key's statements stand in nobody's way once it is cut off.
* A retirement lists what its cut keeps, so the cut holds after a
remake. After a remake a node states what it held of what it
carries over (which claim late against which, what counts through
an unvouch, which value replaced which), where an order of changes
said it; of several values at one place, one that another replaces
is left out. The snapshot keeps the proposals that are open.
* Giving a user up puts it out, and it is gone after `gone`: a cut
takes it back until then. First keys for a user the root change
holds are given once.
* Writers are counted by a party's budget and put off past
`limits.writers`, never refused. A party, for a budget, is a user
with the users only it leads to.
* A node that follows several users takes a ban where most of them
state it. Between two stamps is read from their histories. The
relays stay an operator's list.
* What is asked of a change before Automerge sees it, as the code has
it. 121 attacks.
Diffstat (limited to 'src/identity.rs')
0 files changed, 0 insertions, 0 deletions
