2024-09-30 Waku Weekly

Milestone - Store Service Upgrade §

• Store v3-beta - Message Hashes

  • achieved:
    • [chat] go-waku: ratelimit store queries and add options to Next to allow customization of cursor queries feat: ratelimit store queries and add options to Next
    • [chat] go-waku: storenode cycle feat: storenode cycle
    • [chat] status-go: extract storenode cycle to go-waku api feat_: extract storenode cycle to go-waku api
    • [chat] storenode cycle add tests on go-waku

• Store v3 - store synchronisation

  • achieved:
    • [research] finish Waku sync 2.0 research issue
    • [research] Test plan still WIP
    • [nwaku] fix: static linking negentropy in ARM based mac
    • [nwaku] chore: Switch libnegentropy library build from shared to static linkage
  • next:
    • [research] updates from feedback
    • [research] Complete test plan and start with basic tests

• DOS protection for req-res protocols and metrics

  • achieved:
    • [nwaku] chore: rate limit peer exchange protocol, enhanced response status in RPC
    • [nwaku] chore: DOS protection of non-relay req/resp protocols new cli argument description
    • [nwaku] chore: Adjusted peer-exchange to the latest changes made due to rate limit DOS protection
    • [nwaku] nwaku is feature ready for DOS protection for req-res protocols and metrics

• PostgreSQL Maintenance

  • achieved:
    • [research] Completed more benchmark testing scenarios
    • [nwaku] chore: extending store metrics
  • next:
    • [nwaku] chore: store queries for content topics take longer with cursor
    • [research] Write a quick reference summary of test findings
    • [nwaku] chore: store queries for content topics take longer with cursor

Milestone - Static Sharding - dedicated shards §

• Sharding peer management and discovery hardening
  • achieved:
    • [nwaku] chore: test peer connection management
  • next:
    • [nwaku] added an abstraction for libp2p to make the code easier to manage in the future. refactor: peermanager for stale peers management

Milestone - RLN Mainnet §

• RLNv2 in nwaku

  • achieved:
    • [chat] waku-rlnv2-contract: do not keep track of membership registration order refactor: do not keep track of membership registration order

• Implement RLN smart contract for paid, multilevel memberships

  • achieved:
    • [research] started review of RLN memberships PR
  • next:
    • [research] review / improve the membership PR for RLN on mainnet

• Public dogfooding RLNaaS web app

  • achieved:
    • [nwaku] chore: append current version in agentString which is used by the identify protocol

Milestone - Scale up number of Communities §

• Usage of Rendezvous
  • achieved:
    • [research] nim-libp2p PR update from feedback
  • next:
    • [research] more updates on PR and or merge

Milestone: Nwaku in Status Desktop §

• Nwaku in Status Desktop

  • achieved:
    • [nwaku] disabled metrics in libwaku until proper support is implemented chore: disabling metrics for libwaku
  • next:
    • [nwaku] feat: nwaku in status-go (discv5 and dnsdiscovery)

• Nwaku on Windows

  • next:
    • [nwaku] Windows support was put on hold due to a recurring error. We’ll revisit it after a break.

Milestone: Incentivise running a Waku infrastructure node §

• Service Incentivisation - Pay for RLN provision PoC
  • achieved:
    • [research] updated the Vac forum post on service incentivization

Milestone: Bandwidth optimization and protocol review §

• Status usage of Waku scaling and bandwidth optimization recommendation

  • achieved:
    • [chat] review and document status community flow Status Community Flow

• Review usage of content topics in Status Chat and Communities protocol

  • achieved:
    • [research + chat] forum-post proposal for content-topic usage in status communities Status Communities : Review and proposed usage of Waku content-topics
  • next:
    • [research] POC to showcase proposed usage of content-topic in communities

Bugs and Maintenance §

• achieved:
  • [nwaku] chore: sharding - reduce log level for a too spammy message
  • [nwaku] Release v0.33 preparation and validation
  • [nwaku] chore: updating upload and download artifact actions to v4
  • [nwaku] fix: px protocol decode - do not treat missing response field as error
  • [nwaku] fix: PeerExchange rpc decode in order not to take response’s status_code mandatory - for support old protocol implementation
  • [chat] status-go fix_: remove unreachable code error message
  • [chat] go-waku, fix push notifications not working in mobile in develop branch fix: filter batch duration opt was not propagated correctly

Milestone: Demonstrate product-market fit §

• Define potential USPs

  • achieved:
    • Franck redone validation matrix and we defined how to approach prospects to validate our USPs
  • next:
    • actively seek validation or invalidation of these USPs in next contacts with customers in a structured manner

• Define target customers

  • achieved:
    • we have gained knowledge since last GTM plan iteration to further specify our target customers and segments
  • next:
    • Iterating on GTM plan with new info
  • blockers:
    • doing some interviews and validating USPs

• Customer Interviews

  • achieved:
    • Defined questions and validation Matrix and lined up first couple of leads
  • blockers:
    • some of the contacts went to Bali and other places after token2049 and it’s hard to get a hold of them

• Co-design sessions

  • achieved:
    • A couple projects interested in participating
  • next:
    • defining scope of co design with potential partners
  • blockers:
    • need more details and conducting some interviews before extending formal invitations

Milestone: Acquire first 10 customers §

• 5-10 Highly qualified leads

  • achieved:
    • 4 deals in Solution Engineering stage with others joining soon
  • next:
    • advancing
  • blockers:
    • mostly on customer side apart from some fixes needed in some of our products like js-waku

• Review current integrations

  • achieved:
    • rounded up deals and logged dependencies in CRM and agreed on roadmap priorities according to existing customers
  • next:
    • looking into deals that were lost and figuring out how to revive with new milestones being hit