Franck R.

Still happening, need to discuss with chainsafe and understand if they have same issues. I believe it to be a symptom of https://github.com/libp2p/js-libp2p/issues/939

> > Note, however, that ping protocol is currently only available on `test` fleet nodes. > > Just double-checking that you're still aware of this - `prod` is running the...

> This should be unblocked now with the merging of [status-im/nim-waku#621](https://github.com/status-im/nim-waku/pull/621). Note, however, that ping protocol is currently only available on `test` fleet nodes. Confirmed on test fleet, it does...

It fails exactly 10min in. I am guessing it is a TCP timeout, I also have seen scenarios where nginx was used as a reverse proxy and it would fail...

SafeChain does not seem to encounter the issue due to a lack of idling: https://discord.com/channels/593655374469660673/606584108449005598/867794263945510942 > hmmm I don't think we've ever seen this bc our network is constantly sending...

Resolved with a relay keep alive: #243. Keeping open to watch out for upstream solution libp2p/js-libp2p#744 .

Should be fixed once #802 is done

Best to wait for nim-waku implementation first.

With protobufjs it's possible to build without bufbuild https://github.com/filoozom/tfe-uliege-code/tree/main/platform%2Fnode

Maintenance has been resumed :tada: https://github.com/ipfs/protons/commit/74d3b7abf1e857f7320c100734e797855ea728c1 Focusing this issue in the tree-shakeable problem.