Explore MVDS

[D4nte]

Problem

Data delivery is not guaranteed over the Waku Relay network.

In the past, issues with the network has led to developers implementing naive mechanism such as resending a message until the other party ack

We need to provide an efficient data sync mechanism for developers to improve the success of message delivery

DoD

• Build/try to a PoC implementing MVDS
• Define plan to implement MVDS in js-waku

[fryorcraken]

From @kaiserd

This is based on the Briar protocol: https://code.briarproject.org/briar/briar-spec/blob/master/protocols/BSP.md#11-system-model

This spec is form Whisper/Waku1 times; parts of this would be redundant with gossipsub IHAVE / IWANT.
A reliable message transport can be an interesting protocol in the future, but we need to be careful with adding too much load (i.e. hinder scaling).
It does not make sense to implement the current version, imo. We would have to work on a -V2 RFC.
Something like this might be interesting for store sync in the future.

(This protocol was added before I joined, and it has never been discussed.
And afaik, the only code that exists is in the research repo: https://github.com/vacp2p/research/tree/master/archive/data_sync )

Let's close this. If needs comes then we would need to design a new protocol first.