-
Notifications
You must be signed in to change notification settings - Fork 170
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
Comments
Yes - working on that next. |
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? |
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.
This could also be a DNS Proxy issue
Yes, Netlayer also works with system installed tor since version 0.6 |
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. Some suggestions:
|
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. |
Do you have any plans to support tor?
The text was updated successfully, but these errors were encountered: