phantom/bitcoin
1
0
Fork 0
mirror of https://github.com/bitcoin/bitcoin.git synced 2025-04-29 23:09:44 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 1

Update i2p.md and tor.md regarding -onlynet config option

Browse source
This commit is contained in:
Jon Atack 2021-08-06 11:46:43 +02:00
parent d67330d112
commit bebcf785c0
No known key found for this signature in database
GPG key ID: 4F5721B3D0E3921D
2 changed files with 28 additions and 13 deletions
Show stats Download patch file Download diff file Expand all files Collapse all files

31
doc/i2p.md
View file

@ -42,15 +42,30 @@ named `i2p_private_key` in the Bitcoin Core data directory.
## Additional configuration options related to I2P ## Additional configuration options related to I2P
You may set the `debug=i2p` config logging option to have additional ```
information in the debug log about your I2P configuration and connections. Run -debug=i2p
`bitcoin-cli help logging` for more information. ```
It is possible to restrict outgoing connections in the usual way with Set the `debug=i2p` config logging option to see additional information in the
`onlynet=i2p`. I2P support was added to Bitcoin Core in version 22.0 (mid-2021) debug log about your I2P configuration and connections. Run `bitcoin-cli help
and there may be fewer I2P peers than Tor or IP ones. Therefore, using logging` for more information.
`onlynet=i2p` alone (without other `onlynet=`) may make a node more susceptible
to [Sybil attacks](https://en.bitcoin.it/wiki/Weaknesses#Sybil_attack). Use ```
-onlynet=i2p
```
Make outgoing connections only to I2P addresses. Incoming connections are not
affected by this option. It can be specified multiple times to allow multiple
network types, e.g. onlynet=ipv4, onlynet=ipv6, onlynet=onion, onlynet=i2p.
Warning: if you use -onlynet with values other than onion, and the -onion or
-proxy option is set, then outgoing onion connections will still be made; use
-noonion or -onion=0 to disable outbound onion connections in this case.
I2P support was added to Bitcoin Core in version 22.0 and there may be fewer I2P
peers than Tor or IP ones. Therefore, using I2P alone without other networks may
make a node more susceptible to [Sybil
attacks](https://en.bitcoin.it/wiki/Weaknesses#Sybil_attack). You can use
`bitcoin-cli -addrinfo` to see the number of I2P addresses known to your node. `bitcoin-cli -addrinfo` to see the number of I2P addresses known to your node.
Another consideration with `onlynet=i2p` is that the initial blocks download Another consideration with `onlynet=i2p` is that the initial blocks download

10
doc/tor.md
View file

@ -57,11 +57,11 @@ outgoing connections, but more is possible.
-onlynet=onion Make outgoing connections only to .onion addresses. Incoming -onlynet=onion Make outgoing connections only to .onion addresses. Incoming
connections are not affected by this option. This option can be connections are not affected by this option. This option can be
specified multiple times to allow multiple network types, e.g. specified multiple times to allow multiple network types, e.g.
ipv4, ipv6 or onion. If you use this option with values other onlynet=ipv4, onlynet=ipv6, onlynet=onion, onlynet=i2p.
than onion you *cannot* disable onion connections; outgoing onion Warning: if you use -onlynet with values other than onion, and
connections will be enabled when you use -proxy or -onion. Use the -onion or -proxy option is set, then outgoing onion
-noonion or -onion=0 if you want to be sure there are no outbound connections will still be made; use -noonion or -onion=0 to
onion connections over the default proxy or your defined -proxy. disable outbound onion connections in this case.
In a typical situation, this suffices to run behind a Tor proxy: In a typical situation, this suffices to run behind a Tor proxy: