diff options
| author | tv <tv@krebsco.de> | 2026-11-19 14:45:14 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-19 15:53:30 +0100 |
| commit | 5c55f04bd2ccfc545930f6bc3cbb148ab5e34ff3 (patch) | |
| tree | 9a581a058c646aaf59378106d250d4feb4b85480 /src/api | |
| parent | c61ee56ad0dad9f3c7468616d89d944eda7f5edb (diff) | |
federation.md: what the attack table's answers lack yet, and what won't come
Reviewers read the design, not the plans kept apart from it. The attack
table says now, where a row's answer isn't the best there could be, what
would answer it better and isn't built (*Not yet*):
* voting twice (12): nodes keeping the two votes, and forks announced in
the swarm, followed where k of m named parties go;
* parties that never vote (18): parties that write and don't vote;
* a stolen key a version names (23): keys for some acts only, and acts
taking two of a party's keys;
* one first version, two federations (37): a salt in the first version;
* joining from the root (63): a join asking its operator every time,
not a restart;
* a party named into another's zone (72): names of one label;
* writing without bound (73): limits the parties set, perhaps per rule;
* a followed party's key, stolen (78): following k of m;
* more than 96 parties (79): votes gathered beneath the version event.
Roads not taken says why a `true` isn't taken back, nor moved once its
proposal is far short, and why no event says a party would back one.
Diffstat (limited to 'src/api')
0 files changed, 0 insertions, 0 deletions
