diff options
| author | W. J. van der Laan <laanwj@protonmail.com> | 2021-08-02 10:56:57 +0200 |
|---|---|---|
| committer | W. J. van der Laan <laanwj@protonmail.com> | 2021-08-02 11:03:29 +0200 |
| commit | fd9c22ca69d814815554bfe8acf995cc30afdc2e (patch) | |
| tree | c61e93081ff208c55420740d65040522a72a6a5c /doc | |
| parent | f2e41d11097dde1c841bcaa8615886c984f71632 (diff) | |
| parent | d2dffd5be4c8f6a1942dd971d09707c3620a1689 (diff) | |
| download | bitcoin-fd9c22ca69d814815554bfe8acf995cc30afdc2e.tar.xz | |
Merge bitcoin/bitcoin#22589: net, doc: update I2P hardcoded seeds and docs for 22.0
d2dffd5be4c8f6a1942dd971d09707c3620a1689 doc: add info to i2p.md about IBD time and multiple networks (Jon Atack)
2962640c49cf38f76345e45e63045a8f0eed5c61 contrib, p2p: update I2P hardcoded seeds (Jon Atack)
Pull request description:
- Update the I2P seeds with the latest ones I can connect to (feedback welcome).
- Update the I2P doc with frequently asked and reported info: IBD speed and running with other networks.
ACKs for top commit:
tryphe:
ACK d2dffd5be4c8f6a1942dd971d09707c3620a1689
duncandean:
ACK d2dffd5
willcl-ark:
ACK d2dffd5be4c8f6a1942dd971d09707c3620a1689
laanwj:
ACK d2dffd5be4c8f6a1942dd971d09707c3620a1689
vasild:
ACK d2dffd5be4c8f6a1942dd971d09707c3620a1689
Tree-SHA512: 1edda0eb77b4e224b44961849b36c5a13e1eb14bdc50f909ec44d7fe926c259cada62404906594a1cf68ffd96254647ac49f24248214b42403ecebae45135e63
Diffstat (limited to 'doc')
| -rw-r--r-- | doc/i2p.md | 12 |
1 files changed, 10 insertions, 2 deletions
diff --git a/doc/i2p.md b/doc/i2p.md index 27ef4d9d9f..3a507a25ab 100644 --- a/doc/i2p.md +++ b/doc/i2p.md @@ -47,13 +47,21 @@ information in the debug log about your I2P configuration and connections. Run `bitcoin-cli help logging` for more information. It is possible to restrict outgoing connections in the usual way with -`onlynet=i2p`. I2P support was added to Bitcoin Core in version 22.0 (mid 2021) +`onlynet=i2p`. I2P support was added to Bitcoin Core in version 22.0 (mid-2021) and there may be fewer I2P peers than Tor or IP ones. Therefore, using `onlynet=i2p` alone (without other `onlynet=`) may make a node more susceptible to [Sybil attacks](https://en.bitcoin.it/wiki/Weaknesses#Sybil_attack). Use `bitcoin-cli -addrinfo` to see the number of I2P addresses known to your node. -## I2P related information in Bitcoin Core +Another consideration with `onlynet=i2p` is that the initial blocks download +phase when syncing up a new node can be very slow. This phase can be sped up by +using other networks, for instance `onlynet=onion`, at the same time. + +In general, a node can be run with both onion and I2P hidden services (or +any/all of IPv4/IPv6/onion/I2P), which can provide a potential fallback if one +of the networks has issues. + +## I2P-related information in Bitcoin Core There are several ways to see your I2P address in Bitcoin Core: - in the debug log (grep for `AddLocal`, the I2P address ends in `.b32.i2p`) |