Antminer X9
Monero ASIC Miner
1000KH
HASHRATE
2.47W/KH
EFFICIENCY
2470W
POWER
£852.68
EST. MONTHLY
207
DAYS
EST. ROI
This guide explains Bitcoin Core getbalances 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.19.0 introduced getbalances as a structured replacement for getbalance, getunconfirmedbalance and the balance fields then exposed by getwalletinfo. It returned BTC-denominated groups for spendable wallet outputs and, when relevant, watch-only outputs.
- Why it matters: getbalances gives a clearer wallet snapshot than its predecessors, but each field has a narrow meaning. Safe reporting preserves those distinctions and verifies actual spendability and business ownership separately.
- Current position: Require a second reviewer and explicit rollback or expiry, and pause payments, signing or network-dependent services until post-change evidence is complete.
Bitcoin Core getbalances RPC in simple English
Bitcoin Core getbalances RPC: The mine object separates trusted, untrusted_pending and immature value. Trusted covers confirmed outputs and wallet-created outputs under Core policy.
Simple example
A miner is checking Bitcoin Core getbalances RPC. A plausible figure from another loaded wallet is more dangerous than a clear error, so record wallet identity, node version and chain tip.
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.
- Mempool:
- A node’s changing local collection of valid, unconfirmed transactions.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Exact wallet boundary
Route the call to an explicitly selected wallet on the intended network. A plausible figure from another loaded wallet is more dangerous than a clear error, so record wallet identity, node version and chain tip.
Mine object
The mine object separates trusted, untrusted_pending and immature value. Trusted covers confirmed outputs and wallet-created outputs under Core policy; it does not guarantee every coin is unlocked, policy-eligible or immediately economical to spend.
Pending and immature
untrusted_pending covers outputs from others still in the mempool. Immature covers coinbase outputs that have not reached maturity. Neither should be presented as settled or available cash.
Used balance
When avoid_reuse is enabled, used reports coins sent to addresses previously spent from. This is a privacy classification, not a statement that the coins are invalid or already spent.
Watch-only object
watchonly appears only when the wallet watches something. Its trusted, pending and immature amounts are observations; signing authority may live elsewhere or not exist.
Units and reconciliation
Parse BTC decimal values into integer satoshis without binary floating point. Reconcile material decisions against listunspent, locks, transactions, confirmations and the business ledger.
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 getbalances RPC?
Bitcoin Core getbalances RPC: The mine object separates trusted, untrusted_pending and immature value. Trusted covers confirmed outputs and wallet-created outputs under Core policy.
For Bitcoin Core getbalances RPC, what should a beginner know about exact wallet boundary?
Route the call to an explicitly selected wallet on the intended network.
For Bitcoin Core getbalances RPC, what should a beginner know about mine object?
The mine object separates trusted, untrusted_pending and immature value. Trusted covers confirmed outputs and wallet-created outputs under Core policy.
For Bitcoin Core getbalances RPC, what should a beginner know about pending and immature?
untrusted_pending covers outputs from others still in the mempool. Immature covers coinbase outputs that have not reached maturity.
Conclusion
getbalances gives a clearer wallet snapshot than its predecessors, but each field has a narrow meaning. Safe reporting preserves those distinctions and verifies actual spendability and business ownership separately.
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.