<!-- Describe the issue -->
Expected behavior
10 outbound peers.
<!--- What behavior did you expect? -->
Actual behavior
I was playing around with Tor and i2p, testing v22.0rc2, and while manually adding connections, I realized that I had 16 outbound peers.
<!--- What was the actual behavior (provide screenshots if the issue is GUI-related)? -->
To reproduce
Start v22.0rc2, add peers in this guide via addnode Interestingly, it seems that having the addnode=[peer:port] in bitcoin.conf does not violate the 10 outbound peers limit, but if you add the node manually in the console, it does. I also had the following in my configuration file:
listen=1 assumevalid=0 dbcache=1000 addresstype=bech32 avoidpartialspends=1 changetype=bech32 maxapsfee=0.01 i2psam=127.0.0.1:7656 debug=tor debug=i2p
<!--- How reliably can you reproduce the issue, what are the steps to do so? -->
System information Reproduces reliably following the above steps.
<!-- What version of Bitcoin Core are you using, where did you get it (website, self-compiled, etc)? -->
Self compiled Bitcoin Core, with ./configure --without-miniupnpc --without-natpmp --enable-hardening --without-bdb --with-qrencode --disable-zmq --with-sqlite=yes
<!-- What type of machine are you observing the error on (OS/CPU and disk type)? -->
Qubes 4.0.4, in a Debian-10 standalone-VM with normal networking. Intel x86_64. SSD
Nothing weird in debug.log
<!-- GUI-related issue? What is your operating system and its version? If Linux, what is your desktop environment and graphical shell? -->
<!-- Any extra information that might be useful in the debugging process. -->
<!--- This is normally the contents of a `debug.log` or `config.log` file. Raw text or a link to a pastebin type site are preferred. -->
