Direct Message Reliability
- Reliability Protocol for Resource-Restricted Clients
- next:
- [nwaku] Enhance lightpush protocol error handling
- [nwaku] Enhance error propagation in libp2p
- Optimizing observers for better performance
- Proper error reporting from publish
- next:
End-to-end reliability protocol
- End-to-end reliability protocol - Status integration
- achieved: [research] addressed review comments on reliability utils PR, new PR for reliability manager, started exploring API integration with status-go
- next: [research] merge ongoing PRs
RLN Mainnet
-
Provision RLN for light push clients PoC
- achieved: [research] merged a double-spend protection PR in the incentivization POC
- next: [research] plan and implement local client-side reputation in the POC
-
Implement RLN smart contract for paid, multilevel memberships
- achieved: [research] Tested local deployment of new RLN contract and identified where in the nwaku code the contract address and implementation is used
- next: [research] verify nwaku updates and push
-
RLNv2 Web management interface
- next: [js-waku] migrate to RLNv2 contract
Milestone: Nwaku in Status Desktop (Relay mode)
- Nwaku in Golang: Desktop
- achieved:
- [nwaku] Choose ports automatically
- [nwaku] Fix in GetNumConnectedRelayPeers
- [nwaku] Test parallel requests
- [nwaku] Turn off omitempty for Relay
- [nwaku] Avoid send relay callbacks if relay disabled
- [nwaku] Found root cause and fixed crash in nwaku’s integration in Status Desktop (fixed in https://github.com/status-im/status-go/pull/6283)
- next:
- [nwaku] Continue with integration of nwaku in Status Desktop
- [nwaku] Finish new strategy to manage concurrency in libwaku
- achieved:
Hardening and scaling foundations for private chats
- Specify private chat protocol
- achieved:
Upgrade Waku for the Web
- Scalable Data Sync in browser
- achieved: [js-waku] implement double-hashing strategy for BloomFilter hash functions
- next: [research] review js-waku SDS PRs
Logos Web Apps
- Reliable Qaku & library
- achieved:
- [chat] Qaku FURPS
- [chat] Minor Qaku fixes 1 2 3
- achieved:
Explore Peer Discovery Gap
-
- achieved: [research] limited shard support for waku sync
- next: [research] full shard support & request time range trimming
-
- achieved: [research] understanding of libp2p layers and come up with an approach to implement mix as a protocol and also to decouple mix exit node from destination peer
- next: [research] try to integrate mix with nwaku
Messaging API
- Messaging API: js-waku
- achieved:
- [js-waku] speed up core operations by avoiding PeerStore
- [js-waku] fix health state management and make it lighter
- [js-waku] make health state API event driven
- achieved:
Maintenance H1 2025
- achieved:
- [nwaku] nwaku<>gowaku interop filter issue
- [nwaku] Fix too large metrics values
- [chat] Test new js-waku versions
- [js-waku] use allure reporting for sds package
- next:
- [nwaku] v0.35.0 release
- [nwaku] nwaku<>js-waku interoperability test stabilization
- [nwaku] Deprecate tree sync strategy
- [js-waku] js-waku interoperability investigations