Waku v1: Optimize bandwidth usage about rfc HOT 7 CLOSED

@oskarth You mean this: status-im/nim-eth#114 . I can resolve the conflicts with the current version. Itcould be merged then yes, any possible differences in future spec can be adjusted.

from rfc.

Update: I didn't get to this last week. Also need to think about how to describe a clear diff in the spec.

@kdeme I don't think it'll change materially from previous PoC. Do you think the nim-eth PoC from before can be brought over and merged? While spec is worked on in parallel

from rfc.

I wonder if we should adjust the current bloom filter API, or have another call (probably cleaner) with explicit topic interest.

This might be a good opportunity to use/fixup usage of MVDS/remote log @decanus and take any lessons learned around current mailserver work (closest node, sticky availability, cursor db stuff etc)

from rfc.

E.g. see post by @cammellos https://discuss.status.im/t/performance-of-mailservers/1215 re index patterns etc

from rfc.

@decanus Any progress over the last several days on this? Anything

from rfc.

Mailserver issue factored out #80

from rfc.

Simulation issue factored out vacp2p/simulations#1

Mailserver issue should get merged today

Closing

from rfc.