|
|
@ -88,8 +88,8 @@ don't want to publish it. |
|
|
|
In the case where the auto service is authenticated through a password, it will |
|
|
|
be necessary to add the option `--tor-service-password=yourpassword` (not the hash). |
|
|
|
|
|
|
|
The created non-persistent .onion address wil be shown by the `lightning-cli getinfo`command. |
|
|
|
The others nodes will be able to `connect` to this .onion address through the |
|
|
|
The created non-persistent .onion address will be shown by the `lightning-cli getinfo` |
|
|
|
command. The other nodes will be able to `connect` to this .onion address through the |
|
|
|
9735 port. |
|
|
|
|
|
|
|
#### Creation of a hidden service for a persistent .onion address |
|
|
@ -172,7 +172,7 @@ A non-persistent .onion address is generated by accessing an [auto service](#cre |
|
|
|
connections (connect to a .onion address) by adding the |
|
|
|
`--proxy=127.0.0.1:9050` option. |
|
|
|
|
|
|
|
#### Case 1 c-lightning has a public IP address and no Tor hidden service address, but can connect to an onion address via a Tor socks 5 proxy. |
|
|
|
#### Case #1 c-lightning has a public IP address and no Tor hidden service address, but can connect to an onion address via a Tor socks 5 proxy. |
|
|
|
|
|
|
|
Without a .onion address, the node won't be reachable through Tor by other |
|
|
|
nodes but it will always be able to `connect` to a Tor enabled node |
|
|
|