aboutsummaryrefslogtreecommitdiffstats
path: root/src/simtest/soak.rs
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-12 20:05:49 +0000
committertv <tv@krebsco.de>2026-11-12 20:05:49 +0000
commitf95719a58800bedd5ee021d8bdfac30dc23956ef (patch)
tree0220da9c138865706304855a03f4df4802cf4454 /src/simtest/soak.rs
parent4aaeb002f4309efaa9aee2e10b2c16fdf69f314f (diff)
federation: several roots, final names, every voter counts
The design as it stands after being read against itself and the code: * A statement says where it was signed: its payload names the changes its signer saw. "In sight of", the order past a limit and a proposal's number are read from that, so carrying a statement a second time moves nothing. A statement that is counted states its number. * A node carries for a user once it committed the statement naming it itself. Tokens and logins by key are taken as a node's operator says. * Lines say who is in and nothing else. A claim's witnesses are its user's nodes and the roots'. * The roots are several, named by an epoch's root change like the voters: by the genesis change, then by each remake. What a root signed for another is the seats' once its signer holds none, and the roots take that back only together. * A claim seen holding its name for `final` by a third of the voters is final: no rival holds or contests the name after, whatever a root says and whatever is cut off. It takes no root. * A claim made in sight of one that didn't stand doesn't give way to it when it comes back (its user vouched for again, a limit raised); only a release or a cut that a cut takes back does that, until the later claim is final. Late is witnessed by a change that saw the other stand while the claim didn't. * A cut never leaves out its own statement, and takes back what the key it cuts retired, stopped and unvouched. Giving a user up takes a first key. * Every voter counts toward a decision: more than two thirds of all. Nobody is absent; a remake names those who take part, and a voter votes while it isn't gone. Any node of a voter takes a proposal up; every node judges a record against the votes in its history; a proposal is decided at a record that has two thirds of them in its history. A node takes up nothing lower than it took up, the highest number holds, and what hangs short of records shows and is ended by a later decision. A change is judged by what is decided in its history; the registry is resolved by what holds. * What is decided: numbers, the policy, first keys, the names of a user that is out, whose a contested name is, the voters' names, and a remake with the voters and the roots it names. * A remake: every node carries over what it holds beyond the base, whoever signed it, in its first changes and in order; the root change lists the digests of the base's statements, so nothing it left out is written again; decisions after the base are taken up again, and what a third of the voters' nodes held as gone, final or dropped stays so. An epoch's remakes are one matter. * A kind may name the characters of its names (lower case recommended); a kept name may be claimed, to stay through a change of policy. * The genesis change may hold users, without keys too, so a registry moved in has its users from the first change. * How often nodes stamp, a member entry's size, and what the genesis change sets for the swarm as a whole are numbers of the policy. * A node compares what it resolves with the stamps of the voters' nodes, and stops writing only where a third of them differ. Two wire versions spoken at once is a change for every swarm. * Stages: versions before remakes; the registry stage is for trying, the last for relying on it. 110 attacks.
Diffstat (limited to 'src/simtest/soak.rs')
0 files changed, 0 insertions, 0 deletions