-
Notifications
You must be signed in to change notification settings - Fork 66
Node Settings
The following node settings are implemented in the libbitcoin-node and exposed in both Bitcoin Node (BN) and Bitcoin Server (BS).
[node]
# The time period for block polling after initial block download, defaults to 1 (0 disables).
block_poll_seconds = 1
# The minimum fee per byte required for transaction acceptance, defaults to 1.
minimum_byte_fee_satoshis = 1
# Request that peers relay transactions, defaults to true.
relay_transactions = true
# Request transactions on each channel start, defaults to true.
refresh_transactions = true
See initial block download efficiency and why and configuring polling.
This controls both the limit accepted by the node and the relay level requested of its peers, to the extent supported. Any floating point value is valid. Setting this to 0 exposes the node to a low cost disk exhaustion attack.
Requests that peers relay unconfirmed transactions. This should be disabled during initial block download. This is not supported at protocol levels below 70001. Additionally this support varies somewhat due to an incorrect initial implementation by the satoshi client, which was poorly documented and cloned by various forks.
This causes the node to request the mempool of each capable peer upon connection. This is automatically disabled when relay_transactions
is false. This can help warm up the transaction pool quickly. Since the transaction pool is just the disk-based transaction store the node can be restarted with this setting disabled (immediately after warming up the pool), at which point the pool should remain primed.
Users | Developers | License | Copyright © 2011-2024 libbitcoin developers
- Home
- Build Server
- Download Server
- Frequently Asked Questions
- General Information
- Client Server Interface
- Configuration Settings
- Tutorials