Skip to content

Milestones

List view

  • d14n client iteration 2

    Overdue by 4 month(s)
    •
    Due by April 14, 2025
    •5/7 issues closed
    71% complete2 open5 closed

  • MVP for d14n Web

    Overdue by 5 month(s)
    •
    Due by March 5, 2025
    •4/4 issues closed
    100% complete0 open4 closed

  • Decentralization support in xmtp.chat

    No due date
    0% complete0 open0 closed

  • Initial libxmtp support for decentralization

    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 5 month(s)
    •
    Due by March 21, 2025
    •5/8 issues closed
    62% complete3 open5 closed

  • MLS Milestone 1

    Overdue by 7 month(s)
    •
    Due by January 1, 2025
    •12/12 issues closed
    100% complete0 open12 closed

  • V3 Milestone 1B

    Minimum changeset that is forward-compatible with future versions (messages from future versions do not break this version). We should ship this to create a backlog of XMTP versions that understand V3 messages.

    No due date
    •9/9 issues closed
    100% complete0 open9 closed

  • V3 Milestone 1A

    Minimum 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
    93% complete1 open14 closed