TOR support

[Scalena]

Integrated TOR support may be an important feature for the privacy-conscious Monero community. This would include connecting to peers through the socks5 TOR proxy, running a p2pool node as a hidden service and advertising its .onion address to peers. Similarly, I2P support can be considered, but this might better be addressed in a separate issue.

[SChernykh]

It's in my list of things to do, but be aware that the typical ping time when connecting through TOR is around 500 ms which is very bad for mining. P2Pool has block time of 10 seconds, and 500 ms ping will give you a lot of uncle blocks = direct loss of profitability.

As of now, you can already run a P2Pool node as a hidden service for your mining rigs - XMRig supports SOCKS5 proxies and no special support is required from P2Pool to run as a hidden service.

[Scalena]

I realize that the longer latency of TOR could be a problem. However, unless it makes mining unrealistic, it might be an acceptable cost for some. At least, I'd look forward to it if you decide to implement it.

[honobo]

p2pool --host 127.0.0.1 --socks5 127.0.0.1:9050

[hundehausen]

Here is an example of Seth: https://github.com/sethforprivacy/p2pool-docker/blob/main/examples/docker-compose.yml

[hassan0ibrahim]

Is there any updates on this

[SChernykh]

@hassan0ibrahim https://github.com/SChernykh/p2pool/blob/master/docs/COMMAND_LINE.MD
There is --socks5 and --no-dns command line options. If you use these two with TOR SOCKS5 proxy, all P2Pool traffic will go through TOR. You can also set up a TOR hidden service for P2Pool Stratum port using standard approach - nothing from P2Pool side is needed for this.