List view
All SDK repositories will be consolidated into the libxmtp monorepo with unified build, test, lint, and release infrastructure.
No due date•2/13 issues closed- No due date•5/18 issues closed
Self Removal
Overdue by 4 month(s)•Due by October 24, 2025•3/4 issues closed- Welcome message includes cursor of which messages to sync from, efficiency improvement - MessageV2
Overdue by 6 month(s)•Due by September 4, 2025•1/1 issues closed- Automated Fork Recovery - Self Removal
Overdue by 5 month(s)•Due by September 19, 2025•2/2 issues closed- Overdue by 10 month(s)•Due by April 14, 2025•5/6 issues closed
- Overdue by 1 year(s)•Due by March 5, 2025•4/4 issues closed
- No due date
Libxmtp should be able to speak to the new nodes for all core functionality. Includes: - New API client talking to xmtpd - Including dependencies on published messages - Topological sort of returned messages - Handling new originator ID and sequence_id - Support for reliable streams - Basically everything in https://github.com/xmtp/libxmtp/issues/1637 Does not include: - Client signatures of Authenticated Data - Misbehavior reports - Payer Service in the client
Overdue by 11 month(s)•Due by March 21, 2025•5/7 issues closedMinimum changeset that achieves: 1. Running libxmtp in a dual SDK - clients merge messages from v2 and v3 2. V3 changes do not regress security compared to v2 Does not need to be forward compatible - payloads can be stored/read from namespaced topics that are discarded in the next milestone.
No due date•14/15 issues closed