Inside Bitcoin
Opening the selected file…
Inside Bitcoin
Opening the selected file…
The code behind the network, with room to understand it.
Release published 2026-10-28 · Snapshot fetched 2026-11-01. Latest stable release at fetch time; development branches and Git history are excluded. Only the selected code window and visible folders load here.
751.HP752\fB\-whitelistrelay\fR753.IP754Add 'relay' permission to whitelisted peers with default permissions.755This will accept relayed transactions even when not relaying756transactions (default: 1)757.PP758Block creation options:759.HP760\fB\-blockmintxfee=\fR<amt>761.IP762Set lowest fee rate (in BTC/kvB) for transactions to be included in763block creation. (default: 0.00000001)764.HP765\fB\-blockreservedweight=\fR<n>766.IP767Reserve space for the fixed\-size block header plus the largest coinbase768transaction the mining software may add to the block. Only769affects mining RPC clients, not IPC clients. (default: 8000).770.PP771RPC server options:772.HP773\fB\-rest\fR774.IP775Accept public REST requests (default: 0)776.HP777\fB\-rpcallowip=\fR<ip>778.IP779Allow JSON\-RPC connections from specified source. Valid values for <ip>780are a single IP (e.g. 1.2.3.4), a network/netmask (e.g.7811.2.3.4/255.255.255.0), a network/CIDR (e.g. 1.2.3.4/24), all782ipv4 (0.0.0.0/0), or all ipv6 (::/0). RFC4193 is allowed only if783\fB\-cjdnsreachable\fR=\fI\,0\/\fR. This option can be specified multiple times784.HP785\fB\-rpcauth=\fR<userpw>786.IP787Username and HMAC\-SHA\-256 hashed password for JSON\-RPC connections. The788field <userpw> comes in the format: <USERNAME>:<SALT>$<HASH>. A789canonical python script is included in share/rpcauth. The client790then connects normally using the791rpcuser=<USERNAME>/rpcpassword=<PASSWORD> pair of arguments. This792option can be specified multiple times793.HP794\fB\-rpcbind=\fR<addr>[:port]795.IP796Bind to given address to listen for JSON\-RPC connections. Do not expose797the RPC server to untrusted networks such as the public internet!798This option is ignored unless \fB\-rpcallowip\fR is also passed. Port is799optional and overrides \fB\-rpcport\fR. Use [host]:port notation for800IPv6. This option can be specified multiple times (default:801127.0.0.1 and ::1 i.e., localhost)802.HP803\fB\-rpccookiefile=\fR<loc>804.IP805Location of the auth cookie. Relative paths will be prefixed by a806net\-specific datadir location. (default: data dir)807.HP808\fB\-rpccookieperms=\fR<readable\-by>809.IP810Set permissions on the RPC auth cookie file so that it is readable by811[owner|group|all] (default: owner [via umask 0077])812.HP813\fB\-rpcmaxconnections=\fR<n>814.IP815The maximum number of connected HTTP clients (default: 16)816.HP817\fB\-rpcpassword=\fR<pw>818.IP819Password for JSON\-RPC connections820.HP821\fB\-rpcport=\fR<port>822.IP823Listen for JSON\-RPC connections on <port> (default: 8332, testnet3:82418332, testnet4: 48332, signet: 38332, regtest: 18443)825.HP826\fB\-rpcthreads=\fR<n>827.IP828Set the number of threads to service RPC calls (default: 16)829.HP830\fB\-rpcuser=\fR<user>831.IP832Username for JSON\-RPC connections833.HP834\fB\-rpcwhitelist=\fR<whitelist>835.IP836Set a whitelist to filter incoming RPC calls for a specific user. The837field <whitelist> comes in the format: <USERNAME>:<rpc 1>,<rpc8382>,...,<rpc n>. If multiple whitelists are set for a given user,839they are set\-intersected. See \fB\-rpcwhitelistdefault\fR documentation840for information on default whitelist behavior.841.HP842\fB\-rpcwhitelistdefault\fR843.IP844Sets default behavior for rpc whitelisting. Unless rpcwhitelistdefault845is set to 0, if any \fB\-rpcwhitelist\fR is set, the rpc server acts as846if all rpc users are subject to empty\-unless\-otherwise\-specified847whitelists. If rpcwhitelistdefault is set to 1 and no848\fB\-rpcwhitelist\fR is set, rpc server acts as if all rpc users are849subject to empty whitelists.850.HP851\fB\-server\fR852.IP853Accept command line and JSON\-RPC commands854.SH COPYRIGHT855Copyright (C) 2009-2026 The Bitcoin Core developers857Please contribute if you find Bitcoin Core useful. Visit858<https://bitcoincore.org/> for further information about the software.859The source code is available from <https://github.com/bitcoin/bitcoin>.861This is experimental software.862Distributed under the MIT software license, see the accompanying file COPYING863or <https://opensource.org/license/MIT>864.SH "SEE ALSO"865bitcoin(1), bitcoind(1), bitcoin-cli(1), bitcoin-tx(1), bitcoin-wallet(1), bitcoin-util(1), bitcoin-qt(1)
Independent explanations by MyBitcoinExplorer. Not affiliated with or endorsed by Bitcoin Core. Guides are educational and do not replace the source or its tests.
Bitcoin Core source © its contributors, distributed under the MIT license. Original notices and bundled third-party licenses are retained in the source tree.