From babb4a39c2ac28c141af251a224691f1f8c4d3a8 Mon Sep 17 00:00:00 2001 From: jahway603 Date: Wed, 26 Feb 2025 23:42:31 -0500 Subject: [PATCH] Removed RPCs we do not have from TOR, i2p, and CJDNS docs --- doc/cjdns.md | 7 ++----- doc/i2p.md | 6 +----- doc/tor.md | 4 ---- 3 files changed, 3 insertions(+), 14 deletions(-) diff --git a/doc/cjdns.md b/doc/cjdns.md index 4b47bb8ac..17f5773d2 100644 --- a/doc/cjdns.md +++ b/doc/cjdns.md @@ -106,10 +106,7 @@ details. ## CJDNS-related information in Hush There are several ways to see your CJDNS address in Hush: -- in the "Local addresses" output of CLI `-netinfo` - in the "localaddresses" output of RPC `getnetworkinfo` -To see which CJDNS peers your node is connected to, use `hush-cli -netinfo 4` -or the `getpeerinfo` RPC (i.e. `hush-cli getpeerinfo`). - -You can use the `getnodeaddresses` RPC to fetch a number of CJDNS peers known to your node; run `hush-cli help getnodeaddresses` for details. +To see which CJDNS peers your node is connected to, use `hush-cli getpeerinfo` +RPC. diff --git a/doc/i2p.md b/doc/i2p.md index 8cc3a6557..3e5fabb39 100644 --- a/doc/i2p.md +++ b/doc/i2p.md @@ -100,15 +100,11 @@ address. There are several ways to see your I2P address if accepting incoming I2P connections (`-i2pacceptincoming`): -- in the "Local addresses" output of CLI `-netinfo` - in the "localaddresses" output of RPC `getnetworkinfo` - in the debug log (grep for `AddLocal`; the I2P address ends in `.b32.i2p`) - in the i2p/i2pd web console under "SAM Sessions" -To see which I2P peers your node is connected to, use `hush-cli -netinfo 4` -or the `getpeerinfo` RPC (e.g. `hush-cli getpeerinfo`). - -To see which I2P addresses your node knows, use the `getnodeaddresses 0 i2p` +To see which I2P peers your node is connected to, use `hush-cli getpeerinfo` RPC. ## Compatibility diff --git a/doc/tor.md b/doc/tor.md index fe0608888..002b95754 100644 --- a/doc/tor.md +++ b/doc/tor.md @@ -16,7 +16,6 @@ configure Tor. ## How to see information about your Tor configuration via Hush There are several ways to see your local onion address in Hush: -- in the "Local addresses" output of CLI `-netinfo` - in the "localaddresses" output of RPC `getnetworkinfo` - in the debug log (grep for "AddLocal"; the Tor address ends in `.onion`) @@ -27,9 +26,6 @@ CLI `-addrinfo` returns the number of addresses known to your node per network. This can be useful to see how many onion peers your node knows, e.g. for `-onlynet=onion`. -To fetch a number of onion addresses that your node knows, for example seven -addresses, use the `getnodeaddresses 7 onion` RPC. - ## 1. Run Hush behind a Tor proxy The first step is running Hush behind a Tor proxy. This will already anonymize all