mirror of
https://github.com/dashpay/dash.git
synced 2024-12-26 04:22:55 +01:00
68cecee558
fa6e01f2a163511a735088895ab02232b150801b doc: block-relay-only is not blocksonly (MarcoFalke) Pull request description: Those are different concepts, see https://github.com/bitcoin/bitcoin/blob/master/doc/release-notes/release-notes-0.19.0.1.md#p2p-changes for the block-relay-only nodes. ACKs for top commit: jonatack: ACK fa6e01f hebasto: ACK fa6e01f2a163511a735088895ab02232b150801b Tree-SHA512: 6de2c81201b62ed59e504a3a6f164068600182e1bbf63eda7f9db3160507bdba091c13882ee0e75e713f0832bfaf5973a86eba3b94588d5b72196f05ae0a9c9a
57 lines
2.4 KiB
Markdown
57 lines
2.4 KiB
Markdown
Reduce Traffic
|
|
==============
|
|
|
|
Some node operators need to deal with bandwidth caps imposed by their ISPs.
|
|
|
|
By default, Dash Core allows up to 125 connections to different peers, 10 of
|
|
which are outbound. You can therefore, have at most 115 inbound connections.
|
|
Of the 10 outbound peers, there can be 8 full-relay connections and 2
|
|
block-relay-only ones.
|
|
|
|
The default settings can result in relatively significant traffic consumption.
|
|
|
|
Ways to reduce traffic:
|
|
|
|
## 1. Use `-maxuploadtarget=<MiB per day>`
|
|
|
|
A major component of the traffic is caused by serving historic blocks to other nodes
|
|
during the initial blocks download phase (syncing up a new node).
|
|
This option can be specified in MiB per day and is turned off by default.
|
|
This is *not* a hard limit; only a threshold to minimize the outbound
|
|
traffic. When the limit is about to be reached, the uploaded data is cut by no
|
|
longer serving historic blocks (blocks older than one week).
|
|
Keep in mind that new nodes require other nodes that are willing to serve
|
|
historic blocks.
|
|
|
|
Whitelisted peers will never be disconnected, although their traffic counts for
|
|
calculating the target.
|
|
|
|
## 2. Disable "listening" (`-listen=0`)
|
|
|
|
Disabling listening will result in fewer nodes connected (remember the maximum of 10
|
|
outbound peers). Fewer nodes will result in less traffic usage as you are relaying
|
|
blocks and transactions to fewer nodes.
|
|
|
|
## 3. Reduce maximum connections (`-maxconnections=<num>`)
|
|
|
|
Reducing the maximum connected nodes to a minimum could be desirable if traffic
|
|
limits are tiny. Keep in mind that dash's trustless model works best if you are
|
|
connected to a handful of nodes.
|
|
|
|
## 4. Turn off transaction relay (`-blocksonly`)
|
|
|
|
Forwarding transactions to peers increases the P2P traffic. To only sync blocks
|
|
with other peers, you can disable transaction relay.
|
|
|
|
Be reminded of the effects of this setting.
|
|
|
|
- Fee estimation will no longer work.
|
|
- It sets the flag "-walletbroadcast" to be "0", only if it is currently unset.
|
|
Doing so disables the automatic broadcasting of transactions from wallet. Not
|
|
relaying other's transactions could hurt your privacy if used while a wallet
|
|
is loaded or if you use the node to broadcast transactions.
|
|
- If a peer is whitelisted and "-whitelistforcerelay" is set to "1" (which will
|
|
also set "whitelistrelay" to "1"), we will still receive and relay their transactions.
|
|
- It makes block propagation slower because compact block relay can only be
|
|
used when transaction relay is enabled.
|