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
During RLN testing with different network sizes and RLN config, it was noticed that sometimes when there are many consecutive RLN membership registrations occurring and many messages published by other already registered nodes, then some messages in the network are identified as spam.
This happens while the messaging rate is well within the RLN limits and should not lead to any spam messages being identified by the nodes.
Impact
These messages are not spam and should be relayed. This erroneous identification of spam messages could lead to nodes disconnecting from a peer because it seems like it is spamming
I'm not sure if it's a variant or a different bug occurring in the same scenarios.
With the specific config mentioned here where only 1 full node is present, I don't see invalid messages at all, only the spam.
I have seen the spam and invalid messages happen with the same config mentioned in #2870, but not at the exact same time.
Problem
During RLN testing with different network sizes and RLN config, it was noticed that sometimes when there are many consecutive RLN membership registrations occurring and many messages published by other already registered nodes, then some messages in the network are identified as spam.
This happens while the messaging rate is well within the RLN limits and should not lead to any spam messages being identified by the nodes.
Impact
These messages are not spam and should be relayed. This erroneous identification of spam messages could lead to nodes disconnecting from a peer because it seems like it is spamming
To reproduce
Using the waku-simulator https://github.com/waku-org/waku-simulator:
Expected behavior
These messages should be valid.
Screenshots/logs
nwaku node logging:
Membership registration logging:
nwaku version/commit hash
v0.30.0
The text was updated successfully, but these errors were encountered: