Quote from: RequestPrivacy on June 29, 2022, 02:50:07 PM

Quote from: NotATether on June 29, 2022, 05:49:21 AM

The config directive to add nodes is called addnodes not addnotes (there is a d not a t).

Good catch, thanks for that. I disabled all of them now though, since I wanted to try if bitcoind finds nodes without my help once I got my i2p problem sorted out (I initially added them bc I thought i2pd may need some traffic to prevent the automatic stopping of the i2pd.service. Turns out that isn't true and the problem was rooted in the i2pd since the standard I2P router works).

Quote from: vv181 on June 29, 2022, 09:25:05 AM

You might want to try to update it to the latest version. Or just use the official implementation, I2P Router, I do use it, and so far there haven't been any problems.

The installation could be done by following: https://geti2p.net/en/download/debian#debian. Then enable the SAM on the configuration page(http://127.0.0.1:7657/configclients). With the corrected bitcoin config, you should be good to go.

I followed your provided resources and installed the official java I2P router and enabled the SAM bridge. The i2p side of things seem to work now. I can see bandwidth and memory usage, as well as peer count and tunnels in the I2P Router Console. Thanks for that!

My bitconid seems to prefer onion sites though. I haven't seen it to connect to i2p bitcoin nodes i.e.

Code:

Thanks for the post!
bitcoin@debian:~/.bitcoin $ bitcoin-cli -addrinfo

bitcoin@debian:~/.bitcoin $ bitcoin-cli -netinfo 4

bitcoin@debian:~/.bitcoin $ bitcoin-cli getpeerinfo

show me bitcoind found only 5 i2p peers - but they must have been dropped, since the last command always shows non-i2p nodes (I'm looking once in a while, 1h running).

How does bitcoind choose to distribute peers across networks? Do I have to change the available bandwidth of my i2p router so it can "compete" better with e.g. tor?