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

ElectrumX Onion host support #9

Closed
java4tech opened this issue Sep 8, 2020 · 5 comments
Closed

ElectrumX Onion host support #9

java4tech opened this issue Sep 8, 2020 · 5 comments

Comments

@java4tech
Copy link

Do you have any plans to support tor?

@craigraw
Copy link
Collaborator

craigraw commented Sep 8, 2020

Yes - working on that next.

@craigraw
Copy link
Collaborator

It's already possible to connect Sparrow to a Tor hidden service (.onion address) if you are running tor locally - just set the proxy details in the server preferences appropriately e.g. 127.0.0.1:9050.

By supporting tor, do you mean bundling the tor binaries with Sparrow so that it does not need a locally running tor instance?

@java4tech
Copy link
Author

java4tech commented Sep 10, 2020

It's already possible to connect Sparrow to a Tor hidden service (.onion address) if you are running tor locally - just set the proxy details in the server preferences appropriately e.g. 127.0.0.1:9050.

I have tried to test it on Windows and got error on port 9050 (tried public nodes), I was getting connection refused but 9150 worked but still got the following error.

Could not connect:

Unsupported or unrecognized SSL message

This could also be a DNS Proxy issue

By supporting tor, do you mean bundling the tor binaries with Sparrow so that it does not need a locally running tor instance?

Yes, Netlayer also works with system installed tor since version 0.6

@java4tech
Copy link
Author

java4tech commented Sep 10, 2020

I was thinking about a use case where we can connect to any public node only for Sending Transaction, This can be used in a situation where user want's to use there server only for transaction update and don't want to reveal his node's IP while sending payment.
So In short:
We can keep or drop connection to our own node and connect to tor node>> Once transaction is broadcasted we can disconnect and connect back to our own node to check progress and balance. Attacker or analysis firms won't be able to map IP to our personal node.

Some suggestions:

  1. You can use Netlayer project to support native tor. It is used by bisq project, So it is maintained. (I have tested it on windows and It works). We might be able to check if local instance is running first and if not then we can try to start native tor. Otherwise we'll end up with multiple tor instances and that might cause other issue (not Sure).
  2. It'll be nice to have an option to disconnect node, user might want to do certain tasks while offline (Helpful if someone is using public node).

@craigraw
Copy link
Collaborator

Implemented built in Tor support and released in v0.9.4 - closing this off.

The idea to have a connection to a separate node for broadcasting is an interesting one - perhaps something for a future release.

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

No branches or pull requests

2 participants