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
Report NewExternalAddrCandidate per instance, e.g. one instance of identify behaviour should only report external address candidate only once unless expired.
Motivation
NewExternalAddrCandidate event will not flood the event handling system during DHT walk-through.
Current Implementation
Currently NewExternalAddrCandidate is reported per connection, e.g. the same connection won't report already reported addresses but new connection will. So when bootstraping a DHT network NewExternalAddrCandidate will flood in.
Are you planning to do it yourself in a pull request ?
Yes
The text was updated successfully, but these errors were encountered:
Description
Report
NewExternalAddrCandidate
per instance, e.g. one instance ofidentify
behaviour should only report external address candidate only once unless expired.Motivation
NewExternalAddrCandidate
event will not flood the event handling system during DHT walk-through.Current Implementation
Currently
NewExternalAddrCandidate
is reported per connection, e.g. the same connection won't report already reported addresses but new connection will. So when bootstraping a DHT networkNewExternalAddrCandidate
will flood in.Are you planning to do it yourself in a pull request ?
Yes
The text was updated successfully, but these errors were encountered: