aboutsummaryrefslogtreecommitdiffstats
path: root/docs/guides/federation/upgrades.md
diff options
context:
space:
mode:
authortv <tv@krebsco.de>2026-11-18 12:38:19 +0100
committertv <tv@krebsco.de>2026-11-18 12:38:19 +0100
commit257ad0391ff8eba437108e1885c45314e9fd5833 (patch)
tree3098609e38125c0afb326efeb41a08d0045da3d4 /docs/guides/federation/upgrades.md
parentcfe3dbaff24b5ae433b3203d69c7e9bceb4e1ccc (diff)
parent55f36a960a90aedcb6e899ea963cc642fd630a82 (diff)
Merge branch 'ecdsa'
Diffstat (limited to 'docs/guides/federation/upgrades.md')
-rw-r--r--docs/guides/federation/upgrades.md7
1 files changed, 7 insertions, 0 deletions
diff --git a/docs/guides/federation/upgrades.md b/docs/guides/federation/upgrades.md
index 945088d..95dab12 100644
--- a/docs/guides/federation/upgrades.md
+++ b/docs/guides/federation/upgrades.md
@@ -32,3 +32,10 @@ naming another is taken as a proposal, and a party's client backs none.
A change to any of that is a federation of its own, with the next number, and its own
design. A swarm moves to it by a version naming it, which the parties pass once their
nodes run a continuum that knows it.
+
+A change that only has the federation take what it refused, and reads nothing it took
+otherwise, keeps the number: `ecdsa-sha2-nistp256` keys beside Ed25519 ones. Roll it out
+first, then use it: every party's operators upgrade their nodes, and only then does a
+party name such a key in a version or a key set, or sign with one. A node not upgraded
+refuses what uses it and reads otherwise than the others: a version naming such a key is
+none to it, and it stays on the version before.