This guide explains Bitcoin Core listaccounts 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 listaccounts was deprecated. It returned an object mapping legacy account names to wallet-accounting balances, with a minimum confirmation threshold defaulting to one and optional watch-only inclusion.
- Why it matters: listaccounts is a deprecated accounting projection, not a balance authority. Safe legacy support makes thresholds and watch-only scope explicit while moving financial truth to transaction and UTXO records.
- Current position: Bitcoin Core 0.16.0 listaccounts was deprecated.
Bitcoin Core listaccounts RPC in simple English
Bitcoin Core listaccounts RPC: Label every integration historical and plan removal. Account names, including the empty default account, do not isolate private keys or coins.
Simple example
A miner is checking Bitcoin Core listaccounts RPC. Mark it separately and verify external signer or ownership evidence before any claim of available funds. Build a replacement ledger keyed by immutable outpoints and business references, then compare several confirmation states before cutover.
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.
- UTXO:
- An unspent transaction output: a piece of bitcoin that can be used as an input to a later transaction.
- Node:
- A computer running Bitcoin software that checks data and communicates with other peers.
Deprecated model
Label every integration historical and plan removal. Account names, including the empty default account, do not isolate private keys or coins. Never map an account name directly to a customer custody promise without outpoint-level evidence.
Confirmation threshold
minconf defaults to one; zero includes unconfirmed effects and larger values require depth. Persist the threshold with every export and re-evaluate after reorganisations. Reports at different thresholds are not directly comparable.
Watch-only option
include_watchonly defaults false. When true, monitored but non-spendable value can enter account figures. Mark it separately and verify external signer or ownership evidence before any claim of available funds.
Balance semantics
The values reflect historical wallet-accounting rules, not simply received minus spent UTXOs. Fees, internal account transfers and transaction categories can make results surprising. Reconcile from wallet transactions and current unspent outputs in satoshis.
Dynamic keys and privacy
Object property names are user-controlled account labels and may contain sensitive business information. Parse safely, avoid treating them as schema keys in analytics and redact them from routine logs and screenshots.
Migration ledger
Export account names, mapped addresses, transactions, moves and UTXOs into a versioned evidence set. Build a replacement ledger keyed by immutable outpoints and business references, then compare several confirmation states before cutover.
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 listaccounts RPC?
Bitcoin Core listaccounts RPC: Label every integration historical and plan removal. Account names, including the empty default account, do not isolate private keys or coins.
For Bitcoin Core listaccounts RPC, what should a beginner know about deprecated model?
Label every integration historical and plan removal. Account names, including the empty default account, do not isolate private keys or coins.
For Bitcoin Core listaccounts RPC, what should a beginner know about confirmation threshold?
minconf defaults to one. Zero includes unconfirmed effects and larger values require depth.
For Bitcoin Core listaccounts RPC, what should a beginner know about watch-only option?
include_watchonly defaults false. When true, monitored but non-spendable value can enter account figures.
Conclusion
listaccounts is a deprecated accounting projection, not a balance authority. Safe legacy support makes thresholds and watch-only scope explicit while moving financial truth to transaction and UTXO records.
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.