BITCOIN-QT(1)

📦
version 31.1 · 7 versions
, in epel 10, fedora 43, fedora 44

👑 BITCOIN-QT 👑

bestie. you have found the manual page for bitcoin-qt, a User Commands page, and honestly it's giving main character energy. sit down, grab a strawberry 🍓, and let's get into it.

🌸 NAME 🌸

bitcoin-qt — manual page for bitcoin-qt v31.1.0

✨ SYNOPSIS ✨

bitcoin-qt [options] [URI]

💖 DESCRIPTION 💖

Bitcoin Core version v31.1.0 ✨

so the bitcoin-qt application is a whole graphical interface for interacting with Bitcoin Core. like, a real window. with buttons. we love that for us. 💅

it combines the core functionalities of bitcoind with a user-friendly interface for wallet management, transaction history, and network statistics. it's giving "everything bagel but make it crypto."

it's literally made for users who prefer a graphical over a command-line interface. no shame, we respect the aesthetic. 🎀

and you can optionally specify a payment [URI], in e.g. the BIP21 URI format. cute!

💅 OPTIONS 💅

  • -alertnotify=<cmd> — run this command when an alert gets raised. %s in cmd gets replaced by the message. 📢
  • -allowignoredconf — for backwards compatibility, treat an unused bitcoin.conf file in the datadir as a warning, not an error. soft launch, not a hard fail. 🫶
  • -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). the defaults are:
default: 00000000000000000000ccebd6d74d9194d8dcdc1d177c478e094bfad51ba5ac
testnet3: 000000007a61e4230b28ac5cb6b5e5a0130de37ac1faf2f8987d2fa6505b67f4
testnet4: 0000000002368b1e4ee27e2e85676ae6f9f9e69579b29093e9a82c170bf7cf8a
signet: 00000008414aab61092ef93f1aacc54cf9e9f16af29ddad493b908a01ff5c329
  • -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. no cap. 🔥
  • -blocknotify=<cmd> — run this command when the best block changes. %s in cmd gets replaced by the block hash. 🔔
  • -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. 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 coinstats index used by the gettxoutsetinfo RPC (default: 0).
  • -conf=<file> — specify path to read-only configuration file. relative paths will be prefixed by the datadir location (only useable from command line, not configuration file) (default: bitcoin.conf).
  • -daemon — run in the background as a daemon and accept commands (default: 0). ghost mode 👻
  • -daemonwait — wait for initialization to be finished before exiting. this implies -daemon (default: 0).
  • -datadir=<dir> — specify 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 location of 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 additional configuration file, relative to the -datadir path (only useable from configuration file, not command line).
  • -loadblock=<file> — imports blocks from an external file on startup.
  • -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). multitasking, but make it consensus. 🧚
  • -persistmempool — whether to save the mempool on shutdown and load 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 pid file. relative paths will be prefixed by a net-specific datadir location. (default: bitcoind.pid)
  • -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. that's not a vibe, that's a whole era. 💀

(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 path to dynamic settings data file. can be disabled with -nosettings. file is written at runtime and not meant to be edited by users (use bitcoin.conf instead for custom settings). relative paths will be prefixed by datadir location. (default: settings.json)
  • -shutdownnotify=<cmd> — execute 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 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 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). one full day of silence. 🤫
  • -bind=<addr>[:<port>][=onion] — bind to 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. monogamy, but for peers. 💜
  • -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.
  • -listen — accept connections from outside (default: 1 if no -proxy, -connect or -maxconnections=0).
  • -listenonion — automatically create Tor onion service (default: 1). layers upon layers, iconic. 🧅
  • -maxconnections=<n> — maintain at most <n> automatic connections to peers (default: 125). 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.
  • -maxreceivebuffer=<n> — maximum per-connection receive buffer, <n>*1000 bytes (default: 5000).
  • -maxsendbuffer=<n> — maximum per-connection memory usage for the send buffer, <n>*1000 bytes (default: 1000).
  • -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 the 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.
  • -natpmp

✨ and finishing up the one right before this: Use PCP or NAT-PMP to map the listening port (default: 1).

  • -networkactive — turn ALL the P2P network activity on (default: 1). You can flip this later with the setnetworkactive RPC command 💫
  • -onion=<ip:port|path> — use a whole separate SOCKS5 proxy just for reaching peers through Tor onion services. Set -noonion to shut it off (default: -proxy). It can also be a local file path if you slap unix: in front of it 🧅
  • -onlynet=<net> — make automatic outbound connections go only to network <net>, and your choices are ipv4, ipv6, onion, i2p, cjdns. Inbound and manual connections are not affected by this, jsyk. You can drop this flag multiple times to allow multiple networks 🕸️
  • -peerblockfilters — serve compact block filters to peers per BIP 157 (default: 0)
  • -peerbloomfilters — support filtering of blocks and transaction with bloom filters (default: 0)
  • -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). Fun lil detail: if you set it to a value x, the default onion listening port becomes x+1 🎀
  • -proxy=<ip>[:<port>]|unix:<path>[=<network>] — connect through a SOCKS5 proxy; set -noproxy to disable it. It may be a local file path prefixed with unix: if the proxy supports that. You can end it in =network to set the proxy only for that network, and the network can be any of ipv4, ipv6, tor or cjdns. (default: disabled)
  • -proxyrandomize — randomize credentials for every single proxy connection. This is what enables Tor stream isolation (default: 1) 🔀
  • -seednode=<ip> — connect to a node to retrieve peer addresses, then disconnect. You can specify this multiple times to hit up multiple nodes. During startup, seednodes get tried before dnsseeds 🌱
  • -timeout=<n> — socket connection timeout in milliseconds. If an initial attempt to connect doesn't work after this amount of time, it gets dropped (minimum: 1, default: 5000) ⏱️
  • -torcontrol=<ip>:<port> — Tor control host and port to use if onion listening is enabled (default: 127.0.0.1:9051). No port specified? It defaults to port 9051 🧅
  • -torpassword=<pass> — Tor control port password (default: empty)
  • -v2transport — support v2 transport (default: 1)
  • -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 are: 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 💅
  • -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. Two extra flags, in and out, control whether permissions apply to incoming connections and/or manual (default: incoming only). Can be specified multiple times ✨

💖 Wallet options 💖

  • -addresstype — what type of addresses to use: "legacy", "p2sh-segwit", "bech32", "bech32m" (default: "bech32") 💳
  • -avoidpartialspends — group outputs by address, selecting many (possibly all) or none, instead of selecting on a per-output basis. Privacy gets better since addresses are mostly swept with fewer transactions and outputs are aggregated in clean change addresses. It may result in higher fees though, because this added limitation makes coin selection less optimal and can pull in a larger-than-necessary number of inputs. Always enabled for wallets with "avoid_reuse" enabled, otherwise default: 0.
  • -changetype — what type of change to use: "legacy", "p2sh-segwit", "bech32", "bech32m". Default is "legacy" when -addresstype=legacy, otherwise it's an implementation detail 🤫
  • -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) 🧹
  • -disablewallet — do not load the wallet and disable wallet RPC calls 🚫
  • -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 🗑️
  • -fallbackfee=<amt> — a fee rate (in BTC/kvB) that will be used when fee estimation has insufficient data. 0 entirely disables the fallbackfee feature. (default: 0.00)
  • -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. So like… don't be reckless with this one bestie 😭
  • -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)
  • -mintxfee=<amt> — fee rates (in BTC/kvB) smaller than this are considered zero fee for transaction creation (default: 0.00001)
  • -signer=<cmd> — external signing tool, see doc/external-signer.md ✍️
  • -spendzeroconfchange — spend unconfirmed change when sending transactions (default: 1)
  • -txconfirmtarget=<n> — include enough fee so transactions begin confirmation on average within n blocks (default: 6) ⛓️
  • -wallet=<path> — specify the wallet path to load at startup. Can be used multiple times to load multiple wallets. The path is to a directory containing wallet data and log files. If the path isn't absolute, it's 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> 👛
  • -walletbroadcast — make the wallet broadcast transactions (default: 1) 📡
  • -walletdir=<dir> — specify the directory to hold wallets (default: <datadir>/wallets if it exists, otherwise <datadir>) 🗂️
  • -walletnotify=<cmd> — execute a command when a wallet transaction changes. %s in cmd gets replaced by TxID, %w gets replaced by wallet name, %b gets replaced by the hash of the block including the transaction (set to 'unconfirmed' if the transaction is not included) and %h gets replaced by the block height (-1 if not included). Heads up: %w is not currently implemented on windows. On systems where %w is supported, it should NOT be quoted, because that would break the shell escaping used to invoke the command 🔔
  • -walletrbf — send transactions with full-RBF opt-in enabled (RPC only, default: 1)

🌈 ZeroMQ notification options 🌈

  • -zmqpubhashblock=<address> — enable publish hash block in <address> 📢
  • -zmqpubhashblockhwm=<n> — set publish hash block outbound message high water mark (default: 1000)
  • -zmqpubhashtx=<address> — enable publish hash transaction in <address>
  • -zmqpubhashtxhwm=<n> — set publish hash transaction outbound message high water mark (default: 1000)
  • -zmqpubrawblock=<address> — enable publish raw block in <address>
  • -zmqpubrawblockhwm=<n> — set publish raw block outbound message high water mark (default: 1000)
  • -zmqpubrawtx=<address> — enable publish raw transaction in <address>
  • -zmqpubrawtxhwm=<n> — set publish raw transaction outbound message high water mark (default: 1000)
  • -zmqpubsequence=<address> — enable publish hash block and tx sequence in <address>
  • -zmqpubsequencehwm=<n> — set publish hash sequence message high water mark (default: 1000)

🐛 Debugging/Testing options 🐛

  • -debug=<category> — output debug and trace logging (default: -nodebug, supplying <category> is optional). If <category> isn't supplied, or if <category> is 1 or "all", output all debug logging. If <category> is 0 or "none", any other categories are ignored. Other valid values for <category> are: addrman, bench, blockstorage, cmpctblock, coindb, estimatefee, http, i2p, ipc, kernel, leveldb, libevent, mempool, mempoolrej, net, privatebroadcast, proxy, prune, qt, rand, reindex, rpc, scan, selectcoins, tor, txpackages, txreconciliation, validation, walletdb, zmq. This option can be specified multiple times to output multiple categories 🔍
  • -debugexclude=<category> — exclude debug and trace logging for a category. Can be used alongside -debug=1 to output debug and trace logging for all categories except the one you name. This option can be specified multiple times to exclude multiple categories. This takes priority over "-debug" 🙅
  • -help-debug — print help message with debugging options and exit
  • -logips — include IP addresses in log output (default: 0) 🌐
  • -loglevelalways — always prepend a category and level (default: 0)
  • -logsourcelocations — prepend debug output with name of the originating source location (source file, line number and function name) (default: 0) 📍
  • -logthreadnames — prepend debug output with name of the originating thread (default: 0) 🧵
  • -logtimestamps — prepend debug output with timestamp (default: 1) ⏰
  • -maxtxfee=<amt> — maximum total fees (in BTC) to use in a single wallet transaction; setting this too low may abort large transactions (default: 0.10)
  • -printtoconsole — send trace/debug info to console (default: 1 when no -daemon. To disable logging to file, set -nodebuglogfile) 🖨️
  • -shrinkdebugfile — Shrink that debug.log file on client startup ✂️ (default: 1 when you're not running -debug)
  • -uacomment=<cmt> — Glue a lil comment onto the end of the user agent string 💬 like a signature on your fit

🦋 Chain selection options 🦋

  • -chain=<chain> — Pick your chain <chain> (default: main). Allowed values: main, test, testnet4, signet, regtest ⛓️
  • -signet — Use the signet chain. Same thing as -chain=signet. Heads up tho: the network is actually defined by the -signetchallenge parameter 👀
  • -signetchallenge — Blocks have to satisfy the given script to count as valid (only a signet thing; defaults to the global default signet test network challenge) 🧩
  • -signetseednode — Name a seed node for the signet network, in hostname[:port] format, e.g. sig.net:1234 (you can use this multiple times to list 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. Consider moving to testnet4 now by using -testnet4. Like, fr, start packing your bags 🧳
  • -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 this size or less — yes, multiple outputs allowed (default: 100000) 🗂️
  • -minrelaytxfee=<amt> — Fees (in BTC/kvB) smaller than this get treated as zero fee for relaying, mining and transaction creation (default: 0.000001) 💸
  • -permitbaremultisig — Relay transactions that create non-P2SH multisig outputs (default: 1) 🫶
  • -privatebroadcast — Broadcast transactions submitted via the sendrawtransaction RPC using short-lived connections through the Tor or I2P networks, without putting them in the mempool first. Transactions submitted through the wallet are not affected by this option (default: 0) 🕵️♀️
  • -whitelistforcerelay — Add the 'forcerelay' permission to whitelisted peers that have default permissions. This relays transactions even if they were already in the mempool. (default: 0) 🔁
  • -whitelistrelay — Add the 'relay' permission to whitelisted peers that have default permissions. This accepts relayed transactions even when you're 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 a 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 get prefixed by a net-specific datadir location. (default: data dir) 🍪
  • -rpccookieperms=<readable-by> — Set permissions on the RPC auth cookie file so it's readable by [owner|group|all] (default: owner [via umask 0077]) 🔒
  • -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 how many threads 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're set-intersected. See the -rpcwhitelistdefault docs for info on default whitelist behavior. 📝
  • -rpcwhitelistdefault — Sets the 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 🖥️

🎀 UI Options 🎀

  • -choosedatadir — Choose data directory on startup (default: 0) 📁
  • -lang=<lang> — Set language, for example "de_DE" (default: system locale) 🗣️
  • -min — Start minimized 😴
  • -resetguisettings — Reset all settings changed in the GUI 🔄
  • -splash — Show splash screen on startup (default: 1) 🌈

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)

and that's a wrap bestie!! 🎉 this whole page is straight from bitcoin-qt v31.1.0, dated July 2026, and it's literally titled BITCOIN-QT(1) — so if you need to cite it, that's your receipt 🧾💖 go forth and bitcoin-qt responsibly, mwah 💅✨

📦 where this page comes from