Skip to content

Commit 42bae94

Browse files
fanquakejonasschnelli
authored andcommitted
[doc] Improve lanaguge in reducetraffic.md
1 parent 6a776fa commit 42bae94

File tree

1 file changed

+17
-18
lines changed

1 file changed

+17
-18
lines changed

doc/reducetraffic.md

Lines changed: 17 additions & 18 deletions
Original file line numberDiff line numberDiff line change
@@ -1,36 +1,35 @@
1-
REDUCE TRAFFIC
1+
Reduce Traffic
22
==============
33

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.
55

66
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.
88

99
The default settings can result in relatively significant traffic consumption.
1010

11-
1211
Ways to reduce traffic:
1312

14-
1. Use `-maxuploadtarget=<MiB per day>`
13+
## 1. Use `-maxuploadtarget=<MiB per day>`
1514

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).
1817
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).
2221
Keep in mind that new nodes require other nodes that are willing to serve
2322
historic blocks. **The recommended minimum is 144 blocks per day (max. 144MB
2423
per day)**
2524

26-
2. Disable "listening" (`-listen=0`)
25+
## 2. Disable "listening" (`-listen=0`)
2726

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.
3130

32-
3. Reduce maximal connections (`-maxconnections=<num>`)
31+
## 3. Reduce maximum connections (`-maxconnections=<num>`)
3332

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

Comments
 (0)