Why Run Your Own Bitcoin Node

Affiliate disclosure: the Umbrel Home link below is an affiliate link (we may earn a commission). The Start9 Server One link is not. For most readers we recommend building your own node, as this guide does. The cost table shows why.

Every Bitcoin transaction you make passes through someone else’s node before it reaches the network. If you don’t run your own bitcoin full node, you’re trusting a third party to tell you what’s happening on the blockchain. That third party knows your IP address, your wallet addresses, and your transaction history. Running your own node eliminates that dependency entirely.

This guide covers everything you need to set up and run a bitcoin full node at home: the real reasons it matters, what hardware you need, which software to choose, and a step-by-step walkthrough: 30 to 60 minutes of hands-on work, then a few days while the node checks the whole blockchain. It is written for anyone who wants to check their own transactions and keep their addresses to themselves.

Why Your Own Bitcoin Full Node Matters

The Bitcoin whitepaper describes a peer-to-peer electronic cash system. Peer-to-peer means you interact directly with the network — no intermediaries. But most Bitcoin users today rely on someone else’s infrastructure to broadcast transactions and check balances. That defeats the core design of the protocol.

Running a bitcoin full node restores three properties that Bitcoin was designed to provide. As modern node solutions have made this increasingly accessible, there is less reason than ever to rely on third-party infrastructure:

Financial sovereignty

When you run your own node, you enforce Bitcoin’s consensus rules independently. Your node validates every block and every transaction against the protocol rules. No one can feed you a fake blockchain with altered rules, inflated supply, or coins spent twice. If miners or a majority of other nodes tried to change the rules (increase the 21 million coin cap, for instance), your node would reject those blocks automatically.

This isn’t theoretical. In 2017, a group of companies and miners agreed to double Bitcoin’s block size limit with a hard fork called SegWit2x. Nodes that kept the existing rules would have rejected its bigger blocks. The plan met opposition from users and developers, and on 8 November 2017 its organizers called it off before it activated. How much node operators weighed in that outcome is argued about; what is not in doubt is that your own node decides which blocks you accept. Our lesson Who Enforces Bitcoin’s Rules, and How Do They Change? tells the story.

Independent verification

Without a bitcoin full node, your wallet asks someone else’s server whether a transaction is confirmed. That server could lie. It could tell you a payment was confirmed when it wasn’t. It could show you a wrong balance. It could omit transactions entirely. The probability of this happening is low with reputable wallet providers, but the possibility exists — and in Bitcoin, the entire point is eliminating the need to trust.

“Don’t trust, verify” is not just a slogan. It’s a description of how Bitcoin actually works when you run the software yourself.

Network-level privacy

Every time your wallet connects to a third-party node to check a balance or broadcast a transaction, that node learns your IP address paired with your wallet addresses. Over time, this creates a detailed profile of your financial activity. Public Electrum servers, blockchain API providers, and light wallet backends all collect this metadata, whether intentionally or not.

A bitcoin full node on your home network keeps that information local. Your wallet connects to your own node, and the only thing the broader network sees is that a node at your IP address is relaying blocks and transactions — just like tens of thousands of other nodes.

Don’t Trust, Verify: What a Bitcoin Full Node Actually Does

A bitcoin full node downloads and validates the entire Bitcoin blockchain from the genesis block (January 3, 2009) to the present. On 28 October 2026 that was about 780 GB of block data, growing about 80 GB a year. Here’s what your node does with it:

• Downloads every block from the Bitcoin network, going back to block 0. Your node doesn’t trust any peer: it downloads from several peers at once and checks every block itself.
• Validates every transaction in every block. This means checking digital signatures, confirming inputs haven’t been double-spent, verifying the correct mining reward, and ensuring all consensus rules are followed. During the first sync, Bitcoin Core by default skips the signature checks in older blocks, up to one each release marks as valid (assumevalid); set assumevalid=0 before syncing to check them all.
• Maintains the UTXO set — the current database of all unspent transaction outputs. This is the definitive record of who owns what, and your node builds it independently from the raw blockchain data.
• Relays new transactions and blocks to other nodes on the network. When you broadcast a transaction, your node sends it directly to its peers rather than to a centralized server.
• Rejects invalid data automatically. If a peer sends your node a block that violates any consensus rule, your node drops it and may disconnect from that peer.

The initial sync (called Initial Block Download, or IBD) takes from about a day to several days, depending on your hardware and internet speed. After that, your node stays synchronized by processing new blocks every ~10 minutes — using minimal resources. For a comprehensive guide covering the full process from start to finish, see our guide to running a Bitcoin node for self-sovereignty.

For a deeper look at full node implementation details and best practices, including pruning options and performance tuning, see our technical guide.

Privacy Benefits of Running a Bitcoin Full Node

Privacy is one of the most underrated reasons to run a bitcoin full node. Most Bitcoin wallets leak significant information to third-party servers. Understanding exactly what they leak — and how your own node fixes it — makes the case compelling.

What light wallets reveal

If your wallet uses SPV (Simplified Payment Verification) or connects to a remote Electrum server, the following information is exposed to the server operator:

• Your IP address — linked to your physical location and internet provider.
• All your wallet addresses — the server needs to know which addresses belong to you in order to show your balance.
• Your transaction history — every send and receive, with timestamps.
• Your balance — derived from the addresses you query.
• Your spending patterns — when you transact, how much, and to whom.

This data is a goldmine for chain analysis companies and surveillance entities. Even if the server operator is trustworthy, their logs could be subpoenaed, hacked, or sold.

How your own node protects you

When your wallet connects to your own bitcoin full node, it queries your local copy of the blockchain. No external server ever learns which addresses belong to you. Your wallet’s queries stay on your own hardware, on your own network.

Combined with proper UTXO management and coin control, running your own node is the foundation of a private Bitcoin setup. Without it, every other privacy measure is partially undermined by the metadata you leak when checking balances or broadcasting transactions.

For those seeking maximum financial privacy, pairing your node with advanced UTXO management techniques creates a defense-in-depth approach that’s difficult to penetrate with surveillance tools.

Hardware Requirements for a Bitcoin Full Node

Running a bitcoin full node doesn’t require expensive or specialized hardware. A basic setup uses less electricity than a light bulb. Here are the specifications:

Component	Minimum	Recommended
CPU	Raspberry Pi 5 (quad-core ARM)	Quad-core x86 (Intel N100 or better)
RAM	4 GB	8 GB
Storage	2 TB SSD (1 TB is nearly full)	2 TB NVMe SSD
Internet	25 Mbps download, unmetered	100+ Mbps, unmetered
Power	5–10 W (Raspberry Pi)	15–25 W (mini PC)
Operating system	Linux (64-bit)	Linux (64-bit) or node OS

Storage is the critical component. Bitcoin’s blocks took about 780 GB on 28 October 2026 and grow by about 80 GB a year (blockchain.com). Your node also keeps undo data (what it needs to reverse a block if another chain wins) and its list of unspent coins, the UTXO set, so a synced node takes about 900 GB. A 1 TB drive is already nearly full: about 100 GB left, roughly a year of growth, and no room for an Electrum server’s index. Buy 2 TB. A 2 TB drive gives you room for the blockchain plus additional software like a Lightning node, Electrum server, and block explorer, which node operating systems such as Umbrel and StartOS offer as apps.

Use an SSD, not a hard drive. The initial blockchain sync involves billions of random read/write operations. On a spinning hard drive, this can take weeks and may never complete reliably. On an SSD, it takes from about a day to a few days. NVMe is faster than SATA, but either works.

Choose a Raspberry Pi 5 or a mini PC. Umbrel recommends the Pi 5 and calls the Pi 4 “fine for tinkering”, because USB drives can make a Pi 4 crash. An Intel N100 mini PC, with the SSD inside, syncs faster (about a day or two instead of two to four days) and has room for an Electrum server and Lightning. For a deeper look at the hardware, see our node hardware requirements guide.

Software Options for Running a Bitcoin Full Node

You have two categories of choice: run Bitcoin Core directly on Linux, or use a node operating system that provides a graphical interface and app ecosystem. Both approaches result in a validated bitcoin full node. The difference is user experience. The evolution of self-sovereign infrastructure options has made running a node more approachable than ever.

Bitcoin Core (command line)

Bitcoin Core is the reference implementation of the Bitcoin protocol. It’s the most battle-tested, most peer-reviewed, and most widely deployed node software. Running Bitcoin Core directly on a Linux machine gives you maximum control, minimum overhead, and no dependencies on third-party software stacks.

The tradeoff: you manage everything through the command line and configuration files. There’s no graphical dashboard, no app store, and no one-click Lightning setup. For users comfortable with Linux administration, this is the gold standard. For a detailed walkthrough of verifying and installing Bitcoin Core, including signature verification, see our dedicated guide.

Umbrel

Umbrel is the most popular node operating system, and for good reason. It provides a clean web-based dashboard, a built-in app store with hundreds of self-hosted applications, and a straightforward setup that takes 30 to 60 minutes of hands-on work before the sync. Behind the interface, it runs Bitcoin Core inside Docker containers.

umbrelOS runs on a Raspberry Pi 5 (Umbrel’s recommendation) or Pi 4 and on 64-bit Intel or AMD machines, mini PCs included. Umbrel also sells its own box with umbrelOS installed, the Umbrel Home^[#aff] (Intel N150, 1, 2 or 4 TB NVMe; from $499, checked 3 November 2026). If you buy one, choose 2 TB or more: on Umbrel, 1 TB is already too small for Bitcoin Node and its indexes. Its app ecosystem includes Lightning (LND), Electrum server, block explorer, BTCPay Server, and dozens of non-Bitcoin applications. The downside: Docker adds overhead and complexity. If something breaks inside a container, debugging requires Docker knowledge.

Start9

Start9 runs its own operating system called StartOS, designed from the ground up for self-hosting. Since version 0.4, StartOS runs each service in its own LXC container rather than in Docker, with a custom dependency management system that gives you granular control. The trade-off is a smaller app ecosystem. StartOS installs on your own x86-64, ARM64 or RISC-V machine, or on a Raspberry Pi 4. Its docs say other Pi models are not supported.

Start9 also sells pre-built hardware with StartOS installed, the Start9 Server One (AMD Ryzen 5 6600H, 2 or 4 TB NVMe), from $899 to $1,399 depending on storage and memory. All four versions were for sale when we checked on 8 November 2026. For a direct comparison of both platforms, see our Umbrel vs Start9 guide.

RaspiBlitz

RaspiBlitz is an open-source node project focused on Lightning Network functionality. It runs on Raspberry Pi hardware and provides a terminal-based menu system for managing Bitcoin Core, LND or Core Lightning, and various Lightning tools. RaspiBlitz is ideal for users who want deep Lightning Network integration without the overhead of a full app ecosystem.

The setup process is more hands-on than Umbrel or Start9, with a character-based menu interface rather than a web GUI. This appeals to technically inclined users who prefer transparency over polish. For a complete walkthrough, see our RaspiBlitz setup tutorial.

myNode

myNode sits between Umbrel and RaspiBlitz in terms of user experience. It offers a web-based interface that’s functional but less polished than Umbrel’s. It includes a free community edition with core Bitcoin and Lightning functionality, plus a paid premium version with additional features and one-click updates.

Check myNode’s site for the current Premium price and terms. If you want a web interface without committing to Umbrel’s ecosystem or Start9’s hardware, myNode is a pragmatic choice.

Before you choose it, check which Bitcoin Core version it installs. myNode v0.3.53, released on 8 November 2026, installs Bitcoin Core 32.1, but installs still on a Debian release before 12 stay on 27.2, which has reached its end of life: Bitcoin Core maintains its latest three major versions, 30 to 32 today (myNode changelog, myNode source, Bitcoin Core life cycle).

Step-by-Step Setup with Umbrel

This walkthrough uses Umbrel because it has the lowest barrier to entry while still running a fully validating bitcoin full node. The process applies to a Raspberry Pi 5 or any x86 mini PC.

Step 1: Gather your hardware. You need a computer (a Raspberry Pi 5 with 8 GB of RAM, or an Intel N100 mini PC), a 2 TB SSD (NVMe or USB 3.0), a microSD card of 32 GB or more if you use a Raspberry Pi, an Ethernet cable (Wi-Fi works but wired is more reliable), and a power supply appropriate for your device.

Step 2: Download and flash Umbrel OS. Go to umbrel.com/downloads and download the image for your hardware. For a Raspberry Pi 5 or Pi 4, flash umbrelos-pi.img.zip onto a microSD card of 32 GB or more with balenaEtcher or Raspberry Pi Imager. On a Pi 4, update the bootloader first, as Umbrel’s Raspberry Pi guide explains. For x86 machines, Umbrel’s default is to flash its image onto a USB drive and leave it plugged in, so the internal SSD stays free for apps and data. Its USB installer puts umbrelOS on the internal drive instead.

Step 3: Connect and boot. Insert the microSD card (or plug in the USB drive you flashed), plug in Ethernet, and power on. On a Raspberry Pi, leave the SSD unplugged until setup is done. On a mini PC, umbrelOS uses the internal SSD for apps and data. Umbrel boots automatically and starts its initial setup process.

Step 4: Access the web interface. From any device on the same network, open a browser and navigate to umbrel.local. If that doesn’t resolve, find your node’s IP address in your router’s admin panel and go to http://[IP-address].

Step 5: Create your account. Set a strong password. This protects access to your node’s web interface. If you install the Lightning Node app later, it shows 24 recovery words: write them on paper and store them like any seed.

Step 6: Wait for Initial Block Download. Install Bitcoin Node from the Umbrel App Store. On a Raspberry Pi, plug in your SSD and move Bitcoin Node onto it straight away, because umbrelOS keeps apps on the microSD card by default. In the app’s settings, choose Storage, then App storage, then Move. The drive must be formatted as ext4. Bitcoin Node then downloads and validates the entire Bitcoin blockchain. This takes about a day or two on a mini PC with an NVMe drive, roughly two to four days on a Raspberry Pi 5, and longer on a Pi 4. You can monitor progress from the dashboard. Your node is not fully operational until IBD is complete.

Step 7: Give your wallets a way in. On a mini PC, once IBD finishes, go to the Umbrel App Store and install Electrs (Electrum server in Rust). It indexes the blockchain so your personal wallets can query your own node instead of public servers. Electrs needs to build its own index, about 80 GB, which takes an additional 12–24 hours. On a Raspberry Pi, skip Electrs for now: as of November 2026 umbrelOS can’t move an Electrum server to the SSD, and its index won’t fit on the microSD card. Connect Sparrow straight to Bitcoin Core over Tor instead, as our lesson Setting Up Your Bitcoin Node shows.

Step 8: Connect your wallets. Configure your Bitcoin wallets to use your node. With Electrs on a mini PC, open Settings in Sparrow Wallet, go to the Server tab, choose Private Electrum and enter your node’s local IP address with port 50001. In BlueWallet, go to Settings → Network → Electrum Server and enter the same details. Each wallet handles the connection differently, but the concept is the same: point the wallet at your node’s Electrum server.

Step 9: Verify the connection. Send a small transaction and confirm it appears in your wallet via your own node. Check the Umbrel dashboard to verify your node is fully synced and connected to peers. By default Bitcoin Core keeps 10 outgoing connections (8 that relay transactions and blocks, 2 that relay only blocks); incoming connections come on top if your node accepts them.

Step 10: Install updates yourself. Nothing on Umbrel updates on its own: neither umbrelOS nor its apps install updates automatically. Check at least once a month, umbrelOS in Settings → Software update and apps under Updates in the App Store; each takes one click. In November 2026, Lightning nodes on Linux should run umbrelOS 2.0.1 or later and Lightning Node 0.21.6 or later, as our security advisories explain.

Running Your Bitcoin Full Node Over Tor

Connecting your bitcoin full node through the Tor network adds a significant privacy layer. Without Tor, your ISP can see that you’re running a Bitcoin node, and the nodes you connect to can see your home IP address. With Tor only, your node’s traffic is routed through encrypted relays: peers no longer see your IP address, and your ISP sees only that you use Tor.

Why Tor matters for node operators

Your home IP address is tied to your physical location and real identity through your ISP. When your node connects to other nodes, those peers see your IP address. If any of those peers are run by chain analysis firms, state actors, or malicious entities, they can correlate your node’s IP with the transactions it broadcasts.

Tor eliminates this correlation by routing all connections through the Tor network. Your node gets a .onion address — a cryptographic identifier that reveals nothing about your location or identity.

Setting up Tor

Node platforms offer Tor, but Tor switched on doesn’t mean Tor only. As of November 2026, Umbrel’s Bitcoin Node app connects to peers over clearnet, Tor and I2P by default, and StartOS uses every network it can reach, so clearnet peers still see your home IP address. To hide it, untick Clearnet under Outgoing Peer Connections in Umbrel’s Peer Settings, or select only onion under Onlynet in StartOS’s Peer Settings. Our lesson Network Privacy: Tor, VPNs and Your Own Node shows the steps for each platform.

For Bitcoin Core running on bare Linux, you need to install Tor separately, then add these lines to your bitcoin.conf file:

proxy=127.0.0.1:9050
listen=1
bind=127.0.0.1
onlynet=onion

The proxy line sends every connection through Tor, and onlynet=onion makes your node pick only .onion peers, so nothing leaves through a Tor exit relay. For a hybrid node, replace those two lines with onion=127.0.0.1:9050: Tor is then used only for .onion peers, and ordinary peers connect directly and see your IP address. The listen and bind lines let other nodes reach yours through its own .onion address, which Bitcoin Core creates only if it can use Tor’s control port; Bitcoin Core’s Tor guide shows the lines to add to Tor’s settings.

Tor tradeoffs

Running over Tor adds latency, and the initial sync is slower. You can run IBD over clearnet for speed and switch to Tor-only once the node is synced. During the sync, peers see your IP address and your ISP sees that you run a node. Tor connections also have lower bandwidth, which means your node may relay fewer transactions — but this has no impact on validation or your personal use.

For the privacy-conscious, the latency tradeoff is well worth it. Combined with proper home node configuration, Tor makes it extremely difficult for outside observers to link your Bitcoin activity to your physical identity.

Real Costs: Hardware, Electricity, and Bandwidth

Running a bitcoin full node is one of the cheapest sovereignty tools available. Here’s an honest breakdown of what it costs in 2026:

Hardware costs

Setup	Cost	Notes
Budget (Raspberry Pi 5 + SSD)	Check current prices	Raspberry Pi 5 (8 GB) + 2 TB USB SSD + case + official power supply
Recommended (mini PC)	Check current prices	Intel N100 mini PC + 2 TB NVMe SSD
Pre-built (Umbrel Home)	From $499 (Nov 2026)	Umbrel’s own box: Intel N150, 1, 2 or 4 TB NVMe (choose 2 TB or more), umbrelOS pre-installed
Pre-built (Start9 Server One)	$899–$1,399 (Nov 2026)	AMD Ryzen 5 6600H, 2 or 4 TB NVMe, StartOS pre-installed and configured. All four versions were for sale on 8 November 2026
Repurposed hardware	The price of a 2 TB SSD	Old laptop or desktop with the SSD inside. Free apart from the drive if you already have the computer.

We don’t quote prices for the do-it-yourself builds: they moved a lot in 2026, and Raspberry Pi raised the price of its boards several times as memory got more expensive. Check current prices before you buy, and compare them with the pre-built boxes above, which arrive assembled and set up.

Electricity costs

A Raspberry Pi with its SSD draws about 5–10 watts. An Intel N100 mini PC draws 15–25 watts under typical load. At about 18 cents per kWh, the average U.S. household price the EIA forecasts for 2026:

• Raspberry Pi: about $8–$16 per year
• Intel N100 mini PC: about $24–$40 per year
• Repurposed desktop: about $50–$100 per year (higher idle power draw)

A mini PC running day and night costs about $2 to $3.30 a month. To work it out for your own device and rate, multiply its watts by 8.76 to get kilowatt-hours a year, then multiply by your price per kWh.

Bandwidth costs

After the first sync, a bitcoin full node downloads around 20 GB a month, about 650 MB a day, for new blocks and transactions. Uploads are what grow: bitcoin.org notes that “it’s common for full nodes on high-speed connections to use 200 gigabytes upload or more a month”, mostly because other nodes download blocks from yours, and more so if you allow incoming connections.

For most home internet plans with unlimited data, this is negligible. If you have a metered connection, configure maxuploadtarget in your Bitcoin Core settings to reduce uploads. It sets a daily target, not a hard limit: near the target, your node stops serving blocks more than a week old, but it still relays new blocks and transactions.

Total annual cost

For a typical recommended setup: the one-time cost of a mini PC and a 2 TB SSD, plus about $24–$40 per year in electricity at U.S. household prices. That’s the total cost of financial sovereignty and privacy. No subscriptions, no recurring fees, no dependence on third-party services.

Common Mistakes When Running a Bitcoin Full Node

These are the errors that come up again and again with first nodes:

• Using an HDD instead of an SSD. The single most common reason for failed initial syncs. Hard drives cannot handle the random I/O patterns of blockchain validation. Your sync will crawl for weeks or stall. Use an SSD — no exceptions.
• Running on Wi-Fi during initial sync. Wi-Fi introduces packet loss and variable latency. During IBD, your node downloads about 800 GB, and dropped connections slow the sync. Use Ethernet for the initial sync and, if you run Lightning, keep it: Wi-Fi drops can disrupt your channels.
• Not connecting wallets to the node. Setting up a bitcoin full node but continuing to use public Electrum servers or your wallet’s default backend defeats the purpose. Install an Electrum server (Electrs or Fulcrum) and configure every wallet to connect through your node; on a Raspberry Pi running Umbrel, connect Sparrow straight to Bitcoin Core instead.
• Ignoring updates. Bitcoin Core releases contain bug fixes, performance improvements, and occasionally critical security patches. Running outdated node software doesn’t just put you at risk — it can cause compatibility issues with newer network features.
• Exposing the RPC interface. If you open Bitcoin Core’s RPC port to the internet without proper authentication, anyone can interact with your node. Keep RPC access restricted to localhost or your local network, and always set strong RPC credentials.
• Undersized storage. A 512 GB drive can’t hold today’s blocks at all, and a 1 TB drive has about a year of room left, because a synced node already takes about 900 GB (October 2026). Buy 2 TB.
• Forgetting about UPS. Power outages during blockchain writes can corrupt the database. A basic UPS, a battery that rides out short power cuts, protects your node and prevents hours of reindexing. This is especially important for Raspberry Pi setups with external SSDs.
• Running pruned mode and expecting full functionality. Pruned nodes validate everything but discard old block data to save disk space. This works for personal verification, but pruned nodes can’t serve historical blocks to other nodes, and Electrs and Fulcrum, the Electrum servers most guides use, need the full blockchain. Know the tradeoffs before enabling pruning.

Frequently Asked Questions

Does running a bitcoin full node make me money?

No. A bitcoin full node validates and relays transactions but does not earn block rewards or transaction fees — that’s mining. Running a node is about sovereignty and privacy, not profit. A Lightning node on top of your Bitcoin node can earn small routing fees for forwarding other people’s payments. For most hobbyists, a small node earns little or nothing once you count hardware, electricity, channel fees and your time, so treat any fee income as a bonus. Our lesson Running a Lightning Node does the arithmetic.

Can I run a bitcoin full node on a Raspberry Pi in 2026?

Yes. A Raspberry Pi 5 with 8 GB of RAM and a 2 TB SSD on USB 3 (not the microSD card) syncs in roughly two to four days. Umbrel recommends the Pi 5 and calls the Pi 4 “fine for tinkering”, because USB drives can make a Pi 4 crash; for a node that will hold Lightning funds, choose a Pi 5 or a mini PC. An Intel N100 mini PC syncs faster, in about a day or two, and on Umbrel it can also run an Electrum server, which a Pi that runs umbrelOS from a microSD card, as Umbrel recommends, can’t do for now.

How long does initial blockchain sync take?

Sync time depends primarily on your CPU and storage speed. On a mini PC with a fast NVMe drive and a solid internet connection: about a day or two. On a Raspberry Pi 5 with an SSD: roughly two to four days; a Pi 4 takes longer. Over Tor only, it takes longer still. The sync is a one-time process. After completion, your node stays current by processing new blocks every ~10 minutes, which uses minimal resources.

Does running a node use a lot of internet bandwidth?

After the first sync, a bitcoin full node downloads around 20 GB a month. During initial sync, it downloads the entire blockchain (~780 GB as of 28 October 2026). After sync, if you allow inbound connections (listening on port 8333), your upload usage increases as you serve data to other nodes; 200 GB or more a month is common on fast connections. You can limit this with the maxuploadtarget setting. On an unlimited home internet plan, bandwidth is not a concern. On a metered connection, configure upload limits and consider running without inbound connections.

What’s the difference between a full node and a pruned node?

A full archival node keeps the entire blockchain history on disk (~780 GB as of 28 October 2026). A pruned node validates the complete blockchain during sync but discards old block data afterward, keeping only the most recent blocks (configurable, minimum ~550 MB) plus the UTXO set, roughly 15–20 GB in all. Both validate every transaction identically — pruning does not reduce security. The difference is that a pruned node can’t serve historical blocks to new nodes joining the network, and some software like Electrs requires a full archival node. If you have the storage space (we recommend 2 TB), run an archival node to support the network. If storage is constrained, pruned mode gives you full verification in a fraction of the disk space.

Related Resources

• Bitcoin Full Node Setup: Best Practices — technical deep dive into node implementation, performance tuning, and pruning configuration.
• How to Verify a Bitcoin Core Download (SHA256 and GPG) — how to verify Bitcoin Core downloads and understand the software’s security model.
• Umbrel vs Start9: Which Node Software? — detailed comparison of the two most popular node operating systems.
• Home Bitcoin Node: Privacy and Setup Guide — practical considerations for running a node at home, including network configuration and privacy.
• Lightning Node Setup: Personal Operation Guide — how to add Lightning Network functionality on top of your Bitcoin node.
• Run a Bitcoin Node: Full Setup Guide — broader perspective on self-hosting Bitcoin infrastructure.
• Bitcoin Chain Analysis: How Tracking Works — understand what chain analysis firms can see and why running your own node matters for privacy.