aboutsummaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorbrunoerg <brunoely.gc@gmail.com>2024-04-02 09:01:15 -0300
committerbrunoerg <brunoely.gc@gmail.com>2024-04-04 18:32:39 -0300
commit2179e2c3209a41c1419f1f5ed6270a0dad68b50d (patch)
treee5fe03c771028b6bfd1d46e3eaac2032672beb98 /doc
parentc407caa2972191d6a795228fd4bcdcd4be41d4a7 (diff)
downloadbitcoin-2179e2c3209a41c1419f1f5ed6270a0dad68b50d.tar.xz
doc: i2p: improve `-i2pacceptincoming` mention
Diffstat (limited to 'doc')
-rw-r--r--doc/i2p.md4
1 files changed, 2 insertions, 2 deletions
diff --git a/doc/i2p.md b/doc/i2p.md
index b6c07388b7..b769a74df4 100644
--- a/doc/i2p.md
+++ b/doc/i2p.md
@@ -79,8 +79,8 @@ one of the networks has issues.
## Persistent vs transient I2P addresses
The first time Bitcoin Core connects to the I2P router, it automatically
-generates a persistent I2P address and its corresponding private key by default
-or if `-i2pacceptincoming=1` is set. The private key is saved in a file named
+generates a persistent I2P address and its corresponding private key by default,
+unless `-i2pacceptincoming=0` is set. The private key is saved in a file named
`i2p_private_key` in the Bitcoin Core data directory. The persistent I2P
address is used for making outbound connections and accepting inbound
connections.