List view
Once complemented, the economical behaviour of RLN will have been specified, implemented and discussed with the Status team. An implementation of RLN for light clients will also be done, to demonstrate RLN’s UX with onchain Merkle tree. Finally, the smart contract will be deployed on mainnet. It will then be possible to design the usage of RLN in Status.
Due by July 30, 2025https://roadmap.logos.co/waku/milestones/open/2025-explore-peer-discovery-gap The current peer discovery protocols, discv5, is limited in regards to finding peers with specific characteristics (shards, mounted protocols, etc). As such characteristics are filtered after the fact, and not part of the random walk mechanism. This implementation impedes the decentralization of store services and implementation of a mixnet. In this milestone, we will implement PoCs for those two features, to highlight the caveats of discv5 and define requirements for an upgrade of the peer discovery for Waku.
Due by June 30, 2025•1/1 issues closedhttps://roadmap.logos.co/waku/milestones/open/2025-upgrade-waku-for-the-web Harden Waku for the Browser (js-waku as client, nwaku as service node) to build robust and reliable web applications for Logos.
Due by June 30, 2025•1/1 issues closedhttps://roadmap.logos.co/waku/milestones/open/2025-messaging-api Proceed with further Golang code decommission from the Waku stack by defining a Waku Messaging API that includes peer-to-peer reliability; move code implementing it from Golang to Nim; use Nim code in Status Application. Ensure strict separation of concerns between Chat protocols and Waku protocols. Uses clean nwaku c-bindings to revamp the Waku Rust bindings. **DESCOPED** Milestone reworks, some work moved in https://github.com/waku-org/pm/milestone/46 See https://github.com/waku-org/pm/blob/master/2025H2-SUMMARY.md
Due by December 19, 2025•1/1 issues closedhttps://roadmap.logos.co/waku/milestones/open/2025-nwaku-in-status-mobile Proceed with integration of nwaku in Status application on all platforms; including extending scope to light mode and mobile. Use resulting nwaku-based Status apps for dogfooding and documenting last steps to make nwaku default Waku client in Status apps.
Due by June 30, 2025https://roadmap.logos.co/waku/milestones/open/2025-debugging-tools Improve tooling to facilitate debugging and issues, by providing a tool to help with message tracing in logs (Status app, fleet), and enable Prometheus in Status app to get more detailed connectivity states and other metrics on local instances.
Due by June 29, 2025•2/2 issues closedhttps://roadmap.logos.co/waku/milestones/open/2024-acquire-first-10-customers Onboard Waku first 10 customers. Customers are projects using Waku for their peer-to-peer communication stack. First 10 customers assume involvement from the engineering team to get things right and help co-design. Status, Railgun, TheGraph and Portrait should count as the first four.
Due by December 19, 2025•0/2 issues closedhttps://roadmap.logos.co/waku/milestones/open/2024-demonstrate-product-market-fit To demonstrate the viability of Waku as a self-sustainable independent project, user traction and market fitness must be proven. Validation against the market of Waku’s technology and potential USP is needed. Such validation can enable prioritisation of work and potentially dropping undesired features.
No due date•7/7 issues closedhttps://roadmap.logos.co/waku/milestones/open/2024-incentivise-running-infra-node By the end of this milestone, we will have defined a roadmap and implemented a working proof of concept to incentivise node operators running Waku infrastructure for shared shards. In general, Waku infrastructure consists of RLN Relay nodes both forming the decentralised routing backbone for Waku messages and providing a set of services on top of Waku that might be useful for applications. A sustainable Waku infrastructure is necessary within Status to achieve scalability for 1:1 chats and permissionless communities. These Status features use RLN rate-limiting on shared shards as supported by the RLN relay nodes and require a set of decentralised services for Status Mobile and resource-restricted clients, including RLN proofs as a service, Store, Filter and Lightpush. This milestone encapsulates the efforts to distribute rewards for running RLN Relay nodes and getting paid for providing Waku services. This is the first step to providing a sustainable way to scale the Status application.
Due by October 10, 2025•4/4 issues closedpreviously RLN Mainnet https://roadmap.logos.co/waku/milestones/open/2025-rln-mainnet Once complemented, the economical behaviour of RLN will have been specified, implemented and discussed with the Status team. An implementation of RLN for light client will also be done, to demonstrate RLN’s UX with onchain Merkle tree. Finally, the smart contract will be deployed on mainnet. It will be then possible to design the usage of RLN in Status 1:1 chats.
Due by June 30, 2025•12/12 issues closedhttps://roadmap.logos.co/waku/milestones/open/2024-scale-number-of-communities Proceed with next steps to scale up the number of communities with a focus on testing and configure rendezvous which would enable a large number of communities on their own shard, with the caveat of a more federated global topology. The rendezvous nodes of a community would be a centralised infra to a community. Also proceed with enhancing of the current decentralised discovery protocol to pave the way towards less centralised topology.
Due by September 30, 2025•2/2 issues closedhttps://roadmap.logos.co/waku/milestones/open/2024-static-sharding-dedicated-shards With this milestone, scaling up to 100 communities on separate gossipsub networks (shards) is possible.
No due date•6/6 issues closedhttps://roadmap.logos.co/waku/milestones/open/2024-direct-msg-reliability With this milestone, connectivity issues in Status Mobile and Desktop are solved and tested. Usage of store v3-beta casts a wide net on potential message loss, at the cost of bandwidth overhead (but still lower than current usage of storev2). Review of MVDS usage for all direct messages is done to ensure that critical messages (request to join, contact request, 1:1 messages, private group) are delivered.
Due by March 31, 2025•11/11 issues closedhttps://roadmap.logos.co/waku/milestones/open/2024-bandwidth-optimization-and-protocol-review With this milestone, the store protocol becomes more easily usable for reliability purposes. Moreover, nwaku PostgreSQL implementation will enable better disk space management and enable operators to hard cap the used disk space.
Due by April 11, 2025•4/4 issues closedhttps://github.com/waku-org/pm/issues/125
Due by March 31, 2024•3/3 issues closedhttps://github.com/waku-org/pm/issues/119
Due by March 31, 2024•1/1 issues closedhttps://github.com/waku-org/pm/issues/12
No due date•4/4 issues closedhttps://github.com/waku-org/pm/issues/83
Due by November 30, 2023•3/3 issues closedhttps://github.com/waku-org/pm/issues/73
Due by March 31, 2024•3/3 issues closedhttps://github.com/waku-org/pm/issues/50
Due by December 1, 2023•14/14 issues closed