2015-07-28 11:11:20 -07:00
|
|
|
(note: this is a temporary file, to be added-to by anybody, and moved to
|
|
|
|
release-notes at release time)
|
|
|
|
|
|
|
|
Notable changes
|
|
|
|
===============
|
|
|
|
|
2015-11-05 15:01:51 -08:00
|
|
|
Reduce upload traffic
|
|
|
|
---------------------
|
|
|
|
|
|
|
|
A major part of the outbound traffic is caused by serving historic blocks to
|
|
|
|
other nodes in initial block download state.
|
|
|
|
|
|
|
|
It is now possible to reduce the total upload traffic via the `-maxuploadtarget`
|
|
|
|
parameter. This is *not* a hard limit but a threshold to minimize the outbound
|
|
|
|
traffic. When the limit is about to be reached, the uploaded data is cut by not
|
|
|
|
serving historic blocks (blocks older than one week).
|
|
|
|
Moreover, any SPV peer is disconnected when they request a filtered block.
|
|
|
|
|
|
|
|
This option can be specified in MiB per day and is turned off by default
|
|
|
|
(`-maxuploadtarget=0`).
|
2015-11-12 04:14:54 -08:00
|
|
|
The recommended minimum is 1152 * MAX_BLOCK_SIZE (currently 2304MB) per day.
|
2015-11-05 15:01:51 -08:00
|
|
|
|
2015-11-13 12:10:51 -08:00
|
|
|
Whitelisted peers will never be disconnected, although their traffic counts for
|
|
|
|
calculating the target.
|
|
|
|
|
2015-11-05 15:01:51 -08:00
|
|
|
A more detailed documentation about keeping traffic low can be found in
|
|
|
|
[/doc/reducetraffic.md](/doc/reducetraffic.md).
|