A "good problem to have" is still a problem.

This may be a premature or erroneous conclusion.

I have been running bitcoind over I2P since more than 2 years now without issues, apart from one bug recently that the router in question (i2pd) appears to have patched with the latest 2.45.0 release (am still testing).

We haven't seen a notable increase in the number of bitcoin peers running I2P recently, and most bitcoin nodes don't change the default I2P configuration settings or configure bitcoind to turn off I2P listening. It is likely that bitcoin nodes may not be the issue at all. This is also the view of the developers of i2pd, the I2P C++ router that most Bitcoin nodes with an I2P service are using.

Here are two replies to the OP by someone from the I2P Java router team:

• https://twitter.com/DarknetJr/status/1611389891950133250
• https://twitter.com/DarknetJr/status/1611400846654201856

Here is an article I wrote recently on the topic of why and how to use I2P and CJDNS with your Bitcoin Core node:

• https://jonatack.github.io/articles/using-alternative-p2p-networks-with-bitcoin-core

It is more interesting to see how Indra will fix this issue for bitcoin / LN nodes. I really hope will get more help. #71383

The I2P network isn't nearly as anonymous as the Tor network, and people are ignoring that. Why do you think it still works?