This guide explains Bitcoin Core getwalletinfo RPC in plain English. It shows what the command does, what its result means and what it cannot prove.
TL;DR
- What it is: Bitcoin Core 0.16.0 getwalletinfo returned wallet name and version, confirmed, unconfirmed and immature BTC balances, transaction count, keypool age and sizes, unlock expiry, configured fee and optional HD master-key identifier. The response mixed accounting, capacity, security and configuration data.
- Why it matters: getwalletinfo is the central historical wallet-state summary, but operational approval requires identity, backup, keypool, transaction and spendability evidence beyond its convenient fields.
- Current position: Bitcoin Core 0.16.0 getwalletinfo returned wallet name and version, confirmed, unconfirmed and immature BTC balances, transaction count, keypool age and sizes, unlock expiry, configured fee and optional HD master-key identifier.
Bitcoin Core getwalletinfo RPC in simple English
Bitcoin Core getwalletinfo RPC: txcount counts wallet transactions recognised by current history and rescan state. It is not a blockchain count or an accounting completeness proof.
Simple example
A miner is checking Bitcoin Core getwalletinfo RPC. Compare expected outpoints and rescan evidence when the value changes unexpectedly. Verify both before reading financial fields, especially on multi-wallet hosts.
Key terms in plain English
- Bitcoin Core:
- Widely used software that validates Bitcoin and can provide wallet, network and operator tools.
- RPC:
- A command that software sends to a node to request information or a local action.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Wallet identity
walletname and walletversion identify the loaded wallet context and data format. Verify both before reading financial fields, especially on multi-wallet hosts. A valid response from the wrong wallet is a dangerous success, not a harmless monitoring mismatch.
Balance categories
balance is confirmed, unconfirmed_balance is unsettled and immature_balance usually includes coinbase value not yet spendable. Keep all three separate and use integer satoshis. None alone establishes available balance after coin selection, locks, fees and policy.
Transaction count
txcount counts wallet transactions recognised by current history and rescan state. It is not a blockchain count or an accounting completeness proof. Compare expected outpoints and rescan evidence when the value changes unexpectedly.
External keypool
keypoololdest gives the oldest pregenerated-key timestamp and keypoolsize counts external keys. Low capacity can disrupt address issuance on historical non-HD or locked workflows. Alert before exhaustion and test replenishment under the actual encryption state.
Internal keypool
keypoolsize_hd_internal appears only when the wallet uses a separate HD internal pool for change. Its absence is conditional, not necessarily error. Recovery tests must cover both receiving and change derivations beyond currently issued indexes.
Unlock and fee state
unlocked_until is zero when locked or an epoch expiry when unlocked for transfers. Paytxfee is historical BTC/kB configuration. Minimise unlock windows, preserve fee units and do not log high-resolution security state publicly.
How specialists test it
Operators test the command on a non-production node first. They check a normal reply, an invalid request, a timeout and a restart. This shows what the response means and prevents one local result from being mistaken for a network-wide outcome.
Frequently asked questions
What is the main point of Bitcoin Core getwalletinfo RPC?
Bitcoin Core getwalletinfo RPC: txcount counts wallet transactions recognised by current history and rescan state.
For Bitcoin Core getwalletinfo RPC, what should a beginner know about wallet identity?
walletname and walletversion identify the loaded wallet context and data format. Verify both before reading financial fields, especially on multi-wallet hosts.
For Bitcoin Core getwalletinfo RPC, what should a beginner know about balance categories?
balance is confirmed, unconfirmed_balance is unsettled and immature_balance usually includes coinbase value not yet spendable.
For Bitcoin Core getwalletinfo RPC, what should a beginner know about transaction count?
txcount counts wallet transactions recognised by current history and rescan state. It is not a blockchain count or an accounting completeness proof.
Conclusion
getwalletinfo is the central historical wallet-state summary, but operational approval requires identity, backup, keypool, transaction and spendability evidence beyond its convenient fields.
Primary sources
Check the current specification status and the documentation for the exact implementation you operate before moving production funds or changing a mining node.
Join the ASIC Mining Discussion
Members can read and join the discussion
Log in to read comments from other miners. Create a free account if you would like to ask a question or share your experience.
Membership helps us protect the discussion from spam and keep answers useful.