Bitcoind config rpc

configuration file for the Bitcoin #Fullnode Project: Not (Just) Made In JSON-RPC options (for controlling a running bitcoin-qt/bitcoind process).
Table of contents

Local perspective of time may be influenced by peers forward or backward by this amount.

- - AUR Package Repositories

Incoming connections are not affected by this option. This option can be specified multiple times to allow multiple networks. Use [host]:port notation for IPv6. Allowed permissions are bloomfilter allow requesting BIP37 filtered blocks and transactions , noban do not ban for misbehavior , forcerelay relay transactions that are already in the mempool; implies relay , relay relay even in -blocksonly mode , and mempool allow requesting BIP35 mempool contents.

Specify multiple permissions separated by commas default: noban,mempool,relay. Can be specified multiple times. Uses same permissions as -whitebind.

Wallet options: -addresstype What type of addresses to use "legacy", "p2sh-segwit", or "bech32", default: "bech32" -avoidpartialspends Group outputs by address, selecting all or none, instead of selecting on a per-output basis. Warning: Smaller sizes may increase the risk of losing funds when restoring from an old backup, if none of the addresses in the original keypool have been used. Can be specified multiple times to load multiple wallets. To disable logging to file, set -nodebuglogfile -shrinkdebugfile Shrink debug. Allowed values: main, test, regtest -testnet Use the test chain.

Recommended bitcoin.conf file for resource control

Raw Blame. Lines beginning with are comments. Network-related settings: Note that if you use testnet, signet or regtest, particularly with the options addnode, connect, port, bind, rpcport, rpcbind or wallet, you will also want to read "[Sections]" further down.

In addition it will tell the other nodes connected to it that you exist so they can connect to you. So if you're behind a firewall, or have other problems finding nodes, add some using 'addnode'. If you want to stay private, use 'connect' to only connect to "trusted" nodes. If you run multiple nodes on a LAN, there's no need for all of them to open lots of connections.

Instead 'connect' them all to one node that is port forwarded and has lots of connections. Thanks goes to [Noodle] on Freenode. Refer to the manpage or bitcoind -help for further details. This option is typically used when the server and client are run as the same user.

New user documentation

If not present, those files will be created as new. This setting is over-ridden by the -paytxfee option.


  • Bitcoin Core version released!
  • Your Answer?
  • API reference (JSON-RPC).
  • Enable the RPC JSON API with password authentication in Bitcoin Core!
  • bitcoin countervalue.
  • ani btc.

This mode is incompatible with -txindex and -rescan. If you want to confine an option to just one network, you should add it in the relevant section below. Options only for mainnet [main] Options only for testnet [test] Options only for signet [signet] Options only for regtest [regtest] Copy lines Copy permalink View git blame Reference in new issue. You should also make the bitcoin. On Linux, Mac OSX, and other Unix-like systems, this can be accomplished by running the following command in the Bitcoin application directory:.

Errors or suggestions related to documentation on Bitcoin. If you hover your mouse over a paragraph, cross-reference links will be shown in blue. If you hover over a cross-reference link, a brief definition of the term will be displayed in a tooltip.