bitcoind - manual page for bitcoind v0.22.3


bitcoind [options] Start Bitcoin ABC Daemon


Bitcoin ABC Daemon version v0.22.3



Print this help message and exit


Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message)


If this block is in the chain assume that it and its ancestors are valid and potentially skip their script verification (0 to verify all, default: 000000000000000002294a0be3e78d58b70808bfe338008ff6d98b96326237fd, testnet: 000000000013b28316976684300dc00be5a2b3e9ce3369ac621fcf422a5f84f0)


Maintain an index of compact filters by block (default: 0, values: basic). If <type> is not supplied or if <type> = 1, indexes for all known types are enabled.


Execute command when the best block changes (%s in cmd is replaced by block hash)


Extra transactions to keep in memory for compact block reconstructions (default: 100)


Specify directory to hold blocks subdirectory for *.dat files (default: <datadir>)


Whether to reject transactions from network peers. Transactions from the wallet or RPC are not affected. (default: 0)


Specify configuration file. Relative paths will be prefixed by datadir location. (default: bitcoin.conf)


Run in the background as a daemon and accept commands


Specify data directory


Set database cache size in megabytes (4 to 16384, default: 450)


Specify location of debug log file. Relative paths will be prefixed by a net-specific datadir location. (0 to disable; default: debug.log)


Set the minimum amount of time to wait between a block header reception and the block finalization. Unit is seconds (default: 7200)


Specify additional configuration file, relative to the -datadir path (only useable from configuration file, not command line)


Imports blocks from external blk000??.dat file on startup


Keep the transaction memory pool below <n> megabytes (default: 300)


Keep at most <n> unconnectable transactions in memory (default: 100)


Configure at what depth blocks are considered final (default: 10). Use -1 to disable.


Do not keep transactions in the mempool longer than <n> hours (default: 336)


Set the number of script verification threads (-4 to 15, 0 = auto, <0 = leave that many cores free, default: 0)


Whether to save the mempool on shutdown and load on restart (default: 1)


Specify pid file. Relative paths will be prefixed by a net-specific datadir location. (default:


Reduce storage requirements by enabling pruning (deleting) of old blocks. This allows the pruneblockchain RPC to be called to delete specific blocks, and enables automatic pruning of old blocks if a target size in MiB is provided. This mode is incompatible with -txindex and -rescan. Warning: Reverting this setting requires re-downloading the entire blockchain. (default: 0 = disable pruning blocks, 1 = allow manual pruning via RPC, >=550 = automatically prune block files to stay under the specified target size in MiB)


Rebuild chain state and block index from the blk*.dat files on disk


Rebuild chain state from the currently indexed blocks. When in pruning mode or if blocks on disk might be corrupted, use full -reindex instead.


Create new files with system default permissions, instead of umask 077 (only effective with disabled wallet functionality)


Maintain a full transaction index, used by the getrawtransaction rpc call (default: 0)


Use Cash Address for destination encoding instead of base58 (activate by default on Jan, 14)


Print version and exit

Connection options:


Add a node to connect to and attempt to keep the connection open (see the `addnode` RPC command help for more info)


Threshold for disconnecting and discouraging misbehaving peers (default: 100)


Default duration (in seconds) of manually configured bans (default: 86400)


Bind to given address and always listen on it. Use [host]:port notation for IPv6


Connect only to the specified node(s); -connect=0 disables automatic connections (the rules for this peer are the same as for -addnode)


Discover own IP addresses (default: 1 when listening and no -externalip or -proxy)


Allow DNS lookups for -addnode, -seednode and -connect (default: 1)


Query for peer addresses via DNS lookup, if low on addresses (default: 1 unless -connect used)


Send reject messages per BIP61 (default: 0)


Specify your own public address


Always query for peer addresses via DNS lookup (default: 0)


Accept connections from outside (default: 1 if no -proxy or -connect)


Automatically create Tor hidden service (default: 1)


Maintain at most <n> connections to peers (default: 125)


Maximum per-connection receive buffer, <n>*1000 bytes (default: 5000)


Maximum per-connection send buffer, <n>*1000 bytes (default: 1000)


Maximum allowed median peer time offset adjustment. Local perspective of time may be influenced by peers forward or backward by this amount. (default: 4200 seconds)


Tries to keep outbound traffic under the given target (in MiB per 24h), 0 = no limit (default: 0)


Use separate SOCKS5 proxy to reach peers via Tor hidden services (default: -proxy)


Make outgoing connections only through network <net> (ipv4, ipv6 or onion). Incoming connections are not affected by this option. This option can be specified multiple times to allow multiple networks.


Support filtering of blocks and transaction with bloom filters (default: 1)


Specify p2p connection timeout in seconds. This option determines the amount of time a peer may be inactive before the connection to it is dropped. (minimum: 1, default: 60)


Relay non-P2SH multisig (default: 1)


Listen for connections on <port> (default: 8333, testnet: 18333, regtest: 18444)


Connect through SOCKS5 proxy


Randomize credentials for every proxy connection. This enables Tor stream isolation (default: 1)


Connect to a node to retrieve peer addresses, and disconnect


Specify connection timeout in milliseconds (minimum: 1, default: 5000)


Tor control port to use if onion listening enabled (default:


Tor control port password (default: empty)


Use UPnP to map the listening port (default: 0)


Bind to given address and whitelist peers connecting to it. Use [host]:port notation for IPv6

-whitelist=<IP address or network>

Whitelist peers connecting from the given IP address (e.g. or CIDR notated network (e.g. Can be specified multiple times. Whitelisted peers cannot be DoS banned and their transactions are always relayed, even if they are already in the mempool, useful e.g. for a gateway

Wallet options:


Group outputs by address, selecting all or none, instead of selecting on a per-output basis. Privacy is improved as an address is only used once (unless someone sends to it after spending from it), but may result in slightly higher fees as suboptimal coin selection may result due to the added limitation (default: 0 (always enabled for wallets with "avoid_reuse" enabled))


Do not load the wallet and disable wallet RPC calls


A fee rate (in BCH/kB) that will be used when fee estimation has insufficient data. 0 to entirely disable the fallbackfee feature. (default: 0.00)


Set key pool size to <n> (default: 1000)


Fees (in BCH/kB) smaller than this are considered zero fee for transaction creation (default: 0.00001)


Fee (in BCH/kB) to add to transactions you send (default: 0.00)


Rescan the block chain for missing wallet transactions on startup


Attempt to recover private keys from a corrupt wallet on startup


Spend unconfirmed change when sending transactions (default: 1)


Upgrade wallet to latest format on startup


Specify wallet database path. Can be specified multiple times to load multiple wallets. Path is interpreted relative to <walletdir> if it is not absolute, and will be created if it does not exist (as a directory containing a wallet.dat file and log files). For backwards compatibility this will also accept names of existing data files in <walletdir>.)


Make the wallet broadcast transactions (default: 1)


Specify directory to hold wallets (default: <datadir>/wallets if it exists, otherwise <datadir>)


Execute command when a wallet transaction changes (%s in cmd is replaced by TxID)


Delete all wallet transactions and only recover those parts of the blockchain through -rescan on startup (1 = keep tx meta data e.g. payment request information, 2 = drop tx meta data)

ZeroMQ notification options:


Enable publish hash block in <address>


Set publish hash block outbound message high water mark (default: 1000)


Enable publish hash transaction in <address>


Set publish hash transaction outbound message high water mark (default: 1000)


Enable publish raw block in <address>


Set publish raw block outbound message high water mark (default: 1000)


Enable publish raw transaction in <address>


Set publish raw transaction outbound message high water mark (default: 1000)

Debugging/Testing options:


Output debugging information (default: 0, supplying <category> is optional). If <category> is not supplied or if <category> = 1, output all debugging information.<category> can be: net, tor, mempool, http, bench, zmq, db, rpc, estimatefee, addrman, selectcoins, reindex, cmpctblock, rand, prune, proxy, mempoolrej, libevent, coindb, qt, leveldb, validation.


Exclude debugging information for a category. Can be used in conjunction with -debug=1 to output debug logs for all categories except one or more specified categories.


Print help message with debugging options and exit


Include IP addresses in debug output (default: 0)


Prepend debug output with name of the originating thread (only available on platforms supporting thread_local) (default: 0)


Prepend debug output with timestamp (default: 1)


Maximum total fees (in BCH) to use in a single wallet transaction or raw transaction; setting this too low may abort large transactions (default: 0.10)


Send trace/debug info to console instead of debug.log file (default: 1 when no -daemon. To disable logging to file, set debuglogfile=0)


Shrink debug.log file on client startup (default: 1 when no -debug)


Append comment to the user agent string

Chain selection options:


Use the chain <chain> (default: main). Allowed values: main, test, regtest


Use the test chain. Equivalent to -chain=test.

Node relay options:


Equivalent bytes per sigop in transactions for relay and mining (default: 50)


Relay and mine data carrier transactions (default: 1)


Maximum size of data in data carrier transactions we relay and mine (default: 223)


Fees (in BCH/kB) smaller than this are rejected for relaying, mining and transaction creation (default: 0.00001)


Force relay of transactions from whitelisted peers even if they violate local relay policy (default: 0)


Accept relayed transactions received from whitelisted peers even when not relaying transactions (default: 1)

Block creation options:


Set maximum block size in bytes (default: 2000000)


Set lowest fee rate (in BCH/kB) for transactions to be included in block creation. (default: 0.00001)

RPC server options:


Accept public REST requests (default: 0)


Allow JSON-RPC connections from specified source. Valid for <ip> are a single IP (e.g., a network/netmask (e.g. or a network/CIDR (e.g. This option can be specified multiple times


Username and hashed password for JSON-RPC connections. The field <userpw> comes in the format: <USERNAME>:<SALT>$<HASH>. A canonical python script is included in share/rpcauth. The client then connects normally using the rpcuser=<USERNAME>/rpcpassword=<PASSWORD> pair of arguments. This option can be specified multiple times


Bind to given address to listen for JSON-RPC connections. Do not expose the RPC server to untrusted networks such as the public internet! This option is ignored unless -rpcallowip is also passed. Port is optional and overrides -rpcport. Use [host]:port notation for IPv6. This option can be specified multiple times (default: and ::1 i.e., localhost)


Location of the auth cookie. Relative paths will be prefixed by a net-specific datadir location. (default: data dir)


Domain from which to accept cross origin requests (browser enforced)


Password for JSON-RPC connections


Listen for JSON-RPC connections on <port> (default: 8332, testnet: 18332, regtest: 18443)


Set the number of threads to service RPC calls (default: 4)


Username for JSON-RPC connections


Set a whitelist to filter incoming RPC calls for a specific user. The field <whitelist> comes in the format: <USERNAME>:<rpc 1>,<rpc 2>,...,<rpc n>. If multiple whitelists are set for a given user, they are set-intersected. See -rpcwhitelistdefault documentation for information on default whitelist behavior.


Sets default behavior for rpc whitelisting. Unless rpcwhitelistdefault is set to 0, if any -rpcwhitelist is set, the rpc server acts as if all rpc users are subject to empty-unless-otherwise-specified whitelists. If rpcwhitelistdefault is set to 1 and no -rpcwhitelist is set, rpc server acts as if all rpc users are subject to empty whitelists.


Accept command line and JSON-RPC commands


Copyright (C) 2009-2020 The Bitcoin developers

Please contribute if you find Bitcoin ABC useful. Visit <> for further information about the software. The source code is available from <>.

This is experimental software. Distributed under the MIT software license, see the accompanying file COPYING or <>

This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit <> and cryptographic software written by Eric Young and UPnP software written by Thomas Bernard.