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.
Stage 6 of 7
Your own node removes a third party from routine blockchain queries, but it does not make Bitcoin activity completely anonymous.
Verification path
Your wallet asks your node for balances, history and transaction broadcast. Your node validates the chain and communicates with peers.
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.
Public transaction patterns, address reuse, network observers, device compromise and counterparties can still reveal information.
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.
For software on the same trusted machine, Bitcoin Core's automatically generated cookie is preferred.
For multi-application setups, restrict operating-system users, containers and network reachability rather than assuming RPC whitelists are a complete security boundary.
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.
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.
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.