Arch manual pages

Package containing this man page: community/bitcoin-daemon (version

BITCOIND(1) User Commands BITCOIND(1)


bitcoind - manual page for bitcoind v0.15.0.1


Bitcoin Core Daemon version v0.15.0.1-dirty


bitcoind [options]
Start Bitcoin Core Daemon


Print this help message and exit
Print version and exit
Execute command when a relevant alert is received or we see a really long fork (%s in cmd is replaced by message)
Execute command when the best block changes (%s in cmd is replaced by block hash)
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: 0000000000000000003b9ce759c2a087d52abc4266f8f4ebd6d768b89defa50a, testnet: 0000000002e9e7b00e1f6dc5123a04aad68dd0f0968d8c7aa45f6640795c37b1)
Specify configuration file (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)
Imports blocks from external blk000??.dat file on startup
Keep at most <n> unconnectable transactions in memory (default: 100)
Keep the transaction memory pool below <n> megabytes (default: 300)
Do not keep transactions in the mempool longer than <n> hours (default: 336)
Whether to save the mempool on shutdown and load on restart (default: 1)
Extra transactions to keep in memory for compact block reconstructions (default: 100)
Set the number of script verification threads (-6 to 16, 0 = auto, <0 = leave that many cores free, default: 0)
Specify pid file (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 from the currently indexed blocks
Rebuild chain state and block index from the blk*.dat files on disk
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)
Connection options:
Add a node to connect to and attempt to keep the connection open
Threshold for disconnecting misbehaving peers (default: 100)
Number of seconds to keep misbehaving peers from reconnecting (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
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)
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)
Use separate SOCKS5 proxy to reach peers via Tor hidden services (default: -proxy)
Only connect to nodes in network <net> (ipv4, ipv6 or onion)
Relay non-P2SH multisig (default: 1)
Support filtering of blocks and transaction with bloom filters (default: 1)
Listen for connections on <port> (default: 8333 or testnet: 18333)
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
Tries to keep outbound traffic under the given target (in MiB per 24h), 0 = no limit (default: 0)
Wallet options:
Do not load the wallet and disable wallet RPC calls
Set key pool size to <n> (default: 1000)
A fee rate (in BTC/kB) that will be used when fee estimation has insufficient data (default: 0.0002)
The fee rate (in BTC/kB) that indicates your tolerance for discarding change by adding it to the fee (default: 0.0001). Note: An output is discarded if it is dust at this rate, but we will always discard up to the dust relay fee and a discard fee above that is limited by the fee estimate for the longest target
Fees (in BTC/kB) smaller than this are considered zero fee for transaction creation (default: 0.00001)
Fee (in BTC/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)
If paytxfee is not set, include enough fee so transactions begin confirmation on average within n blocks (default: 6)
Use hierarchical deterministic key generation (HD) after BIP32. Only has effect during wallet creation/first start (default: 1)
Send transactions with full-RBF opt-in enabled (default: 0)
Upgrade wallet to latest format on startup
Specify wallet file (within data directory) (default: wallet.dat)
Make the wallet broadcast transactions (default: 1)
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. account owner and payment request information, 2 = drop tx meta data)
ZeroMQ notification options:
Enable publish hash block in <address>
Enable publish hash transaction in <address>
Enable publish raw block in <address>
Enable publish raw transaction in <address>
Debugging/Testing options:
Append comment to the user agent string
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.
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.
Show all debugging options (usage: --help -help-debug)
Include IP addresses in debug output (default: 0)
Prepend debug output with timestamp (default: 1)
Maximum total fees (in BTC) 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
Shrink debug.log file on client startup (default: 1 when no -debug)
Chain selection options:
Use the test chain
Node relay options:
Equivalent bytes per sigop in transactions for relay and mining (default: 20)
Relay and mine data carrier transactions (default: 1)
Maximum size of data in data carrier transactions we relay and mine (default: 83)
Enable transaction replacement in the memory pool (default: 1)
Fees (in BTC/kB) smaller than this are considered zero fee for relaying, mining and transaction creation (default: 0.00001)
Accept relayed transactions received from whitelisted peers even when not relaying transactions (default: 1)
Force relay of transactions from whitelisted peers even if they violate local relay policy (default: 1)
Block creation options:
Set maximum BIP141 block weight (default: 3000000)
Set maximum block size in bytes (default: 750000)
Set lowest fee rate (in BTC/kB) for transactions to be included in block creation. (default: 0.00001)
RPC server options:
Accept command line and JSON-RPC commands
Accept public REST requests (default: 0)
Bind to given address to listen for JSON-RPC connections. 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, or if -rpcallowip has been specified, and :: i.e., all addresses)
Location of the auth cookie (default: data dir)
Username for JSON-RPC connections
Password for JSON-RPC connections
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/rpcuser. The client then connects normally using the rpcuser=<USERNAME>/rpcpassword=<PASSWORD> pair of arguments. This option can be specified multiple times
Listen for JSON-RPC connections on <port> (default: 8332 or testnet: 18332)
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
Sets the serialization of raw transaction or block hex returned in non-verbose mode, non-segwit(0) or segwit(1) (default: 1)
Set the number of threads to service RPC calls (default: 4)


Copyright (C) 2009-2017 The Bitcoin Core developers
Please contribute if you find Bitcoin Core 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.
September 2017 bitcoind v0.15.0.1