The core problem that BTC has and we inherited is that if you abruptly change your -onlynet setting, for instance from -onlynet=onion to -onlynet=i2p you may get stuck with only "unreachable" peers in peers.dat and your node will not be able to get any outbound connections. The manual fix is to delete/move peers.dat and restart the node.
The better fix is for the node to keep track of peers by network and for it to realize that all peers in peers.dat are "unreachable" and know that it should try harder to find peers.
This BTC PR Review Club link is a very good introduction to the issue:
https://bitcoincore.reviews/26847
which is about https://github.com/bitcoin/bitcoin/pull/26847
The core problem that BTC has and we inherited is that if you abruptly change your `-onlynet` setting, for instance from `-onlynet=onion` to `-onlynet=i2p` you may get stuck with only "unreachable" peers in peers.dat and your node will not be able to get any outbound connections. The manual fix is to delete/move peers.dat and restart the node.
The better fix is for the node to keep track of peers by network and for it to realize that all peers in peers.dat are "unreachable" and know that it should try harder to find peers.
This BTC PR Review Club link is a very good introduction to the issue:
https://bitcoincore.reviews/26847
which is about https://github.com/bitcoin/bitcoin/pull/26847
The core problem that BTC has and we inherited is that if you abruptly change your
-onlynetsetting, for instance from-onlynet=onionto-onlynet=i2pyou may get stuck with only "unreachable" peers in peers.dat and your node will not be able to get any outbound connections. The manual fix is to delete/move peers.dat and restart the node.The better fix is for the node to keep track of peers by network and for it to realize that all peers in peers.dat are "unreachable" and know that it should try harder to find peers.