Retropex/bitcoin
1
0
Fork 0
mirror of https://github.com/Retropex/bitcoin.git synced 2025-08-05 14:34:49 +02:00
Code Issues Actions Packages Projects Releases Wiki Activity

doc: update bandwidth section of I2P documentation

Browse Source
This commit is contained in:
jonatack 2023-01-06 11:46:15 -08:00
parent 0ed9cc5892
commit dffa319457
1 changed files with 22 additions and 11 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

33
doc/i2p.md
View File

@ -134,14 +134,19 @@ port (`TO_PORT`) is always set to 0 and is not in the control of Bitcoin Core.
## Bandwidth ## Bandwidth
I2P routers may route a large amount of general network traffic with their By default, your node shares bandwidth and transit tunnels with the I2P network
default settings. Check your router's configuration to limit the amount of this in order to increase your anonymity with cover traffic, help the I2P router used
traffic relayed, if desired. by your node integrate optimally with the network, and give back to the network.
It's important that the nodes of a popular application like Bitcoin contribute
as much to the I2P network as they consume.
With `i2pd`, the amount of bandwidth being shared with the wider network can be It is possible, though strongly discouraged, to change your I2P router
adjusted with the `bandwidth`, `share` and `transittunnels` options in your configuration to limit the amount of I2P traffic relayed by your node.
`i2pd.conf` file. For example, to limit total I2P traffic to 256KB/s and share
50% of this limit for a maximum of 20 transit tunnels: With `i2pd`, this can be done by adjusting the `bandwidth`, `share` and
`transittunnels` options in your `i2pd.conf` file. For example, to limit total
I2P traffic to 256KB/s and share 50% of this limit for a maximum of 20 transit
tunnels:
``` ```
bandwidth = 256 bandwidth = 256
@ -151,9 +156,15 @@ share = 50
transittunnels = 20 transittunnels = 20
``` ```
If you prefer not to relay any public I2P traffic and only permit I2P traffic
from programs which are connecting via the SAM proxy, e.g. Bitcoin Core, you
can set the `notransit` option to `true`.
Similar bandwidth configuration options for the Java I2P router can be found in Similar bandwidth configuration options for the Java I2P router can be found in
`http://127.0.0.1:7657/config` under the "Bandwidth" tab. `http://127.0.0.1:7657/config` under the "Bandwidth" tab.
Before doing this, please see the "Participating Traffic Considerations" section
in [Embedding I2P in your Application](https://geti2p.net/en/docs/applications/embedding).
In most cases, the default router settings should work fine.
## Bundling I2P in a Bitcoin application
Please see the "General Guidance for Developers" section in https://geti2p.net/en/docs/api/samv3
if you are developing a downstream application that may be bundling I2P with Bitcoin.