# Bitcoin Core explained: node software, wallet and RPC interface 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. Evidence: [Running a Full Node](https://bitcoin.org/en/full-node); [JSON-RPC interface](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/JSON-RPC-interface.md); [Files](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md) Canonical: https://degreesofsatoshi.com/encyclopedia/bitcoin-core-explained/ Published: 2026-10-02 Substantively modified: 2026-10-02 Independently verified by an automated reviewer: 2026-10-02T19:29:20.637Z Data current through: 2026-10-02 AI-assisted research and drafting with a separate automated source-verification pass; no external expert or named human review is implied. ## Key facts - **Node role:** Maintain and validate a chain view ([Running a Full Node](https://bitcoin.org/en/full-node)) - **Wallet role:** Manage relevant keys, scripts and transactions ([Files](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md)) - **RPC role:** Allow authorized programs to control the software ([JSON-RPC interface](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/JSON-RPC-interface.md)) ## 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. Evidence: [JSON-RPC interface](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/JSON-RPC-interface.md); [Files](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md) ## 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. Evidence: [Running a Full Node](https://bitcoin.org/en/full-node); [JSON-RPC interface](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/JSON-RPC-interface.md) ## 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. Evidence: [Node initialization](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/src/init.cpp); [getblockchaininfo RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/blockchain/getblockchaininfo/) ## Questions ### 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. Evidence: [Running a Full Node](https://bitcoin.org/en/full-node); [Mining](https://developer.bitcoin.org/devguide/mining.html) ### 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. Evidence: [JSON-RPC interface](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/JSON-RPC-interface.md) ## Claims and scope ### bitcoin-core-explained-quick-answer 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: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### bitcoin-core-explained-fact-node-role Node role: Maintain and validate a chain view Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### bitcoin-core-explained-fact-wallet-role Wallet role: Manage relevant keys, scripts and transactions Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ### bitcoin-core-explained-fact-rpc-role RPC role: Allow authorized programs to control the software Scope: {"collection":"bitcoin","dataAsOf":"2026-10-02","blockHeight":null} ## Sources - [Running a Full Node](https://bitcoin.org/en/full-node) — Bitcoin.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.154Z. - [JSON-RPC interface](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/JSON-RPC-interface.md) — Bitcoin Core. Privileged RPC scope, authentication, local access and unencrypted transport limitations. Locator: Introduction; Endpoints; Versioning; Security; RPC consistency guarantees. Retrieved: 2026-10-02T18:53:55.910Z. - [Files](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/doc/files.md) — Bitcoin 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. Retrieved: 2026-10-02T18:53:55.926Z. - [Node initialization](https://raw.githubusercontent.com/bitcoin/bitcoin/v29.0/src/init.cpp) — Bitcoin Core. Definitions of reindex/chainstate rebuild and node configuration switches. Locator: SetupServerArgs: assumevalid, reindex, reindex-chainstate, prune, listen, server; prune/reindex-chainstate compatibility check. Retrieved: 2026-10-02T18:53:55.958Z. - [getblockchaininfo RPC](https://bitcoincore.org/en/doc/29.0.0/rpc/blockchain/getblockchaininfo/) — Bitcoin Core. Network identity and sync-status fields; progress is an estimate. Locator: Result: chain, blocks, headers, verificationprogress, initialblockdownload. Retrieved: 2026-10-02T18:53:55.851Z. - [Mining](https://developer.bitcoin.org/devguide/mining.html) — Bitcoin developer documentation. Hardware work, candidate blocks and pool shares; historical examples are not current equipment recommendations. Locator: Mining; Solo Mining; Pool Mining; Block Prototypes. Retrieved: 2026-10-02T18:53:53.955Z. ## Revision history - 2026-10-02: First publication after primary-source research and separate automated verification. ## Cite this entry Degrees 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/