Proxify or Anonymize P2P Traffic

By default, Blacknet node establishes clearnet connections to other nodes and can automatically use locally available supported overlay networks. Network configuration is stored in file blacknet.conf.

With I2P

I2P implements garlic routing.[1]

SAM V3.2 is supported. It may be disabled by default in I2P router. You can enable it in I2P Router Console ➜ Configure I2P Router ➜ Clients ➜ SAM application bridge.

I2P bridge for .b32.i2p connections:

i2psamhost=127.0.0.1
i2psamport=7656

With Tor

Tor implements onion routing and relies on directory authorities.[2]

Onion service v3 is supported. Tor control port may be disabled by default in torrc config file.

Tor proxy for outgoing .onion connections:

torhost=127.0.0.1
torport=9050

Tor proxy for outgoing TCP/IP connections:

listen=false

proxyhost=127.0.0.1
proxyport=9050

Tor control port to listen on .onion address:

torcontrol=9051

With SOCKS5

TCP/IP can be proxified using SOCKS5 protocol:

listen=false

proxyhost=127.0.0.1
proxyport=9050

or disabled:

ipv4=false
ipv6=false
listen=false

About Helianthus

Anonymization solutions described above don’t employ any Sybil-resistance mechanism.[1][2] We plan to tickle this problem in a distant future under a subproject codenamed Helianthus.

Regarding Mesh Networks

We plan to add support for mesh networks. Let us know which ones you would like to see.

References

  1. I2P’s Threat Model, .
  2. Safeguarding the Tor network: our commitment to network health and supporting relay operators, .