Milestone - Store Service Upgrade
-
Store v3-beta - Message Hashes
- achieved:
- [research] Refined testing tools and query criteria for benchmark tests
- next:
- [research] run some more queries and discuss findings
- achieved:
-
Store v3 - store synchronisation
- achieved:
- [research]: remove archive queries 100 hashes limit to allow bigger sync
- next:
- [research]: continue to monitor deployment in fleet, spec update
- achieved:
-
- achieved:
- [nwaku] Enhance libpq response management and new libp2p store metric chore: enhance libpq management
- [nwaku] started the implementation of new metrics to measure queries’ times chore: create grafana panel to show max, min, mean, median stats of query times
- [nwaku] investigate issue chore: store queries for content topics take longer with cursor
- [research] completed main benchmark test scenarios
- next:
- [research] write up of benchmark test findings
- achieved:
Milestone - Direct Message Reliability
-
Review connection management strategy and back-off and fix long disconnection issues
- achieved:
- [chat] bug: requesting always 24h from store node: fix_: store query lastrequest
- achieved:
-
Tooling: filter and light push protocols
- achieved:
- [chat] go-waku: reduce filter loop to 300ms fix_: reduce filter loop to 300ms
- achieved:
-
Reliability Protocol for Relay
- achieved:
- [chat] fix empty subscription when publish message with relay, fix: check subscription when relay publish message, feat: join community request with mvds
- achieved:
-
Reliability Protocol for Resource-Restricted Clients
- achieved:
- [js-waku] fix missing messages from Filter and align with RFC fix: filter missing messages
- [js-waku] improve bootstrapping of the node fix: improve node bootstrapping
- achieved:
-
Review MVDS usage and fail path
- achieved:
- [chat] dogfooding community join request with mvds feat: join community request with mvds
- [chat] accept community join request with mvds feat_: accept community join request with mvds
- achieved:
Milestone - End-to-end reliability protocol
-
End-to-end reliability protocol - PoC
- achieved:
- [research] POC - added better logging and other suggestions from dogfooding
- achieved:
-
End-to-end reliability protocol - Status integration
- achieved:
- [research]: started a post on sdk/library idea for status integration
- next:
- [research]: continue working on post, gather feedback and iterate
- achieved:
Milestone - Scale 1:1 chat messages PoC
-
Maturing RLN variables/parameters revision
- achieved:
- [research]: discussed RLN contract implementation, suggested spec improvements Refinements of RLN on mainnet spec
- achieved:
-
Provision RLN for light push clients PoC
- achieved:
- [research]: drafted a forum post on service incentivization
- next:
- [research]: finalize and discuss the forum post
- achieved:
Milestone - Scale up number of Communities
- Usage of Rendezvous
- achieved:
- [research]: modified nim-libp2p to allow waku rdv strategy, updated nwaku PR to reflect libp2p changes
- next:
- [research]: PR feedback and update cycle, spec update
- achieved:
Other Work
Enhancements
- achieved:
- [nwaku] Reproduction of gossip-level message duplication in stressed conditions.
- Succeed in reproducing and collecting logs from a controlled simulation env.
- Analysed logs to verify possible hypotheses.
- Re-run tests with different setup and configuration.
- [nwaku] NWaku in Windows - Successfully built the nim compiler in isolation with an automated system detail fetching process.
- [chat] go-waku: bump go-libp2p and go-libp2p-pubsub chore: bump go-libp2p and go-libp2p-pubsub
- [js-waku] chore: release master, chore: release master
- [js-waku] remove extra dependencies from sdk package chore: remove relay from sdk package
- [nwaku] Reproduction of gossip-level message duplication in stressed conditions.
- next:
- [js-waku] work on improvements for release processes chore: up release-please
Bugs
- achieved:
- [chat] status-go: retry dnsdisc on failure
- [chat] go-waku: stop creating goroutines if context is already canceled fix: stop creating goroutines if context is already canceled
- [js-waku] fix installation and remove broken dependencies fix: temporarily remove peer cross dependencies
BD: Demonstrate Product-Market Fit
- achieved:
- Defined customer interview questions
- Had first rehearsal with a prospect where some of the questions were asked
- Invited first 3 projects to interview
- next:
- Enroll more projects into the Interviews+Codesign initiative
- Rework validation tracking board
BD: Acquire first 10 Customers
- achieved:
- New project using Waku in the payments vertical, referred by a prospect
- next:
- another prospect call this week
- Prospecting in Singapore