<li><em>next</em>: LightPush REST endpoint will be implemented fully and put on PR review</li>
<li><em>blocking</em>:</li>
</ul>
<p><strong><ahref="https://github.com/waku-org/nwaku/issues/2027"class="external">bug: wrong user_version in sqlite database that blocks the run of a Waku node</a></strong> {bug}</p>
<ul>
<li><em>achieved</em>: bug fix that prevented a <em>Store</em><code>nwaku</code> to start if the <em>SQLite</em> db was created with versions [0.14.0 - 0.18.0]</li>
<li><em>next</em>: -</li>
</ul>
<p><strong><ahref="https://github.com/waku-org/nwaku/issues/1936"class="external">feat: Autosharding API for (relay) subscriptions</a></strong> {E:1.2: Autosharding for autoscaling}</p>
<ul>
<li><em>achieved</em>: many PR fixes,</li>
<li><em>blocker</em>: explicit subscriptions in js-waku tests</li>
</ul>
<p><strong><ahref="https://github.com/waku-org/nwaku/issues/1883"class="external">chore: do not advertise MAs with port 0</a></strong> {bug}</p>
<ul>
<li><em>achieved</em>: tested two different solutions: updating the port with an addressMapper, and not allowing the user to use port 0. Analyzed and discussed technical implications of both solutions. Initially followed decision to proceed with 2nd solution for now, with intention of implementing the first solution in the future.
Opened a draft PR and updated tests for the solution of not allowing the user to choose port 0.</li>
<li><em>next</em>: after further feedback received today, we have to complete the discussion of how to move forward and either review and proceed with current PR, or plan and implement solution that updates all the data structures consistently across the node</li>
</ul>
<p><strong><ahref="https://github.com/waku-org/nwaku/issues/1872"class="external">feat: HTTP REST API: Filter support v2</a></strong> {E:REST API service node}</p>
<ul>
<li><em>achieved</em>: Filter v1 & v2 REST API endpoints merged to master</li>
<li><em>next</em>: LightPush REST endpoint</li>
<li><em>blocking</em>:</li>
</ul>
<p><strong><ahref="https://github.com/waku-org/nwaku/issues/1576"class="external">chore: update resolved enr ip when using <code>dns4-domain-name</code> flag</a></strong> {enhancement}</p>
<ul>
<li><em>achieved</em>: implemented solution that does DNS IP resolution during node bringup when no external IP is found but a DNS address is provided.
Validated and tested “happy paths” of the solution, raised draft PR and got feedback about the solution
-<em>next</em>: discuss and define the system’s behavior on errors, implement error handling and adding tests for this feature.</li>
<p><strong><ahref="https://github.com/waku-org/js-waku/issues/52"class="external">Cover Several Environments As Part of Testing</a></strong> {test}, {E:2023-qa}</p>
<ul>
<li><em>achieved</em>: got reviews on playwrights tests</li>
<p><strong><ahref="https://github.com/waku-org/go-waku/issues/727"class="external">feat: discovery & peer management for static shards</a></strong> {E:1.4: Sharded peer management and discovery}</p>
<ul>
<li><em>achieved</em>: Update WakuPeerStore to store pubSubTopics for a peer.</li>
<li><em>next</em>: Sharded Peer Management considering static sharding for Status communities.</li>
</ul>
<p><strong><ahref="https://github.com/waku-org/go-waku/issues/655"class="external">RLN enabled by default</a></strong> {E:3.2: Basic DoS protection in production}</p>
<ul>
<li><em>achieved</em>: isReady verif in /health endpoint, make RLN available in service nodes and library usage by default, update docs and docker image, use zerokit 0.3.4, allow running service node with no RLN credentials</li>
<li><em>next</em>: bandwidth validation, subcommand to list credentials</li>
<li><em>achieved</em>: CommonService for embedding lifecycle operation in lightpush,discv5,filter,peerConnector etc.</li>
<li><em>next</em>: after discussion with richard prem, use create 2 different types of commonService. Change nameServer flag functionality in go-waku to nwaku. And work on newly created tasks.</li>
</ul>
<p><strong><ahref="https://github.com/waku-org/go-waku/issues/620"class="external">Improve Test Coverage</a></strong> {test}</p>
<ul>
<li><em>achieved</em>: replace golint by revive, and add <code>make lint-full</code> target to run linting with many more rules enabled</li>
