sikkienl/dash
1
0
Fork 0
mirror of https://github.com/dashpay/dash.git synced 2024-12-24 19:42:46 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity

merge bitcoin#22589: update I2P hardcoded seeds and docs for 22.0

Browse Source 
Arguably partial; however the commit it excludes is not relevant

includes:
- d2dffd5be4c8f6a1942dd971d09707c3620a1689
This commit is contained in:
Kittywhiskers Van Gogh 2024-05-27 08:11:24 +00:00 committed by pasta
parent 3b3b1b8e00
commit 68ea6cc5c5
No known key found for this signature in database
GPG Key ID: 52527BEDABE87984
1 changed files with 10 additions and 2 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

12
doc/i2p.md
View File

@ -47,13 +47,21 @@ information in the debug log about your I2P configuration and connections. Run
`dash-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 Dash Core in version 20.0 (fall 2023)
`onlynet=i2p`. I2P support was added to Dash Core in version 20.0 (fall-2023)
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.dash.it/wiki/Weaknesses#Sybil_attack). Use
`dash-cli -addrinfo` to see the number of I2P addresses known to your node.
## I2P related information in Dash 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 Dash Core
There are several ways to see your I2P address in Dash Core:
- in the debug log (grep for `AddLocal`, the I2P address ends in `.b32.i2p`)