Description
There is a bit of talk about the recent IDONTWANT messages not being as effective as they could be.
People are noticing IDONTWANT messages being sent, but still being sent duplicates after. This indicates that nodes are currently sending queued messages, or are in the process of sending messages.
We can check some of these data points in Lighthouse to confirm. One improvement, could be to remove from the send queue any messages that have the ID of an IDONTWANT message we receive. Perhaps we could also drop the current send item, however, this might be difficult in practice with scoring and how the other end receives a half-sent message.
Motivation
Improve network bandwidth and reduce duplicates
Current Implementation
We have no mechanism of canceling messages once they are queued.
Are you planning to do it yourself in a pull request ?
Maybe
Description
There is a bit of talk about the recent IDONTWANT messages not being as effective as they could be.
People are noticing IDONTWANT messages being sent, but still being sent duplicates after. This indicates that nodes are currently sending queued messages, or are in the process of sending messages.
We can check some of these data points in Lighthouse to confirm. One improvement, could be to remove from the send queue any messages that have the ID of an IDONTWANT message we receive. Perhaps we could also drop the current send item, however, this might be difficult in practice with scoring and how the other end receives a half-sent message.
Motivation
Improve network bandwidth and reduce duplicates
Current Implementation
We have no mechanism of canceling messages once they are queued.
Are you planning to do it yourself in a pull request ?
Maybe