|
1 |
| -REDUCE TRAFFIC |
| 1 | +Reduce Traffic |
2 | 2 | ==============
|
3 | 3 |
|
4 |
| -Some node operators need to deal with bandwith cap given by their ISPs. |
| 4 | +Some node operators need to deal with bandwith caps imposed by their ISPs. |
5 | 5 |
|
6 | 6 | By default, bitcoin-core allows up to 125 connections to different peers, 8 of
|
7 |
| -them outbound (and therefore 117 max inbound connections). |
| 7 | +which are outbound. You can therefore, have at most 117 inbound connections. |
8 | 8 |
|
9 | 9 | The default settings can result in relatively significant traffic consumption.
|
10 | 10 |
|
11 |
| - |
12 | 11 | Ways to reduce traffic:
|
13 | 12 |
|
14 |
| -1. Use `-maxuploadtarget=<MiB per day>` |
| 13 | +## 1. Use `-maxuploadtarget=<MiB per day>` |
15 | 14 |
|
16 |
| -A major part of the traffic is caused by serving historic blocks to other nodes |
17 |
| -in initial blocks download state (syncing up a new node). |
| 15 | +A major component of the traffic is caused by serving historic blocks to other nodes |
| 16 | +during the initial blocks download phase (syncing up a new node). |
18 | 17 | This option can be specified in MiB per day and is turned off by default.
|
19 |
| -This is *not* a hard limit but a threshold to minimize the outbound |
20 |
| -traffic. When the limit is about to be reached, the uploaded data is cut by not |
21 |
| -serving historic blocks (blocks older than one week). |
| 18 | +This is *not* a hard limit; only a threshold to minimize the outbound |
| 19 | +traffic. When the limit is about to be reached, the uploaded data is cut by no |
| 20 | +longer serving historic blocks (blocks older than one week). |
22 | 21 | Keep in mind that new nodes require other nodes that are willing to serve
|
23 | 22 | historic blocks. **The recommended minimum is 144 blocks per day (max. 144MB
|
24 | 23 | per day)**
|
25 | 24 |
|
26 |
| -2. Disable "listening" (`-listen=0`) |
| 25 | +## 2. Disable "listening" (`-listen=0`) |
27 | 26 |
|
28 |
| -Disable listening will result in fewer nodes connected (remind the max of 8 |
29 |
| -outbound peers). Fewer nodes will result in less traffic usage because relaying |
30 |
| -blocks and transaction needs to be passed to fewer nodes. |
| 27 | +Disabling listening will result in fewer nodes connected (remember the maximum of 8 |
| 28 | +outbound peers). Fewer nodes will result in less traffic usage as you are relaying |
| 29 | +blocks and transactions to fewer nodes. |
31 | 30 |
|
32 |
| -3. Reduce maximal connections (`-maxconnections=<num>`) |
| 31 | +## 3. Reduce maximum connections (`-maxconnections=<num>`) |
33 | 32 |
|
34 |
| -Reducing the connected nodes to a miniumum can be desired in case traffic |
35 |
| -limits are tiny. Keep in mind that bitcoin trustless model works best if you are |
36 |
| -connected to a handfull of nodes. |
| 33 | +Reducing the maximum connected nodes to a miniumum could be desirable if traffic |
| 34 | +limits are tiny. Keep in mind that bitcoin's trustless model works best if you are |
| 35 | +connected to a handful of nodes. |
0 commit comments