---
# System prepended metadata

title: November 15-19 Waku2 strategy

---

November 15-19 Waku2 strategy
===

#### ~~Upgrade go-waku in status-go to remove the noisy ping error when the node attempts to ping itself~~
Assigned to: Anthony
status-go: Done
status-lib: Done
status-desktop: Done

#### ~~Find out the state of mobile.~~
Assigned to: Anthony

Similar to desktop, it happens with very low frequencies, and it is quite hard to replicate. Also they use waku V1.
Conclusion: it seems to me that the error on mobile/desktop are the same, we should try to focus our research into status-go

#### Test script
Assigned to: Anthony

- ~~Discuss with @cammellos the state of the test script that continuously writes messages to a channel.~~ 
- Setup the script

=> Script will be setup today/tomorrow


#### Missing messages
Assigned to: Anthony, Richard

- ~~Find out if missing messages happen in WakuV1~~
    - The problem might be happening in the client / status-go instead of happening in waku
    - **Confirmed: the problem also happened on waku V1**
- If the error is not happening in the client or in status-go, Find out how to trace the message in nim-waku/go-waku. Also use waku metrics

#### Dogfooding
Assigned to: Everyone :)

- Try to dogfood more than 1hr daily. 
    - Nov18
        - If there is an error while sending a message related to a peer not being temporarily available, the sendChatMessage RPC method would fail immediatly.A PR was created to status-go reattempts to send the message before finally marking it as unset.
        - Some edge cases were found: 
            - What happens if there are not enough relay peers for sending a message and no lightpush nodes available? Asked @oskarth in the group about it
            - What happens if a node that has been added to the peerstore indicating that it supports a protocol, later stops supporting it? Asked @hanno about it
- ~~Convince the team to use desktop with waku2 instead of discord on Monday or Tuesday~~
- Test light client functionality in desktop. 
    - ~~rramos: Filter might not be working. I wasn't able to see any log indicating that it's being used instead of relay. Consider adding logs if they don't exist~~
        - Nov16: Filter functionality was not being enabled on desktop. PR with a fix was created.
- Test rendezvous with desktop and mobile
    - We need to create a branch that uses a single rendezvous server, and confirm that the number of peers increase once more users connect (since they'll be discovered with rendezvous)
    - Mobile might not have Rendezvous configuration set. Confirm with @vitaliy

#### DiscoveryV5
Assigned to: Richard

- Implement DiscoveryV5 according to the spec
    - Nov15: Implemented. Currently working in adding flags to wakunode
    - Nov17: Adding flags to wakunode is implemented
- Test if nim-waku / go-waku nodes from the fleet are discovered
- Upgrade status-go to use DiscoveryV5
    - Nov17: Currently working on this
    - Add API methods to start / stop discovery
    - Add required configuration items
    - Determine with Vac team if DNS Discovery is going to be used for finding nodes to bootstrap DiscV5

#### DNS Discovery - Prod Fleet
Assigned to: Hanno, Richard

- Once an URL for DNS discovery is available, Add the URL in the nodeconfig for Desktop
    - Nov15: Hanno told me that this is going to be done this week, since Jakub is back from vacations
    - Nov18: Discussion about prod fleet config here: https://github.com/status-im/infra-nim-waku/issues/29
- Confirm that switching between test and production fleet works.
- If peer persistence is enabled in status-go (?), confirm if switching the fleet will still cause the client to connect to the previous fleet nodes
