Investigate message seen cache handled by gowaku's libp2p #126
Labels
meta:triaged
This issue has been triaged (has a good description, as well as labels for priority, size and type)
p3
Low priority
size:small
Small
type:refactor
Changes not visible to users
Describe the bug
If a radio is connected to multiple peers and the peers are gossiping some of the same messages, the radio experiences multiple instances of those messages. Currently we handle duplicated messages by filtering based on the message id upon receiving Waku signal, but Waku node should have done this already, as explained by the team that
In libp2p there's a message seen cache that should avoid duplication for up to 2 minutes (the default value for seen_ttl
The team will expose this config, we can investigate further and hopefully remove the radio's filtering step.
Expected behavior
Waku config allows the radio to toggle message seen cache to prevent duplicated messages, and radio be alleviated from tracking seen messages.
Screenshots
The text was updated successfully, but these errors were encountered: