You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
GossipSub doesn't natively define a mechanism for ensuring the correct message delivery. With that, we need to have an additional layer to increase the likelihood that any message has been sent to the desired destination.
Suggested solution
Have an interaction with a store node where we check whether a bunch of recently sent messages had reached at least, the offending store node.
As a reference, we have the following implementation and we need to do the same but in nwaku: status-im/status-go#5217 . With that, status-go should be able to use nwaku.
At first, we will work on having this feature working in relay but is likely that we will need to extend it to light push as well.
Additional context
The following can help to have a better context of what is needed from Status PoV: status-im/status-go#5234
Acceptance criteria
Have a reliability mechanism, in relay, that deals with StoreV3 and is analog to: status-im/status-go#5217
Problem
GossipSub doesn't natively define a mechanism for ensuring the correct message delivery. With that, we need to have an additional layer to increase the likelihood that any message has been sent to the desired destination.
Suggested solution
Have an interaction with a store node where we check whether a bunch of recently sent messages had reached at least, the offending store node.
As a reference, we have the following implementation and we need to do the same but in
nwaku
: status-im/status-go#5217 . With that,status-go
should be able to usenwaku
.At first, we will work on having this feature working in relay but is likely that we will need to extend it to light push as well.
Additional context
The following can help to have a better context of what is needed from Status PoV: status-im/status-go#5234
Acceptance criteria
Have a reliability mechanism, in relay, that deals with StoreV3 and is analog to: status-im/status-go#5217
Epic
Reliability Protocol for Relay - #3082
The text was updated successfully, but these errors were encountered: