docs: move contact discovery to group chats milestone

2026-08-27 09:01:07 +00:00 · 2026-03-23 17:44:26 +00:00
parent e270290e0d
commit ae3d3f313e
3 changed files with 10 additions and 13 deletions
@@ -68,8 +68,16 @@ Group chat features will be limited at this stage and extended with further mile
 - A "user" is represented as a set of installations (devices)
 - Basic association between installations belonging to the same user
 - Basic key rotation: ability to add/remove installations
- Basic device recovery mechanism

+### Implement contact discovery
+
+**Owner**: Chat Team
+
+The implementation should replace v0.1 out-of-band intro bundle sharing.
+Current agreement is to use on-chain storage.
+
+> [!WARNING] Risk
+> Requires research into whether Logos Blockchain supports the needed functionality by this timeline. Fallback is to continue with out-of-band sharing.
 ### Design SDS and de-MLS integration

 **Owner**: Chat Team
@@ -19,7 +19,6 @@ The Developer Preview focuses on polishing the Logos Chat implementation into a
 The focus is:
 - Stabilize and polish the API based on feedback from v0.2 Status test integration
 - Complete the full identity model
- Replace out-of-band contact discovery with on-chain approach
 - Test and fix integration issues at scale with DST
 - Deliver user-facing features needed for a real chat experience

@@ -50,16 +49,6 @@ Building on the simple identity model from v0.2:
 - Optional binding to external identity systems
 - Specification and implementation, in collaboration with AnonComms team

-### Implement contact discovery
-
-**Owner**: Chat Team
-
-The implementation should replace v0.1 out-of-band intro bundle sharing.
-Current agreement is to use on-chain storage.
-
-> [!WARNING] Risk
-> Requires research into whether Logos Blockchain supports the needed functionality by this timeline. Fallback is to continue with out-of-band sharing.
-
 ### Stabilize and polish API

 **Owner**: Chat Team
@@ -16,7 +16,7 @@ date: 2026-03-01

 Logos Chat is feature-complete, production-ready, and QA-approved for mainnet deployment. By this point, identity and user-facing features are already delivered (v0.3). This milestone focuses on production hardening:

- Production-grade reliability at scale (beyond the ~200 users tested in v0.3)
+- Production-grade reliability at scale (beyond the ~201 users tested in v0.3)
 - Comprehensive documentation for production deployments
 - Performance optimization for mainnet user projections
 - API stability guarantees