- [nwaku] PostgreSQL query optimizations [chore: query performance in PostgreSQL by avoiding ordering in queries](https://github.com/waku-org/nwaku/issues/2902)
- [nwaku] PostgreSQL enhance retention policy: [bug: retention policy does not work when postgres db is over loaded](https://github.com/waku-org/nwaku/issues/2890)
## [Milestone - Direct Message Reliability](https://github.com/waku-org/pm/milestone/29)
- [Review connection management strategy and back-off and fix long disconnection issues](https://github.com/waku-org/pm/issues/177)
- achieved:
- [chat] [feat: flag to enable/disable missing message verification](https://github.com/status-im/status-go/pull/5497)
- [Tooling: filter and light push protocols](https://github.com/waku-org/pm/issues/178)
- achieved:
- [chat] added support for 2 lightpush peers to be used for better reliability [feat: support for lightpush to use more than 1 peer](https://github.com/waku-org/go-waku/pull/1158)
- [chat] fix metadata protocol from disconnecting light-clients and only use clusterID and accept connections from lightclients [fix: for light node do not check for matching shards but only clusterID](https://github.com/waku-org/go-waku/pull/1154)
- next:
- [nwaku] Little enhancement for network connectivity, use bootstrap enr's to connect to any kind of network and detect shardings
- [nwaku] Auto select service peers and use them randomly for testing on both sides.
- [nwaku] run lite-protocol-tester on shards.staging
- [Reliability Protocol for Relay](https://github.com/waku-org/pm/issues/184)
- achieved:
- [nwaku] started local sqlite registry implementation [feat: enhance reliability thanks to StoreV3](https://github.com/waku-org/nwaku/issues/2819)
- [chat] config to enable/disable storev3 confirmations for sent messages [feat: flag to enable/disable sent message store query confirmations](https://github.com/status-im/status-go/pull/5493)
- [nwaku] carry on with implementation [feat: enhance reliability thanks to StoreV3](https://github.com/waku-org/nwaku/issues/2819)
- [Reliability Protocol for Resource-Restricted Clients](https://github.com/waku-org/pm/issues/186)
- achieved:
- [js-waku] improved renewal of peers for Filter [feat(filter): peer/subscription renewal with recurring Filter pings](https://github.com/waku-org/js-waku/pull/2052)
- [js-waku] check for missing messages from Filter subscriptions [feat: validate messages for individual filter nodes & perform renewals](https://github.com/waku-org/js-waku/pull/2057)
- [Sharding peer management and discovery hardening](https://github.com/waku-org/pm/issues/172)
- achieved:
- [research] review of discv5 both spec and nim implementation
- [research] compiled audit of discovery status quo and potential future strategies
- [nwaku] Creating versions for DST team to test discv5 and message reliability
- [nwaku] Proposing new solution to log received message info from nim-libp2p. Created custom version for DST team to use [chore: creating branch to test Waku's received messages](https://github.com/vacp2p/nim-libp2p/pull/1128)
- [nwaku] Started investigating and implementing improvements for connection management of bootstrap only nodes [bug: Node accepts connections when configured for just discovery](https://github.com/waku-org/nwaku/issues/2892)
- [nwaku] Improved logging [chore: improving logging under debugDiscv5 flag](https://github.com/waku-org/nwaku/pull/2899), [chore: logging content topic of spam messages](https://github.com/waku-org/nwaku/pull/2906)
- [nwaku] Investigated at depth discv5’s implementation [bug: discv5 not returning enough peers](https://github.com/waku-org/nwaku/issues/2810)
- next:
- [research] review other discovery methods and state of implementation in nim
- [research] review metrics collected and add more if needed