-
Notifications
You must be signed in to change notification settings - Fork 137
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
TOR support #202
Comments
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. |
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. |
|
Here is an example of Seth: https://github.com/sethforprivacy/p2pool-docker/blob/main/examples/docker-compose.yml |
Is there any updates on this |
@hassan0ibrahim https://github.com/SChernykh/p2pool/blob/master/docs/COMMAND_LINE.MD |
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.
The text was updated successfully, but these errors were encountered: