Skip to content

Conversation

@OlegGirko
Copy link

This is backport of Bitcoin PR bitcoin#8594.

The original PR description follows.

We should learn about new peers via address messages.

An inbound peer connecting to us tells us nothing about
its ability to accept incoming connections from us, so
we shouldn't assume that we can connect to it based on
this.

The vast majority of nodes on the network do not accept
incoming connections, adding them will only slow down
the process of making a successful connection in the
future.

Nodes which have configured themselves to not announce would prefer we
not violate their privacy by announcing them in GETADDR responses.

We should learn about new peers via address messages.

An inbound peer connecting to us tells us nothing about
 its ability to accept incoming connections from us, so
 we shouldn't assume that we can connect to it based on
 this.

The vast majority of nodes on the network do not accept
 incoming connections, adding them will only slow down
 the process of making a successful connection in the
 future.

Nodes which have configured themselves to not announce would prefer we
 not violate their privacy by announcing them in GETADDR responses.
@UdjinM6 UdjinM6 added this to the 12.2 milestone Aug 29, 2017
Copy link

@UdjinM6 UdjinM6 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

utACK

@UdjinM6 UdjinM6 merged commit 76181f5 into dashpay:v0.12.2.x Aug 31, 2017
@OlegGirko OlegGirko deleted the bc-pr-8594 branch August 31, 2017 16:10
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants