NodeGuide / Optional reference / Policy Settings
Policy Settings Reference Guide
Scroll down to see entire page
Quick definitions appear when you tap technical terms during setup. This optional guide gives you more help with setup, settings, and troubleshooting.
Safety wording reviewed September 23, 2026. Reference instructions may differ by device, app and installed software version; NodeGuide does not detect your version. Check the current official instructions before making a change.
Before changing network or policy settings, record the current values and check your installed version’s official guide. A wrong change can block access or transaction relay. Never put RPC or an admin dashboard on the public internet.
Bitcoin network rules vs your node’s preferences
Bitcoin’s network rules decide which transactions and blocks are valid. Your node’s policy settings decide which unconfirmed transactions it accepts and shares.
Which transactions your node shares
These settings control which unconfirmed transactions your node shares with other Bitcoin nodes. Most beginners can leave the default settings unchanged.
Standard or stricter transaction sharing
Standard settings work with the widest range of transactions. Stricter settings may prevent your node from sharing some transactions that are still valid on Bitcoin.
Transactions that include extra data
Some Bitcoin transactions include extra information that is not a payment. This setting controls whether your node shares some of those transactions with other nodes.
Older multisignature transactions
This setting affects whether your node shares certain older multisignature transaction types. Most beginners do not need to change it.
Replace-by-fee policy
Replace-by-fee allows some unconfirmed transactions to be replaced by a newer version that pays a higher fee. This is commonly used when someone needs to speed up an unconfirmed transaction by paying a higher fee.
Lowest fee your node will normally share
This is the lowest transaction fee your node normally requires before it will share a transaction with other nodes. Most beginners can leave the default setting unchanged.
How your node handles waiting transactions
These settings control which unconfirmed transactions your node keeps, how much space they can use, and which ones your node shares with other nodes.
Why different nodes can use different policies
Different Bitcoin nodes can make different local policy choices and still follow the same Bitcoin consensus rules.
Common policy-setting troubleshooting
If transactions are not being accepted or shared as expected, first check your mempool and transaction-sharing settings. Change one setting at a time. Avoid advanced changes unless you understand what they do.