From: Vasil Dimov <vd@freebsd.org>
To: Prayank via bitcoin-dev <bitcoin-dev@lists.linuxfoundation.org>
Subject: Re: [bitcoin-dev] non-default ports for automatic connections in Bitcoin P2P network
Date: Wed, 2 Feb 2022 14:30:47 +0100 [thread overview]
Message-ID: <YfqHhyZ8eL3ZUiBw@smle> (raw)
In-Reply-To: <Mubr4YT--3-2@tutanota.de>
[-- Attachment #1: Type: text/plain, Size: 706 bytes --]
Prayank, thanks for taking the time to inform the wider community.
I just want to clarify to avoid confusion that this is about whether to
open automatic outgoing connections to a peer at addr:port if port is
not 8333. Right now, Bitcoin Core has a very very strong preference
towards peers that listen on port 8333. So, if one listens on !=8333
then he is practically not getting any incoming connections (from
Bitcoin Core).
See the PR for details and justifications:
https://github.com/bitcoin/bitcoin/pull/23542.
--
Vasil Dimov
gro.DSBeerF@dv
%
Diplomacy is the art of telling people to go to hell in such a way that
they ask for directions.
-- Winston Churchill
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 1528 bytes --]
prev parent reply other threads:[~2022-02-02 13:40 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-01-29 22:02 [bitcoin-dev] non-default ports for automatic connections in Bitcoin P2P network Prayank
2022-02-02 13:30 ` Vasil Dimov [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=YfqHhyZ8eL3ZUiBw@smle \
--to=vd@freebsd.org \
--cc=bitcoin-dev@lists.linuxfoundation.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox