-
Notifications
You must be signed in to change notification settings - Fork 2k
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.md: change alpha to beta testnet, add new zcash hidden service address #1511
Tor.md: change alpha to beta testnet, add new zcash hidden service address #1511
Conversation
…nea/zcash into document-hidden-service-in-tor.md
Launch zcashd as follows, adding the Zcash hidden server: | ||
|
||
zcashd -onion=127.0.0.1:9050 -addnode=zctestseie6wxgio.onion | ||
./zcashd -onion=127.0.0.1:9050 -connect=zctestseie6wxgio.onion |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
There are two scenarios we should document:
- You want to connect to just a single node, in which cause use -connect.
- You want to connect to multiple tor nodes, -addnode=.. -dnsseed=0 -onlynet=onion (or it might be -onlynet=tor)
@@ -92,13 +93,9 @@ for normal IPv4/IPv6 communication, use: | |||
To test your set-up, you might want to try connecting via Tor to just a | |||
a single Zcash hidden server. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If connecting to the zcash server which has just been setup above in section 2, might want to say test and launch zcashd on a different computer. Otherwise a user might get confused and try to connect from the same computer as the one they are trying to connect to.
@arcalinea There's another PR which updates tor.md so I want to get this one merged soon. Thanks. |
@arcalinea Thanks. ACK |
📌 Commit 1f48a34 has been approved by |
☀️ Test successful - zcash |
Note: When @ageis and I checked this the other day, we were getting multiple peer connections. Think we said we'd change this before launch, so I opened issue #1510. Leaving documentation to expect a single peer.