Skip to content

Commit 481175f

Browse files
committed
merge bitcoin#27719: remove Tor link & generalize onion getnodeaddresses RPC
1 parent 378ad01 commit 481175f

File tree

3 files changed

+4
-11
lines changed

3 files changed

+4
-11
lines changed

doc/cjdns.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -91,5 +91,4 @@ There are several ways to see your CJDNS address in Dash Core:
9191
To see which CJDNS peers your node is connected to, use `dash-cli -netinfo 4`
9292
or the `getpeerinfo` RPC (i.e. `dash-cli getpeerinfo`).
9393

94-
To see which CJDNS addresses your node knows, use the `getnodeaddresses 0 cjdns`
95-
RPC.
94+
You can use the `getnodeaddresses` RPC to fetch a number of CJDNS peers known to your node; run `dash-cli help getnodeaddresses` for details.

doc/i2p.md

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -109,8 +109,7 @@ incoming I2P connections (`-i2pacceptincoming`):
109109
To see which I2P peers your node is connected to, use `dash-cli -netinfo 4`
110110
or the `getpeerinfo` RPC (e.g. `dash-cli getpeerinfo`).
111111

112-
To see which I2P addresses your node knows, use the `getnodeaddresses 0 i2p`
113-
RPC.
112+
You can use the `getnodeaddresses` RPC to fetch a number of I2P peers known to your node; run `dash-cli help getnodeaddresses` for details.
114113

115114
## Compatibility
116115

doc/tor.md

Lines changed: 2 additions & 7 deletions
Original file line numberDiff line numberDiff line change
@@ -2,11 +2,7 @@
22

33
It is possible to run Dash Core as a Tor onion service, and connect to such services.
44

5-
The following directions assume you have a Tor proxy running on port 9050. Many
6-
distributions default to having a SOCKS proxy listening on port 9050, but others
7-
may not. In particular, the Tor Browser Bundle defaults to listening on port 9150.
8-
See [Tor Project FAQ:TBBSocksPort](https://www.torproject.org/docs/faq.html.en#TBBSocksPort)
9-
for how to properly configure Tor.
5+
The following directions assume you have a Tor proxy running on port 9050. Many distributions default to having a SOCKS proxy listening on port 9050, but others may not. In particular, the Tor Browser Bundle defaults to listening on port 9150.
106

117
## Compatibility
128

@@ -30,8 +26,7 @@ CLI `-addrinfo` returns the number of addresses known to your node per
3026
network. This can be useful to see how many onion peers your node knows,
3127
e.g. for `-onlynet=onion`.
3228

33-
To fetch a number of onion addresses that your node knows, for example seven
34-
addresses, use the `getnodeaddresses 7 onion` RPC.
29+
You can use the `getnodeaddresses` RPC to fetch a number of onion peers known to your node; run `dash-cli help getnodeaddresses` for details.
3530

3631
## 1. Run Dash Core behind a Tor proxy
3732

0 commit comments

Comments
 (0)