NAMECOIN(1)

📦 version 32.0, in nixpkgs unstable

🌸 NAMECOIN(1) — General Commands Manual 🌸

okay so bestie, this is the NAMECOIN(1) page and it's filed under General Commands Manual — but the tea is that the NAME line literally reads namecoin - manual page for namecoin =======, because this file has a whole merge-conflict fossil in it (<<<<<<< HEAD:doc/man/namecoin.1 … =======). Then the bitcoind manual shows up wearing its own NAMECOIN(1) / BITCOIND(1) — User Commands header. We're keeping every crumb, no cap. 💅

🎀 NAME 🎀

namecoin — manual page for namecoin

👑 BITCOIND(1) — User Commands 👑

💖 NAME 💖

bitcoind — manual page for bitcoind v32.0.0

📜 SYNOPSIS 📜

bitcoind [options]

🌟 DESCRIPTION 🌟

Version check, bestie: Bitcoin Core daemon version v32.0.0 bitcoind.

The Bitcoin Core daemon (bitcoind) is a headless program that connects to the Bitcoin network to validate and relay transactions and blocks, as well as relaying addresses. It's literally the backbone of the Bitcoin network, and its RPC, REST, and ZMQ services can provide various transaction, block, and address-related services. There's also an optional wallet component that provides transaction services. It can be used in a headless environment or as part of a server setup. Periodt. ✨

✨ OPTIONS ✨

  • -alertnotify=<cmd> — run a command when an alert is raised; %s in the command gets replaced by the message. 🚨
  • -allowignoredconf — for backwards compatibility, treat an unused bitcoin.conf file in the datadir as a warning, not an error. 🫶
  • -assumevalid=<hex> — 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: 00000000000000000000748969ec33043c0e52a763c6dd5193861f559f2c72e3, testnet3: 00000000b318a3703d14a844c55ef507f4c2fc8f8766e24271fd43c180c51637, testnet4: 0000000021df65b91665a342e26ceb05e54826ad7d8fcd40316230058fa3b865, signet: 00000002a5e0ba0498f1e9f4591af0b66b63c654665efe65206fd0ae7bbaf923. 🧚
  • -blockfilterindex=<type> — maintain an index of compact filters by block (default: 0, values: basic). If <type> isn't supplied or if <type> = 1, indexes for all known types are enabled. 🔍
  • -blocknotify=<cmd> — run a command when the best block changes (%s in the command gets replaced by the block hash). Not run for blocks connected during initial block download or reindexing. 💅
  • -blockreconstructionextratxn=<n> — extra transactions to keep in memory for compact block reconstructions (default: 100). 🧠
  • -blocksdir=<dir> — specify the directory to hold the blocks subdirectory for *.dat files (default: <datadir>). 📁
  • -blocksonly — whether to reject transactions from network peers. This disables automatic broadcast and rebroadcast of transactions unless the source peer has the 'forcerelay' permission. RPC transactions are not affected. (default: 0). 🚫
  • -blocksxor — whether an XOR-key applies to blocksdir *.dat files. The created XOR-key will be zeros for an existing blocksdir or when -blocksxor=0 is set, and random for a freshly initialized blocksdir. (default: 1). 🔐
  • -coinstatsindex — maintain the coinstats index used by the gettxoutsetinfo RPC (default: 0). 📊
  • -conf=<file> — specify the path to a read-only configuration file. Relative paths will be prefixed by the datadir location — and it's only usable from the command line, not from the configuration file. (default: bitcoin.conf). 📝
  • -daemon — run in the background as a daemon and accept commands (default: 0). 👻
  • -daemonwait — wait for initialization to be finished before exiting. This implies -daemon (default: 0). ⏳
  • -datadir=<dir> — specify the data directory. 🗂️
  • -dbcache=<n> — maximum database cache size <n> MiB (minimum 4, default: 1024). Make sure you have enough RAM, bestie. In addition, unused memory allocated to the mempool is shared with this cache (see -maxmempool). 🧠💾
  • -debuglogfile=<file> — specify the location of the debug log file (default: debug.log). Relative paths will be prefixed by a net-specific datadir location. Pass -nodebuglogfile to disable writing the log to a file. 🪵
  • -help — print this help message and exit (also -h or -?). 🙋‍♀️
  • -includeconf=<file> — specify an additional configuration file, relative to the -datadir path (only usable from the configuration file, not the command line). 🧾
  • -loadblock=<file> — imports blocks from an external file on startup. Obfuscated blocks are not supported. 📦
  • -maxmempool=<n> — keep the transaction memory pool below <n> megabytes (default: 300). 🏊
  • -mempoolexpiry=<n> — do not keep transactions in the mempool longer than <n> hours (default: 336). ⌛
  • -par=<n> — set the number of script verification threads (0 = auto, up to 15, <0 = leave that many cores free, default: 0). 🧵
  • -persistmempool — whether to save the mempool on shutdown and load it on restart (default: 1). 💾
  • -persistmempoolv1 — whether a mempool.dat file created by -persistmempool or the savemempool RPC will be written in the legacy format (version 1) or the current format (version 2). This temporary option will be removed in the future. (default: 0). 🕰️
  • -pid=<file> — specify the pid file. Relative paths will be prefixed by a net-specific datadir location. (default: bitcoind.pid). 🪪
  • -prevoutfetchthreads=<n> — set the number of threads used to prefetch block input prevouts from the chainstate database (0 disables, up to 16, default: 8). Negative values are rejected. 🚀
  • -prune=<n> — 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. ⚠️ Warning: reverting this setting requires re-downloading the entire blockchain. Wallets and indexes should be loaded at startup and kept active while pruning is enabled so they stay synchronized before old block data is deleted; wallets or indexes that fall behind pruned data may require a reindex. (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). 🪓
  • -reindex — if enabled, wipe chain state and block index, and rebuild them from blk*.dat files on disk. Also wipe and rebuild other optional indexes that are active. If an assumeutxo snapshot was loaded, its chainstate will be wiped as well. The snapshot can then be reloaded via RPC. 🔁
  • -reindex-chainstate — if enabled, wipe chain state, and rebuild it from blk*.dat files on disk. If an assumeutxo snapshot was loaded, its chainstate will be wiped as well. The snapshot can then be reloaded via RPC. 🔄
  • -settings=<file> — specify the path to the dynamic settings data file. Can be disabled with -nosettings. The file is written at runtime and is not meant to be edited by users (use bitcoin.conf instead for custom settings). Relative paths will be prefixed by the datadir location. (default: settings.json). ⚙️
  • -shutdownnotify=<cmd> — execute a command immediately before beginning shutdown. The need for shutdown may be urgent, so be careful not to delay it long (if the command doesn't require interaction with the server, consider having it fork into the background). 🛑
  • -startupnotify=<cmd> — execute a command on startup. 🎬
  • -txindex — maintain a full transaction index, used by the getrawtransaction rpc call (default: 0). 🔎
  • -txospenderindex — maintain a transaction output spender index, used by the gettxspendingprevout rpc call (default: 0). 💸
  • -version — print version and exit. 🏷️

🔌 Connection options:

  • -addnode=<ip> — add a node to connect to and attempt to keep the connection open (see the addnode RPC help for more info). This option can be specified multiple times to add multiple nodes; connections are limited to 8 at a time and are counted separately from the -maxconnections limit. 🔗
  • -asmap=<file> — specify the asn mapping used for bucketing of the peers. Relative paths will be prefixed by the net-specific datadir location. If a bool arg is given (-asmap or -asmap=1), the embedded mapping data in the binary will be used. 🗺️
  • -bantime=<n> — default duration (in seconds) of manually configured bans (default: 86400). ⏱️
  • -bind=<addr>[:<port>][=onion] — bind to the given address and always listen on it (default: 0.0.0.0). Use [host]:port notation for IPv6. Append =onion to tag any incoming connections to that address and port as incoming Tor connections (default: 127.0.0.1:8334=onion, testnet3: 127.0.0.1:18334=onion, testnet4: 127.0.0.1:48334=onion, signet: 127.0.0.1:38334=onion, regtest: 127.0.0.1:18445=onion). 🧅
  • -cjdnsreachable — if set, then this host is configured for CJDNS (connecting to fc00::/8 addresses would lead us to the CJDNS network, see doc/cjdns.md) (default: 0). 🌐
  • -connect=<ip> — connect only to the specified node; -noconnect disables automatic connections (the rules for this peer are the same as for -addnode). This option can be specified multiple times to connect to multiple nodes. 🎯
  • -discover — discover own IP addresses (default: 1 when listening and no -externalip or -proxy). 🛰️
  • -dns — allow DNS lookups for -addnode, -seednode and -connect (default: 1). 📡
  • -dnsseed — query for peer addresses via DNS lookup, if low on addresses (default: 1 unless -connect used or -maxconnections=0). 🌱
  • -externalip=<ip> — specify your own public address. 🌍
  • -fixedseeds — allow fixed seeds if DNS seeds don't provide peers (default: 1). 🌾
  • -forcednsseed — always query for peer addresses via DNS lookup (default: 0). 📡
  • -i2pacceptincoming — whether to accept inbound I2P connections (default: 1). Ignored if -i2psam is not set. Listening for inbound I2P connections is done through the SAM proxy, not by binding to a local address and port. 🕵️‍♀️
  • -i2psam=<ip:port> — I2P SAM proxy to reach I2P peers and accept I2P connections. 🛰️
  • -inboundrelaypercent=<n> — (the page cuts off right here in part 1 — no description is given yet, bestie). ✂️

Okay, picking up right where we left off: the inbound relay percent limit lets you permit a maximum percent of inbound connections to relay transactions, so memory utilization stays in check (0 to 100, default: 50). It’s basically a vibe check for your node’s memory, bestie. 🫶

  • -listen — Accept connections from outside (default: 1 if no -proxy, -connect or -maxconnections=0). Let the people in, but only under those conditions. 💖
  • -listenonion — Automatically create Tor onion service (default: 1). Onion mode: on, unless you say otherwise. 🧅
  • -maxconnections=<n> — Maintain at most <n> automatic connections to peers (default: 200). 11 slots of these are reserved for outgoing connections. See -inboundrelaypercent for more information about limits applied to transaction relay inbound peers. This limit does not apply to connections manually added via -addnode or the addnode RPC, which have a separate limit of 8. It does not apply to short-lived private broadcast connections either, which have a separate limit of 64. So many little limits, but they all matter. 💀
  • -maxreceivebuffer=<n> — Maximum per-connection receive buffer, <n>*1000 bytes (default: 5000). Buffer boundaries are self-care. ✨
  • -maxsendbuffer=<n> — Maximum per-connection memory usage for the send buffer, <n>*1000 bytes (default: 1000). Another memory ceiling, another slay. 🎀
  • -maxuploadtarget=<n> — Tries to keep outbound traffic under the given target per 24h. Limit does not apply to peers with 'download' permission or blocks created within past week. 0 = no limit (default: 0M). Optional suffix units [k|K|m|M|g|G|t|T] (default: M). Lowercase is 1000 base while uppercase is 1024 base. The capitalization is lowkey important, so don’t sleep on it. 🔥
  • -natpmp — Use PCP or NAT-PMP to map the listening port (default: 1). NAT traversal, but make it cute. 🌸
  • -networkactive — Enable all P2P network activity (default: 1). Can be changed by the setnetworkactive RPC command. The main character switch for networking. 👑
  • -onion=<ip:port|path> — Use separate SOCKS5 proxy to reach peers via Tor onion services, set -noonion to disable (default: -proxy). May be a local file path prefixed with 'unix:'. Onion routing with options, periodt. 🧅
  • -onlynet=<net> — Make automatic outbound connections only to network <net> (ipv4, ipv6, onion, i2p, cjdns). Inbound and manual connections are not affected by this option. It can be specified multiple times to allow multiple networks. Choose your network little fam. 🌈
  • -peerblockfilters — Serve compact block filters to peers per BIP 157 (default: 0). BIP 157 said what it said. ⭐
  • -peerbloomfilters — Support filtering of blocks and transaction with bloom filters (default: 0). Bloom filters, but off by default. 🦋
  • -port=<port> — Listen for connections on <port> (default: 8333, testnet3: 18333, testnet4: 48333, signet: 38333, regtest: 18444). Not relevant for I2P (see doc/i2p.md). If set to a value x, the default onion listening port will be set to x+1. Port math: iconic. 🧮
  • -proxy=<ip>[:<port>]|unix:<path>[=<network>] — Connect through SOCKS5 proxy, set -noproxy to disable. May be a local file path prefixed with 'unix:' if the proxy supports it. Could end in =network to set the proxy only for that network. The network can be any of ipv4, ipv6, tor or cjdns. (default: disabled). Proxy drama, but configurable. 💅
  • -proxyrandomize — Randomize credentials for every proxy connection. This enables Tor stream isolation (default: 1). Randomize the creds, protect the streams. 🙈
  • -seednode=<ip> — Connect to a node to retrieve peer addresses, and disconnect. This option can be specified multiple times to connect to multiple nodes. During startup, seednodes will be tried before dnsseeds. Seednodes first, no cap. 🌱
  • -timeout=<n> — Specify socket connection timeout in milliseconds. If an initial attempt to connect is unsuccessful after this amount of time, drop it (minimum: 1, default: 5000). Don’t wait forever, bestie. ⏳
  • -torcontrol=<ip>:<port> — Tor control host and port to use if onion listening enabled (default: 127.0.0.1:9051). If no port is specified, the default port of 9051 will be used. Tor control, but with defaults doing the most. 🧅
  • -torpassword=<pass> — Tor control port password (default: empty). Keep it empty unless you need it, and keep it secret. 🤫
  • -v2transport — Support v2 transport (default: 1). New transport, new era. 🚀
  • -whitebind=<[permissions@]addr> — Bind to the given address and add permission flags to the peers connecting to it. Use [host]:port notation for IPv6. Allowed permissions: bloomfilter (allow requesting BIP37 filtered blocks and transactions), noban (do not ban for misbehavior; implies download), forcerelay (relay transactions that are already in the mempool; implies relay), relay (relay even in -blocksonly mode, and unlimited transaction announcements), mempool (allow requesting BIP35 mempool contents), download (allow getheaders during IBD, no disconnect after maxuploadtarget limit), addr (responses to GETADDR avoid hitting the cache and contain random records with the most up-to-date info). Specify multiple permissions separated by commas (default: download,noban,mempool,relay). Can be specified multiple times. Permission flags are giving main character energy. 👑
  • -whitelist=<[permissions@]IP address or network> — Add permission flags to the peers using the given IP address (e.g. 1.2.3.4) or CIDR-notated network (e.g. 1.2.3.0/24). Uses the same permissions as -whitebind. Additional flags "in" and "out" control whether permissions apply to incoming connections and/or manual (default: incoming only). Can be specified multiple times. Whitelist, but make it precise. 🎀

👜 Wallet options 👜

  • -addresstype — What type of addresses to use ("legacy", "p2sh-segwit", "bech32", "bech32m", default: "bech32"). Address type is a whole personality, choose wisely. 💖
  • -avoidpartialspends — Group outputs by address, selecting many (possibly all) or none, instead of selecting on a per-output basis. Privacy is improved as addresses are mostly swept with fewer transactions and outputs are aggregated in clean change addresses. It may result in higher fees due to less optimal coin selection caused by this added limitation and possibly a larger-than-necessary number of inputs being used. Always enabled for wallets with "avoid_reuse" enabled, otherwise default: 0. Privacy versus fees: the eternal group-chat debate. 😭
  • -changetype — What type of change to use ("legacy", "p2sh-segwit", "bech32", "bech32m"). Default is "legacy" when -addresstype=legacy, else it is an implementation detail. Change type, but make it mysterious. 🦋
  • -consolidatefeerate=<amt> — The maximum feerate (in BTC/kvB) at which transaction building may use more inputs than strictly necessary so that the wallet’s UTXO pool can be reduced (default: 0.0001). Consolidation with boundaries. ✨
  • -disablewallet — Do not load the wallet and disable wallet RPC calls. Wallet? Not today. 🚫
  • -discardfee=<amt> — The fee rate (in BTC/kvB) 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. Dust policy, but make it financially literate. 💸
  • -fallbackfee=<amt> — A fee rate (in BTC/kvB) that will be used when fee estimation has insufficient data. 0 to entirely disable the fallbackfee feature. (default: 0.00). Backup fee, backup plan. 🫶
  • -keypool=<n> — Set key pool size to <n> (default: 1000). 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. This warning is real, bestie, don’t skip it. 😭
  • -maxapsfee=<n> — Spend up to this amount in additional (absolute) fees (in BTC) if it allows the use of partial spend avoidance (default: 0.00). Pay a little extra for the privacy vibe. 💅
  • -mintxfee=<amt> — Fee rates (in BTC/kvB) smaller than this are considered zero fee for transaction creation (default: 0.00001). Minimum fee, minimum drama. ⭐
  • -signer=<cmd> — External signing tool, see doc/external-signer.md. Signing outside the house, iykyk. 🔐
  • -spendzeroconfchange — Spend unconfirmed change when sending transactions (default: 1). Zero-conf change is a choice, and the default says yes. 🎀
  • -txconfirmtarget=<n> — Include enough fee so transactions begin confirmation on average within n blocks (default: 6). Target those confirmations. 🎯
  • -wallet=<path> — Specify wallet path to load at startup. Can be used multiple times to load multiple wallets. Path is to a directory containing wallet data and log files. If the path is not absolute, it is interpreted relative to <walletdir>. This only loads existing wallets and does not create new ones. For backwards compatibility this also accepts names of existing top-level data files in <walletdir>. Load your wallets, don’t expect it to birth new ones. 👑
  • -walletbroadcast — Make the wallet broadcast transactions (default: 1). Wallet says send it, network hears about it. 📣
  • -walletdir=<dir> — Specify directory to hold wallets (default: <datadir>/wallets if it exists, otherwise <datadir>). Wallet home directory, basically. 🏠
  • -walletnotify=<cmd> — Execute command when a wallet transaction changes. %s in cmd is replaced by TxID, %w is replaced by wallet name, %b is replaced by the hash of the block including the transaction (set to 'unconfirmed' if the transaction is not included) and %h is replaced by the block height (-1 if not included). %w is not currently implemented on windows. On systems where %w is supported, it should NOT be quoted because this would break shell escaping used to invoke the command. Notifications with placeholders, but mind the quoting rule. 🙈
  • -walletrbf — (DEPRECATED) Send transactions with full-RBF opt-in enabled (default: 1). It’s deprecated, so don’t build your whole lore around it. 💀

💌 ZeroMQ notification options 💌

  • -zmqpubhashblock=<address> — Enable publish hash block in <address>. Hash block notifications, activated. 🔔
  • -zmqpubhashblockhwm=<n> — Set publish hash block outbound message high water mark (default: 1000). High water mark, high key important. 🌊
  • -zmqpubhashtx=<address> — Enable publish hash transaction in <address>. Hash transaction notifications, activated. 🔔
  • -zmqpubhashtxhwm=<n> — Set publish hash transaction outbound message high water mark (default: 1000). Another HWM, another boundary. 🌊
  • -zmqpubrawblock=<address> — Enable publish raw block in <address>. Raw block notifications, activated. 🧱
  • -zmqpubrawblockhwm=<n> — Set publish raw block outbound message high water mark (default: 1000). Raw block HWM, handled. 🌊
  • -zmqpubrawtx=<address> — Enable publish raw transaction in <address>. Raw transaction notifications, activated. 📨
  • -zmqpubrawtxhwm=<n> — Set publish raw transaction outbound message high water mark (default: 1000). Raw tx HWM, handled. 🌊
  • -zmqpubsequence=<address> — Enable publish hash block and tx sequence in <address>. Sequence notifications, activated. 🔔
  • -zmqpubsequencehwm=<n> — Set publish hash sequence message high water mark (default: 1000). Sequence HWM, handled. 🌊

🧪 Debugging/Testing options 🧪

  • -debug=<category> — The debugging/testing knob, with a <category> value. That’s where this chunk hands off, bestie. 🧚
  • -debug=<category> — turn on debug + trace logging, bestie 💖 (default is -nodebug, and tbh you don't even have to give a <category>). If <category> is missing, or it's 1 or "all", you get everything. If <category> is 0 or "none", any other categories you listed just get ignored, no drama. Other valid <category> values are: addrman, bench, blockstorage, cmpctblock, coindb, estimatefee, http, i2p, ipc, kernel, leveldb, mempool, mempoolrej, mining, net, privatebroadcast, proxy, prune, qt, rand, reindex, rpc, scan, selectcoins, tor, txpackages, txreconciliation, validation, walletdb, zmq. You can pass this option multiple times to get multiple categories, slay ✨
  • -debugexclude=<category> — nah, skip debug + trace logging for one category 🚫. You can pair it with -debug=1 so you get debug and trace logging for all categories except the one you named — iconic combo. Pass it multiple times to exclude multiple categories. And heads up: this one takes priority over "-debug".
  • -help-debug — print the help message with the debugging options and bounce 👋
  • -logips — include IP addresses in log output (default: 0)
  • -loglevelalways — always prepend a category and level (default: 0)
  • -logratelimit — apply rate limiting to unconditional logging to mitigate disk-filling attacks (default: 1) 🛡️
  • -logsourcelocations — prepend debug output with the name of the originating source location (source file, line number and function name) (default: 0)
  • -logthreadnames — prepend debug output with the name of the originating thread (default: 0)
  • -logtimestamps — prepend debug output with a timestamp (default: 1) ⏰
  • -maxtxfee=<amt> — max total fees (in BTC) to use in a single wallet transaction; set it too low and your big transactions may just abort 😭 (default: 0.10)
  • -printtoconsole — send trace/debug info to the console (default: 1 when no -daemon). Wanna kill logging to file? set -nodebuglogfile 🪵
  • -shrinkdebugfile — shrink the debug log file when the client starts (default: 1 when no -debug)
  • -uacomment=<cmt> — append a comment to the user agent string 💬

⛓️ Chain selection options

  • -chain=<chain> — use the chain <chain> (default: main). Allowed values: main, test, testnet4, signet, regtest
  • -signet — use the signet chain. Same thing as -chain=signet. Note that the network is defined by the -signetchallenge parameter 👀
  • -signetchallenge — blocks must satisfy the given script to be considered valid (only for signet networks; defaults to the global default signet test network challenge)
  • -signetseednode — specify a seed node for the signet network, in the hostname[:port] format, e.g. sig.net:1234 (may be used multiple times to specify multiple seed nodes; defaults to the global default signet test network seed node(s))
  • -testnet — use the testnet3 chain. Equivalent to -chain=test. > Support for testnet3 is deprecated and will be removed in an upcoming release, so maybe consider moving to testnet4 now by using -testnet4 💀
  • -testnet4 — use the testnet4 chain. Equivalent to -chain=testnet4 🌈

📡 Node relay options

  • -bytespersigop — equivalent bytes per sigop in transactions for relay and mining (default: 20)
  • -datacarrier — relay and mine data carrier transactions (default: 1)
  • -datacarriersize — relay and mine transactions whose data-carrying raw scriptPubKeys in aggregate are of this size or less, allowing multiple outputs (default: 100000)
  • -minrelaytxfee=<amt> — fees (in BTC/kvB) smaller than this are considered zero fee for relaying, mining and transaction creation (default: 0.000001)
  • -permitbaremultisig — relay transactions creating non-P2SH multisig outputs (default: 1)
  • -privatebroadcast — EXPERIMENTAL 🧪: broadcast transactions submitted via the sendrawtransaction RPC using short-lived connections through the Tor or I2P networks, without putting them in the mempool first. This gives best-effort concealment of the transaction's origin. Transactions submitted through the wallet are not affected by this option (default: 0)
  • -whitelistforcerelay — add 'forcerelay' permission to whitelisted peers with default permissions. This will relay transactions even if the transactions were already in the mempool (default: 0)
  • -whitelistrelay — add 'relay' permission to whitelisted peers with default permissions. This will accept relayed transactions even when not relaying transactions (default: 1)

🧱 Block creation options

  • -blockmintxfee=<amt> — set the lowest fee rate (in BTC/kvB) for transactions to be included in block creation (default: 0.00000001)
  • -blockreservedweight=<n> — reserve space for the fixed-size block header plus the largest coinbase transaction the mining software may add to the block. Only affects mining RPC clients, not IPC clients (default: 8000).

🌐 RPC server options

  • -rest — accept public REST requests (default: 0)
  • -rpcallowip=<ip> — allow JSON-RPC connections from the specified source. Valid values for <ip> are a single IP (e.g. 1.2.3.4), a network/netmask (e.g. 1.2.3.4/255.255.255.0), a network/CIDR (e.g. 1.2.3.4/24), all ipv4 (0.0.0.0/0), or all ipv6 (::/0). RFC4193 is allowed only if -cjdnsreachable=0. This option can be specified multiple times
  • -rpcauth=<userpw> — username and HMAC-SHA-256 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
  • -rpcbind=<addr>[:port] — bind to the 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: 127.0.0.1 and ::1 i.e., localhost)
  • -rpccookiefile=<loc> — location of the auth cookie. Relative paths will be prefixed by a net-specific datadir location (default: data dir)
  • -rpccookieperms=<readable-by> — set permissions on the RPC auth cookie file so that it is readable by [owner|group|all] (default: owner [via umask 0077])
  • -rpcmaxconnections=<n> — the maximum number of connected HTTP clients (default: 16)
  • -rpcpassword=<pw> — password for JSON-RPC connections 🔑
  • -rpcport=<port> — listen for JSON-RPC connections on <port> (default: 8332, testnet3: 18332, testnet4: 48332, signet: 38332, regtest: 18443)
  • -rpcthreads=<n> — set the number of threads to service RPC calls (default: 16)
  • -rpcuser=<user> — username for JSON-RPC connections
  • -rpcwhitelist=<whitelist> — 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 the -rpcwhitelistdefault documentation for info on default whitelist behavior 👀
  • -rpcwhitelistdefault — 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, the rpc server acts as if all rpc users are subject to empty whitelists.
  • -server — accept command line and JSON-RPC commands

Copyright (C) 2009-2026 The Bitcoin Core developers

Please contribute if you find Bitcoin Core useful 💖. Visit <https://bitcoincore.org/> for further information about the software. The source code is available from <https://github.com/bitcoin/bitcoin>.

This is experimental software. Distributed under the MIT software license, see the accompanying file COPYING or <https://opensource.org/license/MIT> 🫶

🦋 SEE ALSO

bitcoin(1), bitcoind(1), bitcoin-cli(1), bitcoin-tx(1), bitcoin-wallet(1), bitcoin-util(1), bitcoin-qt(1)

okay that's literally the whole page bestie, you ate that 🎀✨ this one's bitcoind v32.0.0, dated October 2026, and it lives in the BITCOIND(1) section — go be the main character of your own node now, ily, bye 💜🌈

📦 where this page comes from