Closed jcnelson closed 2 months ago
Misconfiguration could be the problem. Still needs to be evaluated on a testnet
This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
It appears that there has been a behavioral regression in the node's neighbor walk algorithm. It ought to be the case that if node A contacts node B, then node B should attempt to contact node A, and if successful, add node A to its outbound peer set (making it eligible for data pushed from node B, and eligible for enumeration in response to a
GetNeighbors
p2p message). This isn't happening anymore.