Skip to content
Crypto.world

Practical Guides

How to Run a Bitcoin Full Node at Home

Install Bitcoin Core at home and verify the download, sync the chain, choose full or pruned storage, connect your own wallet, decide on port 8333 and Tor, and keep the node updated.

How to Run a Bitcoin Full Node at Home

What a Home Node Does for You, and What It Does Not

The steps below install Bitcoin Core, the reference software published at bitcoincore.org, on a computer you own, and turn it into a full node that your own wallet can rely on. The guide is for readers comfortable with a terminal who want to check their own payments without asking someone else's server. Every option name and default comes from the Bitcoin Core 31.1 source code, its documentation or its release notes, checked on 23 October 2026.

:::callout-info In one minute: A full node checks every block against Bitcoin's rules by itself, and it earns its owner nothing. A full copy needs about 870 GB by the 31.1 software's own estimate; pruning cuts the block files to as little as 550 MiB. Download from bitcoincore.org, check the file against SHA256SUMS, then check the signatures on SHA256SUMS. Keep the wallet connection on your own machine or network, and decide on purpose whether port 8333 stays open. :::

Bitcoin.org's guide defines the program in one line: "A full node is a program that fully validates transactions and blocks." Its validation page says Bitcoin Core checks each block it receives, "allowing it to trust the block without trusting the miner who created it." The same page adds that Bitcoin Core users "see all transactions included in received blocks," so nobody can withhold a payment included in those blocks from view. A wallet that leans on someone else's server has to take both on trust.

Privacy is the second gain. Bitcoin.org's privacy page explains that Bitcoin Core downloads every transaction on the chain and finds the ones that pay you itself. Lightweight wallets that query a single server, the page says, tell that server all of their addresses. Tor support, covered below, helps separate the node's traffic from your IP address as well.

A node earns nothing, and the whitepaper explains why. It says the first transaction in each block "starts a new coin owned by the creator of the block," and adds: "The incentive can also be funded with transaction fees." Both go to the miner who creates the block, which bitcoin.org says currently receives a 3.125 bitcoin subsidy. Bitcoin uses proof of work, so a home node locks up no stake and receives no payout. Bitcoin.org's guide calls the people who run nodes volunteers.

Hardware, Disk and Bandwidth: What the Official Pages Say Today

The official pages disagree on disk space, because they are updated at different times. Read on 23 October 2026, they give these figures:

Source Full node Pruned node
bitcoincore.org download page "about 600GB" one-time download, plus 5–10 GB a month "as little as 10GB total"
bitcoin.org requirements page 750 GB disk; 740 GB first download 7 GB disk
Bitcoin Core 31.1 source (chainparams.cpp) 856 GB of blocks plus a 14 GB chain state 550 MiB of blocks at minimum, plus the chain state
Blockchain.com chart (independent) 777,519 MB of block data on 22 October 2026, excluding indexes —

The 31.1 figure is the one the program's first-run window uses when it tells you how much space a full copy needs. A drive smaller than 1 TB leaves little headroom for a full node. Bitcoin.org's guide also asks for a minimum read/write speed of 100 MB/s, and its requirements page lists 2 GB of RAM as the minimum recommended.

Memory use changed in version 31.0. Its release notes say the default -dbcache rose "to 1024 MiB from 450 MiB on systems where at least 4096 MiB of RAM is detected," and that dbcache=450 restores the old behaviour on tight machines. The 31.x release notes list support for Linux Kernel 3.17, macOS 14 and Windows 10 (version 1903) or newer.

Bitcoin.org's requirements page puts default-settings upload at about 5 GB a day (150 GB a month) and warns that some providers charge for, or cut off, heavy upload. The option maxuploadtarget tries to keep upload under a target per 24 hours and is off by default (0). Bitcoin.org's guide also warns that sleep settings, often on by default on laptops, slow or halt network traffic.

Download Bitcoin Core and Verify the File

Get the software only from bitcoincore.org, and check two things before running it: that the file matches the published checksum, and that the checksum list was signed by people you have reason to trust. The download page calls verification "optional but highly recommended." The steps follow its Linux instructions; macOS uses shasum -a 256 in place of sha256sum, and Windows uses certUtil -hashfile <file> SHA256.

  1. Download the release and the two check files. From bitcoincore.org/en/download, take the file for your system, plus SHA256SUMS and SHA256SUMS.asc, into one folder.
  2. Check the hash. In that folder, run the command below and look for OK after your file's name.
sha256sum --ignore-missing --check SHA256SUMS
  1. Import builder keys. Releases are signed by several contributors whose keys live in the bitcoin-core/guix.sigs repository. The download page suggests importing a few you trust, or all of them:
git clone https://github.com/bitcoin-core/guix.sigs
gpg --import guix.sigs/builder-keys/*
  1. Verify the signatures on the checksum list.
gpg --verify SHA256SUMS.asc SHA256SUMS
  1. Read the output. Each valid signature prints a line starting gpg: Good signature and a Primary key fingerprint line. A warning that a key "is not certified with a trusted signature" means you still have to confirm, by your own means, that the fingerprint belongs to that signer. If keys have expired, the page gives gpg --keyserver hkps://keys.openpgp.org --refresh-keys.

We ran these steps on 23 October 2026 on bitcoin-31.1-x86_64-linux-gnu.tar.gz. The hash check printed OK and gpg reported 11 good signatures, each with the "not certified" warning described above. Bitcoin.org's older guide still describes releases signed by a single release key; follow the current multi-signer steps on bitcoincore.org. The download page adds that the Snap package cannot be verified this way.

On Linux, unpack and install the programs the way bitcoin.org's guide shows, with the version you downloaded:

tar xzf bitcoin-31.1-x86_64-linux-gnu.tar.gz
sudo install -m 0755 -o root -g root -t /usr/local/bin bitcoin-31.1/bin/*

First Start and the Initial Block Download

Start the graphical program (bitcoin-qt) or the background service (bitcoind -daemon). The graphical program opens a welcome window that asks where to store data and offers to limit block storage; the defaults are $HOME/.bitcoin/ on Linux, $HOME/Library/Application Support/Bitcoin/ on macOS and %LOCALAPPDATA%\Bitcoin\ on Windows, per the 31.1 documentation. Settings go in a bitcoin.conf file in that folder, which is not created automatically.

The first sync is the initial block download (IBD). Bitcoin.org's guide says it "will take at least several days", longer on a slow connection or computer, and that during it the node does not accept incoming transactions. The welcome window warns that the sync "is very demanding, and may expose hardware problems with your computer that had previously gone unnoticed." You can stop and restart; it resumes where it left off.

Check progress from a terminal while the node runs:

bitcoin-cli getblockchaininfo

Watch blocks climb towards headers, verificationprogress approach 1, and initialblockdownload turn false. Stop the node cleanly with bitcoin-cli stop. Since version 30.0, bitcoin node, bitcoin gui and bitcoin rpc work as synonyms for bitcoind, bitcoin-qt and bitcoin-cli -named.

One default skips some checks. With assumevalid, the help text says, if a hard-coded block is in the chain the node will "assume that it and its ancestors are valid and potentially skip their script verification." Blocks after that point get full script checks. Setting assumevalid=0 makes the node verify every script from the first block.

Full or Pruned Storage: The prune Setting

A pruned node downloads and checks every block, then deletes old block files to stay under a size you choose. The 31.1 settings window says: "All blocks are still fully validated." You set it in bitcoin.conf, in MiB:

# keep about 10 GB of block files; 0 = no pruning (default)
prune=10000

The help text gives the values: 0 disables pruning, 1 allows manual pruning through the pruneblockchain RPC, and any value of 550 or more prunes automatically to stay under that target. The chain state is stored separately, so the disk still holds it in full. The welcome window adds that "It is faster to download the full chain first and prune it later."

What a pruned node cannot do:

  1. Run a transaction index. The help text says pruning "is incompatible with -txindex," so software that needs txindex=1 will not work.
  2. Rescan old history. A wallet rescan below the prune point stops with "Can't rescan beyond pruned data." Restore an old wallet before you prune, or on a full node.
  3. Serve the whole chain to new nodes. Under BIP 159, pruned peers must not signal that they serve the complete chain and "SHOULD NOT serve blocks deeper than" 288 blocks, about two days.
  4. Switch back cheaply. "Reverting this setting requires re-downloading the entire blockchain."

Connecting Your Own Wallet to Your Own Node

The simplest connection is the wallet built into Bitcoin Core. Since version 30.0, the release notes say, "BDB legacy wallets can no longer be created or loaded"; new wallets are descriptor wallets, and older ones can be migrated. Bitcoin.org's validation page says that if you request payments in the built-in wallet, or create addresses with getnewaddress, "your received transactions will be fully validated."

  1. Create a wallet. In the graphical program choose "Create Wallet…" in the File menu; from a terminal run bitcoin-cli createwallet "home". Back it up with "Backup Wallet…" or the backupwallet RPC, and again after encrypting it, as bitcoin.org's requirements page advises.
  2. Use a hardware wallet through the node. Start the node with -signer=<cmd>, pointing at a signing tool such as HWI, documented in doc/external-signer.md. The same document calls HWI "experimental" with "far less review than Bitcoin Core itself."
  3. Connect a separate wallet program. Programs that offer a Bitcoin Core connection talk to its RPC interface on port 8332. bitcoind enables RPC by default; the graphical program needs server=1. By default RPC accepts only local clients, and credentials go into a .cookie file readable only by the user who started the node.
  4. Serve light clients. blockfilterindex=1 plus peerblockfilters=1 makes the node serve BIP 157 compact block filters; the second option fails without the first.

Reaching RPC from another computer means setting rpcbind and rpcallowip, which the documentation reserves for secured private networks, and warns:

Although Bitcoin Core's RPC interface does use authentication, it does not use encryption, so your login credentials are sent as clear text that can be read by anyone on your network path. — Bitcoin Core, doc/JSON-RPC-interface.md (v31.1)

Port 8333, Inbound Connections and Tor

Your node validates the same whether or not others can connect to it. Bitcoin.org's guide notes that the node opens outbound connections on its own (the 31.1 code allows 8 full-relay and 2 block-relay-only), and adds: "If you just want to use your full node as a wallet, you don’t need more than these 10 connections". Accepting inbound connections on port 8333, the mainnet default, helps other nodes and lightweight clients.

The default changed in version 30.0, and a home router may already be open:

The -natpmp option is now set to 1 by default. This means nodes with -listen enabled (the default) but running behind a firewall, such as a local network router, will be reachable if the firewall/router supports any of the PCP or NAT-PMP protocols. — Bitcoin Core, release notes for version 30.0

Choose one setup and write it in bitcoin.conf:

  1. Open on purpose. Leave the defaults, or forward TCP 8333 to the node's fixed local address on your router and allow it in your firewall, as bitcoin.org's guide describes.
  2. Closed to the internet. Set natpmp=0 to stop automatic router mapping, or listen=0 to refuse all inbound connections; the code also turns off natpmp, discover and listenonion when listen=0.

To run over Tor, install Tor and point the node at its SOCKS port, 9050 on many Linux systems (Tor Browser uses 9150), per doc/tor.md:

proxy=127.0.0.1:9050
# optional: automatic outbound connections only to .onion peers
onlynet=onion
# setting proxy turns listening off; add listen=1 to keep an onion service
listen=1

With listen=1 and access to Tor's control port (9051 by default, with cookie authentication), the node creates its own onion service, since listenonion defaults to 1. bitcoin-cli getnetworkinfo shows the .onion address under localaddresses. In 31.x, -privatebroadcast sends transactions submitted through sendrawtransaction over Tor or I2P; the help text says transactions submitted through the wallet "are not affected by this option." A 6 June 2026 advisory reported that 31.0 could leak the sender's IP address with that option, and 31.1 fixed it.

Keeping the Node Updated

As of 23 October 2026, the download page names 31.1 as the latest version, which its release notes date 8 July 2026, with 31.0 (19 April 2026) and 30.0 (10 October 2025) before it. The project's GitHub repository carried a v32.0 tag dated 21 October 2026, but bitcoincore.org had no 32.0 release page or signed checksum file that day. Install a release only once it appears on bitcoincore.org with its SHA256SUMS.

The lifecycle page says the project aims for a major release every six months (its table footnote says 6 to 7) and states: "We always maintain the latest three major versions." Its table puts the end of life for 31.x after 34.0. Announcements appear on the RSS feed at bitcoincore.org/en/rss.xml and on the security advisories page. The release notes still point to an announcements mailing list, whose sign-up page read "currently not available" on 23 October.

  1. Read the release notes for option changes, such as the 31.0 dbcache default.
  2. Shut the node down and wait until it has completely stopped, which the notes say "might take a few minutes."
  3. Install the new version over the old one, after the same SHA256SUMS and signature checks.
  4. Start it and confirm the running version in the subversion field of bitcoin-cli getnetworkinfo.

Repeat this check each month. Compare subversion in getnetworkinfo with the "Latest version" line on bitcoincore.org/en/download, and confirm that blocks equals headers in getblockchaininfo. Then read connections_in in getnetworkinfo: zero means no peer is connected inbound at that moment, which does not prove the node is closed, and any higher number means it is accepting inbound connections, whichever you chose.

Sources

  1. Bitcoin Core: Download page and verification instructions (Latest version: 31.1, read 23 October 2026) bitcoincore.org
  2. Bitcoin Core 31.1 release notes, 8 July 2026 bitcoincore.org
  3. Bitcoin Core 31.0 release notes, 19 April 2026 bitcoincore.org
  4. Bitcoin Core 30.0 release notes, 10 October 2025 bitcoincore.org
  5. Bitcoin Core: Software Life Cycle bitcoincore.org
  6. Bitcoin Core: Private Broadcast May Reveal Sender IP Address in Bitcoin Core 31.0, 6 June 2026 bitcoincore.org
  7. Bitcoin Core: Subscribe to Bitcoin Core announcements (RSS feed) bitcoincore.org
  8. Bitcoin Core v31.1 source: src/init.cpp (option help text and defaults) github.com
  9. Bitcoin Core v31.1 source: src/kernel/chainparams.cpp (port 8333, assumed blockchain and chain state size) github.com
  10. Bitcoin Core v31.1 documentation: Tor support (doc/tor.md) github.com
  11. Bitcoin Core v31.1 documentation: JSON-RPC interface, Security section github.com
  12. Bitcoin Core v31.1 documentation: Support for signing transactions outside of Bitcoin Core github.com
  13. Bitcoin Core v31.1 documentation: bitcoin.conf configuration file github.com
  14. BIP 159: NODE_NETWORK_LIMITED service bit github.com
  15. Bitcoin.org: Running A Full Node bitcoin.org
  16. Bitcoin.org: Bitcoin Core Requirements and Warnings bitcoin.org
  17. Bitcoin.org: Bitcoin Core Validation bitcoin.org
  18. Bitcoin.org: Bitcoin Core's Excellent Privacy bitcoin.org
  19. Satoshi Nakamoto, Bitcoin: A Peer-to-Peer Electronic Cash System, section 6 (Incentive) bitcoin.org
  20. Blockchain.com: Blockchain Size chart (777,519 MB on 22 October 2026) blockchain.com

Related stories

Explore

More articles