Encyclopedia How the network works · Entry 196
Bitcoin Core explained: node software, wallet and RPC interface
In this article
At a glance
Key facts
Separate the jobs performed by one installation
A Core process can communicate with Bitcoin peers while a wallet tracks only the outputs relevant to its keys and scripts. The block database and wallet database are separate parts of the data directory. Losing one has different consequences from losing the other.
The cited RPC interface documents both general endpoints and wallet-specific endpoints. More than one wallet can be loaded, so an application must identify which wallet it intends to query or control.
A node can run without holding your spending keys
Imagine a household node serving a separate wallet application. The node supplies a validated chain view, while another device signs transactions. The node’s online presence does not itself imply that it can spend the household’s funds.
Conversely, a Core wallet with usable keys is sensitive even though it lives alongside public chain data. Protect its backups and privileged control interface.
Read the configuration with the role in mind
Pruning affects historical block retention; wallet settings affect key and transaction management; synchronization options can affect which historical checks are performed under configured assumptions. A label such as full node does not replace reading those settings.
Core reports its selected chain and synchronization state. Confirm those before using it as the basis for a payment decision, particularly after initial setup or a long offline period.
Direct answers
Questions people ask
Do I earn bitcoin by running Bitcoin Core?
No. Running a validating node has no built-in block reward. Mining constructs candidate blocks and performs proof of work; a node can validate and relay without performing that mining work.
Do I need to keep a wallet inside my node?
No. The node and wallet are distinct roles. A separate signer or wallet application can use a node for chain information, and the RPC interface supports non-wallet requests as well as wallet-specific operations.
Inspect the evidence
The answer and key facts have stable claim links. These records retain the scope and qualification when reused.
Bitcoin Core is Bitcoin software that can validate and relay blocks and transactions, maintain a chain view and manage wallets. Its graphical application and background daemon expose different interfaces to related capabilities. Running it is not mining and does not automatically earn bitcoin. Wallet use is optional, and validation, storage and network behavior depend on the actual version and configuration.
Educational explanation. Product-specific behavior is scoped to the cited documentation, checked 2026-10-02.
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.
Link to this claimNode role: Maintain and validate a chain view
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.
Link to this claimWallet role: Manage relevant keys, scripts and transactions
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.
Link to this claimRPC role: Allow authorized programs to control the software
Scope: Bitcoin · data through 2026-10-02. Verification: verified · 2026-10-02T19:29:20.637Z.
Link to this claimRevision history
- — First publication after primary-source research and separate automated verification.
Source register
Sources and references
Retrieval dates and locators are recorded individually.- Running a Full NodeBitcoin.org
Operational roles, synchronization, inbound/outbound connections and version-dependent resource guidance.
Locator: What Is A Full Node?; Initial Block Download; Network Configuration; Reduce Storage; Disable listening · Retrieved: 2026-10-02T18:53:56.154ZOpen source - JSON-RPC interfaceBitcoin Core
Privileged RPC scope, authentication, local access and unencrypted transport limitations.
Locator: Introduction; Endpoints; Versioning; Security; RPC consistency guarantees · Version / scope: Bitcoin Core v29.0 · Retrieved: 2026-10-02T18:53:55.910ZOpen source - FilesBitcoin Core
Wallet, block, chainstate and index files have different recovery purposes.
Locator: Data directory location and chain-specific paths; Data directory layout: blocks/, chainstate/, wallets/; Multi-wallet environment and backupwallet guidance · Version / scope: Bitcoin Core v29.0 · Retrieved: 2026-10-02T18:53:55.926ZOpen source - Node initializationBitcoin Core
Definitions of reindex/chainstate rebuild and node configuration switches.
Locator: SetupServerArgs: assumevalid, reindex, reindex-chainstate, prune, listen, server; prune/reindex-chainstate compatibility check · Version / scope: Bitcoin Core v29.0 · Retrieved: 2026-10-02T18:53:55.958ZOpen source - getblockchaininfo RPCBitcoin Core
Network identity and sync-status fields; progress is an estimate.
Locator: Result: chain, blocks, headers, verificationprogress, initialblockdownload · Version / scope: Bitcoin Core 29.0 RPC reference; not a recommendation to install an old release · Retrieved: 2026-10-02T18:53:55.851ZOpen source - MiningBitcoin developer documentation
Hardware work, candidate blocks and pool shares; historical examples are not current equipment recommendations.
Locator: Mining; Solo Mining; Pool Mining; Block Prototypes · Version / scope: Developer guide; historical implementation details require qualification · Retrieved: 2026-10-02T18:53:53.955ZOpen source
Research and drafting use AI assistance. A separate automated review checks claims against primary sources; no external expert or named human review is implied. Publication, substantive editing, source retrieval and verification are recorded separately. This version was independently checked by an automated reviewer on 2 October 2026.
Editorial method and correctionsDegrees of Satoshi editorial project. “Bitcoin Core explained: node software, wallet and RPC interface.” Published 2026-10-02; updated 2026-10-02. https://degreesofsatoshi.com/encyclopedia/bitcoin-core-explained/