21Relay
Run Your Node

Stage 6 of 7

Improve verification and privacy

Your own node removes a third party from routine blockchain queries, but it does not make Bitcoin activity completely anonymous.

  1. 1Choose setup
  2. 2Check hardware
  3. 3Install
  4. 4Synchronise
  5. 5Maintain
  6. Improve privacy
  7. 7Troubleshoot

Verification path

Wallet
Personal node
Bitcoin network

The verification path

Wallet → personal node → Bitcoin network

Your wallet asks your node for balances, history and transaction broadcast. Your node validates the chain and communicates with peers.

What improves

You rely less on an external wallet server that could associate your addresses and queries. You also verify confirmations under your own node's rules.

What does not disappear

Public transaction patterns, address reuse, network observers, device compromise and counterparties can still reveal information.

Essential beginner protections

  • Connect wallets only over localhost or a trusted private network
  • Keep RPC bound to localhost unless a secured private design requires otherwise
  • Never publish RPC cookies, usernames or passwords
  • Do not expose RPC or unrestricted management ports to the public internet
  • Use a host firewall and install security updates
  • Avoid address reuse where the wallet supports fresh receive addresses
  • Use encrypted, authenticated remote access rather than router port forwarding

RPC security warning

  1. 1

    Treat RPC credentials as high privilege

    A client with valid RPC access may control the node, read private data and potentially operate loaded wallets.

    Warning: Bitcoin Core's official documentation says not to expose RPC over the public internet; RPC authentication is not transport encryption.

  2. 2

    Prefer local cookie authentication

    For software on the same trusted machine, Bitcoin Core's automatically generated cookie is preferred.

  3. 3

    Use system-level isolation

    For multi-application setups, restrict operating-system users, containers and network reachability rather than assuming RPC whitelists are a complete security boundary.

Optional advanced privacy

Tor for peer traffic

Bitcoin Core can use a Tor SOCKS proxy and can operate an onion service. Follow current official Tor documentation and understand DNS and multi-network correlation caveats.

Private remote access

Use a properly configured VPN or SSH tunnel into the home network. Do not directly forward RPC or the Umbrel management interface from the router.

Wallet discipline

Coin control and avoiding unnecessary input consolidation can reduce linkage, but require careful transaction management.

Official sources

Stage progress

Mark this stage complete when you are ready to continue.