diff options
| author | Marnix <93143998+MarnixCroes@users.noreply.github.com> | 2023-05-22 15:44:37 +0200 |
|---|---|---|
| committer | Marnix <93143998+MarnixCroes@users.noreply.github.com> | 2023-06-01 15:52:51 +0200 |
| commit | 6fce5ddc17ac9d1e07849f92088ea3f7cfcafe26 (patch) | |
| tree | 2215ae8ad5af0579fc6c42133cea2eb860814c25 /doc/i2p.md | |
| parent | 28653a596ab7e0811ffec3bbb7632e17d54f8e43 (diff) | |
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/i2p.md')
| -rw-r--r-- | doc/i2p.md | 3 |
1 files changed, 1 insertions, 2 deletions
diff --git a/doc/i2p.md b/doc/i2p.md index 1599c2fe0f..2653a867f4 100644 --- a/doc/i2p.md +++ b/doc/i2p.md @@ -111,8 +111,7 @@ incoming I2P connections (`-i2pacceptincoming`): To see which I2P peers your node is connected to, use `bitcoin-cli -netinfo 4` or the `getpeerinfo` RPC (e.g. `bitcoin-cli getpeerinfo`). -To see which I2P addresses your node knows, use the `getnodeaddresses 0 i2p` -RPC. +You can use the `getnodeaddresses` RPC to fetch a number of I2P peers known to your node; run `bitcoin-cli help getnodeaddresses` for details. ## Compatibility |