Prem Chaitanya Prathi

> * both success case and failed case shows two times "peer connected” and “peer disconnected” events. This seems to be happening as metadata protocol is disconnecting the peer as...

> > * both success case and failed case shows two times "peer connected” and “peer disconnected” events. > > This seems to be happening as metadata protocol is disconnecting...

As per discussion here https://discord.com/channels/1110799176264056863/1111540684575477821/1145970002948792420 , some of the changes related to this would be part of app-sdk/chat-sdk team. Need to revisit the scope of changes for go-waku.

Closing this issue as it is already being addressed via new filterManager and storev3 based reliability for status.

@richard-ramos , time to merge this PR i guess. CI issues need to be fixed though It would be useful for peer management for status.

This would no longer be required as nwaku would be replacing go-waku in status by end of 2024. Hence closing this as there is no plan to implement it.

@vyzo wondering if this PR ready to be merged or are you waiting for anything to be fixed/addressed? This seems to improve bandwidth usage and we want to take advantage...

> I think in general it looks good, but i do want to do another pass. > > In the meantime: > > * can you bump the version to...