diff options
Diffstat (limited to 'docs')
| -rw-r--r-- | docs/devel-phases-next.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/docs/devel-phases-next.md b/docs/devel-phases-next.md index 48620ca..e842b62 100644 --- a/docs/devel-phases-next.md +++ b/docs/devel-phases-next.md @@ -1109,7 +1109,7 @@ flags. Additions that belong in the user-facing docs: | 15.3 | Node: decrypt chat on receive | Decrypt incoming chat messages, handle out-of-order | | 15.4 | Key rotation on removal | Member removed **or device revoked or unpinned** → all remaining devices rotate | | 15.5 | Chat retention config | Per-group `max_age_days` setting, periodic cleanup in ChatStore | -| 15.6 | MNP version negotiation | Handshake declares a supported version range, not a single `v` field (L2 — today `v` is sent by everyone and checked by no one). **Move this earlier**: it pairs with the minimum-client-version check, and version skew begins the day the desktop client ships (`desktop-client-v1.md` §2.6), not when chat is encrypted | +| 15.6 | MNP version negotiation | ✅ **DONE 2026-09-03**, and not here: it shipped with **MNP 1.0** (the sealed index and ack), which forced a coordinated deployment anyway. `handshake` and `handshake_challenge` each carry `v` and `v_min`; `check_version` refuses with `version_too_old` / `version_too_new` / `version_unreadable`, shaped like `not_a_member`. The flag day was already being paid for, so the next breaking change costs a refusal message instead of a second one. See `MESHBAY_NODE_PROTOCOL.md` §13.1 | | 15.7 | Chat attachments | Attachments are ordinary files on the node and remain plaintext at rest. Either encrypt them under the sender key, or document the asymmetry explicitly. Note they now land in the **operator-designated upload root** (§6.7 of the desktop-client doc) | --- |