aboutsummaryrefslogtreecommitdiff
path: root/doc/cjdns.md
diff options
context:
space:
mode:
authorMarnix <93143998+MarnixCroes@users.noreply.github.com>2023-05-22 15:44:37 +0200
committerMarnix <93143998+MarnixCroes@users.noreply.github.com>2023-06-01 15:52:51 +0200
commit6fce5ddc17ac9d1e07849f92088ea3f7cfcafe26 (patch)
tree2215ae8ad5af0579fc6c42133cea2eb860814c25 /doc/cjdns.md
parent28653a596ab7e0811ffec3bbb7632e17d54f8e43 (diff)
downloadbitcoin-6fce5ddc17ac9d1e07849f92088ea3f7cfcafe26.tar.xz
doc: update getnodeaddresses for CJDNS, I2P and Tor and rm link
- unify bitcoin-cli getnodeaddresses for CJDNS, I2P and Tor - remove outdated link to Tor project
Diffstat (limited to 'doc/cjdns.md')
-rw-r--r--doc/cjdns.md3
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/cjdns.md b/doc/cjdns.md
index b69564729f..031cd1978b 100644
--- a/doc/cjdns.md
+++ b/doc/cjdns.md
@@ -112,5 +112,4 @@ There are several ways to see your CJDNS address in Bitcoin Core:
To see which CJDNS peers your node is connected to, use `bitcoin-cli -netinfo 4`
or the `getpeerinfo` RPC (i.e. `bitcoin-cli getpeerinfo`).
-To see which CJDNS addresses your node knows, use the `getnodeaddresses 0 cjdns`
-RPC.
+You can use the `getnodeaddresses` RPC to fetch a number of CJDNS peers known to your node; run `bitcoin-cli help getnodeaddresses` for details.