INTcoin’s daemon has first-class Tor support — you can run as a
hidden service so peers reach you over .onion without exposing
your IP.
1. Install Tor
sudo apt install tor # Debian / Ubuntu
sudo systemctl enable --now tor
Verify:
ss -tlnp | grep 9050 # SOCKS proxy
2. Add control-port hidden-service config
INTcoin uses Tor’s control port (9051) to create persistent v3
onions on startup. Edit /etc/tor/torrc:
ControlPort 9051
CookieAuthentication 1
CookieAuthFileGroupReadable 1
Add the intcoin user to the debian-tor group so it can read the
cookie:
sudo usermod -aG debian-tor intcoin
sudo systemctl restart tor
3. Add the INTcoin Tor config
In intcoin.conf:
tor=1
listenonion=1
torcontrol=127.0.0.1:9051
onlynet=onion # optional: outbound only via Tor
proxy=127.0.0.1:9050 # SOCKS for clearnet peers if onlynet not set
Restart intcoind. On startup it generates (or loads) a persistent
v3 onion key and listens on it.
4. Verify
intcoin-cli getnetworkinfo
Look for the localaddresses field — your .onion should appear
there. From a second machine running INTcoin, addnode <youronion>:2210
should connect.
I2P
I2P setup follows the same pattern, but uses i2psam= and the SAM
bridge on 127.0.0.1:7656. Persistent destinations are stored under
<datadir>/i2p_private_key. Full guide:
I2P configuration thread.
Why bother
- Hides your real IP from chain peers
- Lets you accept inbound connections from behind any NAT
- Resists eclipse and partitioning attacks (when combined with diverse
clearnet peers)
Trade-off: latency. Tor adds 100–500 ms per hop, so block propagation
is slower. Mixed clearnet + onion is usually the right balance.