roadmap/content/waku/monthly-reports/2023-aug.md

81 lines
3.0 KiB
Markdown

# Waku Monthly Report - August 2023
## Epics and Milestones
1. **Waku Network Can Support 10K Users**
- PostgreSQL integration for improved performance
- Setting up a staging fleet for Status to try static sharding
- Stress testing and performance comparisons between SQLite and PostgreSQL
2. **Light Protocols and Status MVP**
- Light push and filter protocols available in Status Mobile and Desktop
- Peer Exchange supported and used by default in js-waku
- Some light dogfooding has started
3. **1 Million Users / Public Waku Network**
- Completed Autosharding v1 for nwaku
- Task breakdown and assignment for the epic
- Started work on Waku Network RFC
4. **Quality Assurance and Maintenance**
- Improved release processes for nwaku
- Enhanced test coverage for go-waku
- Maintenance work on js-waku, including dependency upgrades
5. **RLN (Rate Limiting Nullifier) Improvements**
- Post-Testnet3 improvements in go-waku
- RLN enabled by default in go-waku
6. **Peer Management**
- Introduced peer management in go-waku
- Implemented sharded peer management and discovery in nwaku
## Client Updates
### nwaku
- Completed Autosharding v1 implementation
- Progress on PostgreSQL integration and stress testing
- Improvements in HTTP REST API support
- Enhancements in C-bindings and thread safety
- Setting up static sharding fleet for Status
### js-waku
- Peer Exchange supported and used by default
- Maintenance work, including dependency upgrades
- Improvements in developer experience
- Progress on covering multiple environments in testing
### go-waku
- RLN enabled by default and running on all configured topics
- Implemented core logic for Autosharding v1
- Introduced and improved peer management
- Enhanced test coverage
- Maintenance work, including metrics refactoring
## Research and Documentation
- Breakdown and assignment of tasks for the 1 million users/public Waku Network epic
- Started work on Waku Network RFC
- Advanced documentation for js-waku, including debugging guides and NodeJS support
## Ecosystem Development
- Increased Twitter followers by 20%
- Participated in web3conf with talks, side events, and swag distribution
- Initiated migration of eco-dev elements from GitHub to Notion
- Planning for upcoming events like ETHRome hackathon
## Challenges and Next Steps
1. Continue refining and implementing the 1 million users/public Waku Network plan
2. Further stress testing and optimization of PostgreSQL integration
3. Dogfooding new peer management with Status
4. Expanding test coverage across all clients
5. Finalizing and deploying the static sharding fleet for Status
6. Advancing the Waku Network RFC
7. Continuing ecosystem growth through events and community engagement
The Waku team has made significant progress across multiple fronts in August, with notable advancements in scalability, light protocols, and quality assurance. The focus on supporting 10K users and laying groundwork for 1 million users demonstrates the project's commitment to growth and adoption.