Skip to content
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

Mining over privacy network (Tor/i2p) setting #32

Open
CryptoGrampy opened this issue May 3, 2023 · 1 comment
Open

Mining over privacy network (Tor/i2p) setting #32

CryptoGrampy opened this issue May 3, 2023 · 1 comment
Labels
feature New feature or request

Comments

@CryptoGrampy
Copy link

Would it be possible to add a simple setting for Gupax to run P2Pool / Mine over i2p or Tor? It would be great to see this software as resilient as possible for areas where it may be dangerous to be running p2pool software.

@CryptoGrampy CryptoGrampy added the feature New feature or request label May 3, 2023
@hinto-janai
Copy link
Owner

Gupax has a Tor client inside but not a server. It can create circuits, connect to them, send/recv bytes via that circuit, but it can't forward arbitrary bytes from a different process.

Although, that part can be added. P2Pool also can natively connect to a SOCKS proxy which makes it easier.

I didn't add this initially because of the downside of using a latency-heavy connection to mine on a latency-sensitive pool like P2Pool. In the case of remote nodes, you can negate this by picking a fast node close to you, but with Tor, the nodes you get routed through are random (technically, you can manually pick your circuit but that's... a bad idea).

A circuit that takes 5 seconds from You -> Tor -> P2Pool and back means all your blocks will be stale.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
feature New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants