We have seen node operators shutting down nodes because of traffic exceeding. Reducing traffic is possible with different measures and therefore very likely a "communication problem". This documentation might help those who like to or need to reduce traffic.
Thanks @fanquake for the overhaul!
Release notes for maxuploadtarget is handled over #6958.
Looks good. Concept ACK
0 | @@ -0,0 +1,35 @@ 1 | +REDUCE TRAFFIC
Nit: No CAPSLOCK
20 | +longer serving historic blocks (blocks older than one week). 21 | +Keep in mind that new nodes require other nodes that are willing to serve 22 | +historic blocks. **The recommended minimum is 144 blocks per day (max. 144MB 23 | +per day)** 24 | + 25 | +2. Disable "listening" (`-listen=0`)
Nit: .md will convert this to 1.. Use subsections?
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). 21 | +Keep in mind that new nodes require other nodes that are willing to serve 22 | +historic blocks. **The recommended minimum is 144 blocks per day (max. 144MB 23 | +per day)**
Nit: Don't overuse bold. Make only a single word bold?
Fixed @MarcoFalke's nits. The bold test part is okay IMO.
30 | + 31 | +## 3. Reduce maximum connections (`-maxconnections=<num>`) 32 | + 33 | +Reducing the maximum connected nodes to a miniumum could be desirable if traffic 34 | +limits are tiny. Keep in mind that bitcoins trustless model works best if you are 35 | +connected to a handfull of nodes.
Thanks! Force-Push fixed.
ACK
utACK
ACK.
(Nit: I don't like the use of the passive voice; for example "Reducing the maximum connected nodes to a miniumum could be desirable" would be clearer as "Set -maxconnections=1 for minimal bandwidth usage" ... but I think this is good enough to pull as-is).