Electrum server vs Bitcoin full node
A full node validates the chain. An Electrum server indexes it for wallets. They solve different problems — stacking both has a cost.
Marketing blurbs mash “run your own node” into one glowing box. Operators then install Bitcoin Core, wonder why Sparrow/Electrum still talks to random servers, and install five more services on a 4GB Pi. This page separates the layers — without wallet shilling or seed handling.
Layer 1 — Bitcoin Core (the full / pruned node)
Bitcoin Core downloads and verifies blocks. It enforces consensus. It answers: “Is this transaction valid in my view of the chain?” A pruned node still validates; it discards old block files afterward. See pruned vs full.
Core’s RPC is for local tools and status — keep it on localhost (security basics). Core does not ship a convenient per-address history API the way block explorers do.
Layer 2 — Electrum server / electrs (optional indexer)
Electrum-protocol servers index the chain so light wallets can ask “history for this script?” without trusting a public server. Common self-hosted options include electrs and similar indexers. They typically require:
- A synced Bitcoin Core instance (often with
txindexor indexer-specific requirements — read current electrs docs) - Extra disk for the index
- Extra RAM and CPU during initial index build
Until the index is built, wallets pointed at your server will not magically be “private and fast.” Budget time like a second IBD-ish wait.
This site does not walk through wallet recovery, seed backup, or custody. Keep keys on hardware wallets or offline workflows you already trust. The node and indexer are verification and query infrastructure — not a place to store backups.
Who needs which
| Goal | Need Core? | Need Electrum server? |
|---|---|---|
| Learn / verify chain rules | Yes (pruned OK) | No |
| Stop using public explorers for wallet history | Yes | Usually yes |
| Broadcast via your node only | Yes + wallet that supports it | Depends on wallet |
| Lowest power Pi, Core-only | Yes | Defer — RAM tight |
Still deciding whether any of this is worth it? Do you need a node?
Hardware implications
Our hardware bestpick (N100 + 16GB) leaves headroom for Core + a modest indexer. Raspberry Pi 5 8GB can run Core pruned comfortably; adding electrs is the moment many Pi builds feel small. Used SFF boxes with 32GB RAM are happier multi-service hosts. Appliances (Start9/Umbrel) bundle these stacks — you pay for integration.
Disk: full node + index is a different size class than pruned Core alone. Read disk full & pruned before filling a 500GB drive with two databases.
Privacy honesty
Pointing a wallet at your Electrum server reduces leakage to public Electrum servers. It does not anonymize Bitcoin. Your ISP or VPS provider still sees traffic patterns unless you add Tor and careful wallet behavior. See Tor and privacy.
Operational order (recommended)
- Install and sync Bitcoin Core only — setup
- Live with Core for a week using commands and maintenance
- If your wallet workflow still needs an address index, add electrs (or appliance app) with RAM/disk checked
- Never expose Electrum or RPC ports to the public internet as a “quick fix”
What this site will not do
- Rank wallet brands or promise “best Electrum setup 2026!!!”
- Provide seed phrase UX or recovery scripts
- Pretend an indexer replaces consensus validation
Core remains the foundation. Everything else is optional scaffolding. When configs get sharp, keep defaults conservative in bitcoin.conf reference and the setup sample.
txindex and related Core flags
Some indexers want Core started with extra indexing options. Those flags increase disk use and initial work. Enable them only when a documented dependency requires it — not “just in case.” If you are Core-only for verification, you can ignore them. When disk fills after enabling indexes, use disk recovery habits: stop cleanly, expand or simplify, never delete random chain files.
Troubleshooting the “I have a node but my wallet still phones home” feeling
Wallets choose their own defaults. Installing Core on the same LAN does not automatically redirect every app. You must configure the wallet to use your Electrum server or node connection features. If that sounds like more ops than you wanted, stay on Core-only and use the node for learning and verification tools you explicitly point at localhost. Commands for Core health remain on the commands page regardless of wallet stack.
FAQ
Is an Electrum server the same as a Bitcoin full node?
No. Bitcoin Core validates consensus rules. An Electrum server (for example electrs) builds an address index so Electrum-compatible wallets can query history privately against your machine.
Do I need electrs to run a node?
No. Most people who only want independent verification run Bitcoin Core alone — often pruned. Add an Electrum server only if your wallet workflow needs it.
How much RAM does electrs need?
Plan extra RAM beyond Core. 16GB class machines are more comfortable than 8GB when Core and an indexer share a box. Exact usage varies by implementation and load.