diff options
| author | tv <tv@krebsco.de> | 2026-11-15 04:41:15 +0000 |
|---|---|---|
| committer | tv <tv@krebsco.de> | 2026-11-15 04:41:15 +0000 |
| commit | d4745d965493a2687bd6b0b526882d5b19a92211 (patch) | |
| tree | 36c79fec225d32eb5f6bca698033ddcfbe79512e /docs/federation.md | |
| parent | c169c74c31d5ca2fd0e1e3ed916e1abf78b9c5ad (diff) | |
federation: a removed key is the party's not to add again
Nothing remembers removed keys, so no node can refuse one added again;
the design says it is the party's to keep from doing, as it would
bring back what that key signed.
Diffstat (limited to 'docs/federation.md')
| -rw-r--r-- | docs/federation.md | 3 |
1 files changed, 2 insertions, 1 deletions
diff --git a/docs/federation.md b/docs/federation.md index 8d709ff..13fd53a 100644 --- a/docs/federation.md +++ b/docs/federation.md @@ -220,7 +220,8 @@ be put back wherever its place is empty, by anyone who holds it; it counts if it still its party's and its party may write there. Housekeeping empties a place only where that can't be: by (1), where its party may not write; by (2), once its party holds no keys; by (3), once its party holds none of the keys it held when it deleted, the only ones -that can have signed what came before. A removed key is never added again. +that can have signed what came before. A party never adds a key it removed again: nothing +remembers removed keys, and it would bring back what that key signed. ### Keys |
