aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorapitko <81133459+apitko@users.noreply.github.com>2021-03-21 22:42:14 -0700
committerJarol Rodriguez <jarolrod@tutanota.com>2021-05-28 12:53:17 -0400
commit947f9734daab4e47c0abdc6ef7d52812102ecb6b (patch)
tree22ed5b36388fa682e3e3f1b082674883dde31269
parent5c041cb348e667672c8b5ed504dba05adf60783b (diff)
downloadbitcoin-947f9734daab4e47c0abdc6ef7d52812102ecb6b.tar.xz
doc: add maxuploadtarget to bitcoin.conf example
Introduce the maxuploadtarget option to the example bitcoin.conf file. This adds visibility for this option which is useful to those looking to configure bandwidth usage.
-rw-r--r--share/examples/bitcoin.conf6
1 files changed, 6 insertions, 0 deletions
diff --git a/share/examples/bitcoin.conf b/share/examples/bitcoin.conf
index 318b48bf2e..4a947001fa 100644
--- a/share/examples/bitcoin.conf
+++ b/share/examples/bitcoin.conf
@@ -71,6 +71,12 @@
# configuration option or the addnode RPC, which have a separate limit of 8 connections.
#maxconnections=
+# Maximum upload bandwidth target in MiB per day (e.g. 'maxuploadtarget=1024' is 1 GiB per day).
+# This limits the upload bandwidth for those with bandwidth limits. 0 = no limit (default: 0).
+# -maxuploadtarget does not apply to peers with 'download' permission.
+# For more information on reducing bandwidth utilization, see: doc/reduce-traffic.md.
+#maxuploadtarget=
+
#
# JSON-RPC options (for controlling a running Bitcoin/bitcoind process)
#