mirror of
https://github.com/ChristopherA/Learning-Bitcoin-from-the-Command-Line.git
synced 2025-06-09 17:06:28 +00:00
edit
This commit is contained in:
parent
b0f5d4e381
commit
569d185a1f
@ -2,15 +2,16 @@
|
||||
|
||||
> :information_source: **NOTE:** This is a draft in progress, so that I can get some feedback from early reviewers. It is not yet ready for learning.
|
||||
|
||||
You've got a working Tor service, but if you want you can make changes to it.
|
||||
You've got a working Tor service, but over time you may wish to reset or otherwise adjust it.
|
||||
|
||||
## Reset Your `bitcoind` Onion Address
|
||||
|
||||
If you ever want to reset your onion address for `bitcoind`, just remove the `onion_private_key` in your data directory, such as `~/.bitcoin/testnet`:
|
||||
```
|
||||
$ cd ~/.bitcoin/testnet
|
||||
$ rm onion_private_key
|
||||
```
|
||||
Wehn you restart, a new onion address will be generated:
|
||||
When you restart, a new onion address will be generated:
|
||||
```
|
||||
2020-07-22T23:52:27Z tor: Got service ID pyrtqyiqbwb3rhe7, advertising service pyrtqyiqbwb3rhe7.onion:18333
|
||||
2020-07-22T23:52:27Z tor: Cached service private key to /home/standup/.bitcoin/testnet3/onion_private_key
|
||||
@ -18,9 +19,9 @@ Wehn you restart, a new onion address will be generated:
|
||||
|
||||
## Reset Your RPC Onion Address
|
||||
|
||||
If you want to reset your onion address for RPC access, you similarly delete the `HiddenServiceDirectory` and restart Tor:
|
||||
If you want to reset your onion address for RPC access, you similarly delete the appropriate `HiddenServiceDirectory` and restart Tor:
|
||||
```
|
||||
$ sudo rm -f /var/lib/tor/standup/
|
||||
$ sudo rm -rf /var/lib/tor/standup/
|
||||
$ sudo /etc/init.d/tor restart
|
||||
```
|
||||
|
||||
@ -46,15 +47,15 @@ addnode=address.onion
|
||||
addnode=address.onion
|
||||
addnode=address.onion
|
||||
```
|
||||
Afterward, restart `tor` and `bitcoind`
|
||||
Afterward, restart `tor` and `bitcoind`.
|
||||
|
||||
You should now be communicating exlusively on Tor. But, unless you are in a hostile state, this level of anonymity is probably not required. It also is not particularly recommended: you might greatly decrease your number of potential peers, inviting problems of censorship or even correlation. And, this setup may give you a false sense of anonymity that really doesn't exist on the Bitcoin network.
|
||||
You should now be communicating exlusively on Tor. But, unless you are in a hostile state, this level of anonymity is probably not required. It also is not particularly recommended: you might greatly decrease your number of potential peers, inviting problems of censorship or even correlation. You may also see lag. And, this setup may give you a false sense of anonymity that really doesn't exist on the Bitcoin network.
|
||||
|
||||
> :warning: **WARNING:** This setup is untested! Use at your own risk!
|
||||
|
||||
## Summary: Changing Your Bitcoin Hidden Services
|
||||
|
||||
You probably won't need to fool with your Onion services once you've investigated them but in case you do, here's how to reset a Tor address that has become compromised or to move over to exclusive-Tor use for your `bitcoind`.
|
||||
You probably won't need to fool with your Onion services once you've verified them, but in case you do, here's how to reset a Tor address that has become compromised or to move over to exclusive-Tor use for your `bitcoind`.
|
||||
|
||||
## What's Next?
|
||||
|
||||
|
Loading…
x
Reference in New Issue
Block a user