INTcoin has native I2P support via the SAM 3.1 protocol. Your node can operate as an I2P destination, making your real IP address invisible to peers.
Prerequisites
Install the I2P router on your system. On Debian/Ubuntu:
sudo apt install i2pd
sudo systemctl enable --now i2pd
The I2P router needs a few minutes to build tunnels after first start. The SAM interface listens on 127.0.0.1:7656 by default.
Verify SAM is enabled in /etc/i2pd/i2pd.conf:
[sam]
enabled = true
address = 127.0.0.1
port = 7656
Configure INTcoin
Add to your intcoin.conf:
i2p=1
i2psam=127.0.0.1:7656
Restart intcoind. The node will create a persistent I2P destination and begin accepting connections over I2P.
Check it’s working:
intcoin-cli getnetworkinfo
Look for the I2P section showing your .b32.i2p address and reachable status.
I2P-Only Mode
To run exclusively over I2P with no clearnet connections:
onlynet=i2p
i2p=1
i2psam=127.0.0.1:7656
dnsseed=0
You’ll need to manually add at least one I2P peer to bootstrap:
addnode=<destination>.b32.i2p:2210
INTcoin I2P seed destinations are listed in the wiki.
Combined Tor + I2P
You can run both simultaneously:
tor=1
i2p=1
i2psam=127.0.0.1:7656
The node accepts connections on clearnet, Tor, and I2P, and will relay addresses across all networks.
Session Pooling
INTcoin maintains a pool of pre-warmed I2P sessions to reduce connection latency. This is automatic — no configuration needed. The pool holds up to 10 unused sessions and reuses them for new outbound connections.
Notes
- I2P connections use the same V2 post-quantum encrypted transport as clearnet connections (Kyber1024 + ChaCha20-Poly1305)
- I2P destinations are persistent across restarts (stored in your data directory)
- I2P adds latency compared to clearnet — block propagation may be slightly slower
- The I2P router itself consumes some bandwidth for relay participation — this is normal and helps the network