Milestone - Store Service Upgrade
-
Store v3 - store synchronisation
- achieved:
- [research] Waku sync 2.0 research post first draft.
- [nwaku] bug: libnegentropy.so is missing during link or false linked static linkage for libnegentropy - helps easier deployment chore: Switch libnegentropy library build from shared to static linkage
- next:
- [research] Write a basic test plan for store sync
- [research] finalize Waku sync 2.0 research post
- achieved:
-
- achieved:
- [research] Investigated some store query duration test cases
- [nwaku] Submitted PR - chore: extending store metrics
- next:
- [research] Run a few more tests and summarise the test results
- achieved:
Milestone - End-to-end reliability protocol
-
End-to-end reliability protocol - PoC
- achieved:
- [research] dogfooding session for POC
- achieved:
-
End-to-end reliability protocol - Status integration
- achieved:
- [research] published API spec proposal for status-go integration to Vac forum: Vac API Specification for End-to-end Reliability
- next:
- [research] discussion and iterate on API spec; detailed review of points of integration
- achieved:
Milestone - Static Sharding - dedicated shards
-
Sharding peer management and discovery hardening
- achieved:
- [nwaku] made the connectivity loop interval dynamic depending on the current number of peers and targets
- [nwaku] investigated impact nodes advertised with localhost addresses chore: don’t propagate peers with 127.0.0.1 multiaddresses via Discv5
- [nwaku] implemented feedback and merged pubsub topic deprecation chore: deprecating pubsub topic
- achieved:
-
Enable testing of custom shard implementation for Communities
- achieved:
- [chat] add cli test with own shard community feat: add the first community in own shard
- achieved:
Milestone - Scale 1:1 chat messages PoC
-
- achieved:
- [nwaku] RLN Membership Contract - feat: membership
- achieved:
-
Maturing RLN variables/parameters revision
- achieved:
- [research] review RLN on mainnet PR
- achieved:
Milestone - Scale up number of Communities
-
- blockers:
- [research] awaiting nim-libp2p PR review
- blockers:
-
DoS protection for req-res protocols and metrics (go-waku as service node)
- achieved:
- [nwaku] PeerExchange protocol with rate limit check.
- chore: rate limit peer exchange protocol, enhanced response status in RPC
- Updated protocol
- New CLI for configure rate limiting. Allows fine tune rate limits to one needs.
- [nwaku] Deliverable is ready on nwaku.
- [nwaku] PeerExchange protocol with rate limit check.
- achieved:
Milestone: Nwaku in Status Desktop
-
- achieved:
- [nwaku] start working on it more actively feat: nwaku in status-go (discv5 and dnsdiscovery)
- [nwaku] chore: libwaku reduce repetitive code by adding a template handling resp returns
- achieved:
-
- achieved:
- [nwaku] Worked on resolving external library linking issues. feat: windows support
- [nwaku] Started refactoring the peer manager. Improvement: manage stale peer in peer_manager
- next:
- [nwaku] Wrapping up Windows support with automation & then focusing on peer manager refactoring after that.
- achieved:
Milestone: Incentivise running a Waku infrastructure node
-
RLN Relay Incentivisation - Distribute RLN fees PoC
- achieved:
- [research] Got feedback for the initial proposal: RLN Fees distribution to operators with root voting
- next:
- [research] Refine and explore open problems: challenge for lazy node, analyze if assumptios hold valid, consensus problem when no 2/3 are archieved, etc.
- achieved:
-
Service Incentivisation - Pay for RLN provision PoC
- achieved:
- [research] discussed the Vac forum post on service incentivization
- next:
- [research] finalize forum post discussion; amend incentivization spec
- achieved:
Milestone: Bandwidth optimization and protocol review
-
Status usage of Waku scaling and bandwidth optimization recommendation
- achieved:
- [chat] draft the spec about some bandwidth issues feat: bandwidth optimize spec
- achieved:
-
Review usage of content topics in Status Chat and Communities protocol
- achieved:
- [chat] analysis of current content-topic usage in status communities Status Message Types - Content Topics
- achieved:
Milestone: Demonstrate Product-Market Fit
- achieved:
- found new projects interested in interviewing and co-designing (see milestone 2)
- next:
- book interviews and enroll for co-design
Milestone: Acquire first 10 Customers
- achieved:
- attended Singapore Blockchain Week (token2049):
- projects interested in partnering:
- Sports prediction market;
- private social protocol;
- Network state/pop up city;
- Intents protocols;
- Inbound leads have been coming to us on discord, a good sign despite marketing activity wind down;
- projects interested in partnering:
- attended Singapore Blockchain Week (token2049):
Other Work
Maintenance
- achieved:
- [nwaku] added version migration instructions to the docs feat: add migration instructions
Bugs
- achieved:
- [nwaku] investigated failed interop tests and found solutions. Fixed config bug fix: setting up node with modified config