Danish Arora

> something that is tangentially related to this issue, please ensure that the rln_tree is persisted across runs so the nwaku nodes finish sync and startup quicker Good point!

Based on https://github.com/waku-org/js-waku/pull/1245, it can be deduced that `protobuf-es` while reducing the total lines of code by 50%, still increases the package size by about 13% which makes `protons` better...

> > Based on #1245, it can be deduced that `protobuf-es` while reducing the total lines of code by 50%, still increases the package size by about 13% which makes...

As a followup to the above thread: One idea that came up in a discussion with @felicio was if we could have the Logos scaling simulation tests run js-waku with...

> Yes this is a fair idea. But not for 2023 https://notes.status.im/Uz9HeCwZTDSYyOq36Q54cA?edit > > I'd suggest to open a different issue and park it. Sounds good :) Future work being...

> Initial implementation done: #762 but only works in NodeJS with a listening node. > > Blocked by: > > * [Filter does not push messages to js-waku in the...

> Some progress on react-native compatibility for js-libp2p - [libp2p/js-libp2p#2136 (comment)](https://github.com/libp2p/js-libp2p/issues/2136#issuecomment-1849999462) super cool! --- imo we should prioritize the react-native SDK effort with js-waku cc @waku-org/js-waku-developers @hackyguru @chair28980

As a part of this epic, we should also track work around looking into implementing other more reliable NAT traversal techniques by libp2p like: - autonat (https://github.com/libp2p/specs/tree/master/autonat) - circuit-relay v2...

issue description is empty. moving this back to triage

@weboko are we set on the proposed solution? do we want to triage it before we tackle it?