In an effort to enhance user privacy and control, Trezor Suite has introduced support for connecting to self-hosted full nodes in its desktop application. With version 22.3.2 and later, users can now link their Trezor hardware wallet directly to any Electrum server, giving them full autonomy over how their blockchain data is accessed. This guide walks you through the importance of running your own node, how to configure Trezor Suite accordingly, and practical steps for integrating with popular node solutions like Umbrel.
Why Connecting to a Full Node Matters
When you use a cryptocurrency wallet, it needs to communicate with the blockchain to check balances and broadcast transactions. Most wallets rely on third-party servers—often run by companies or service providers—to fetch this data. While convenient, this setup introduces privacy risks.
By connecting to your own full node, you eliminate the need to trust external services. Your wallet queries your personal copy of the blockchain, ensuring that no third party can see which addresses you're monitoring or when you're making transactions.
Even if you don’t run your own node, Trezor Suite defaults to backend servers operated by SatoshiLabs using the open-source Blockbook software. These nodes do not log user activity and are designed with privacy in mind—but nothing beats the sovereignty of running your own infrastructure.
👉 Discover how secure wallet integrations empower user control over digital assets
Understanding Full Nodes and Electrum Servers
What Is a Full Node?
A full node is a program that downloads and verifies every block and transaction in the Bitcoin blockchain. It enforces consensus rules independently, contributing to network security by rejecting invalid data. Running a full node means maintaining a complete copy of the blockchain—currently over 500GB—and keeping it synchronized with new blocks.
While powerful, raw node software like bitcoind (Bitcoin Core's daemon) isn’t user-friendly. That’s where tools like Electrum servers come in.
The Role of Electrum Servers
An Electrum server acts as a bridge between bitcoind and lightweight wallets like Trezor Suite. It indexes blockchain data so wallets can quickly retrieve balance histories and transaction records—something bitcoind alone cannot do efficiently.
Trezor Suite supports three backend connection types:
- Default SatoshiLabs-operated nodes
- Custom Blockbook servers
- Custom Electrum servers
Electrum server support is especially valuable because it's widely used in consumer-grade node setups such as Umbrel, RaspiBlitz, and other home node platforms.
How to Set Up a Custom Full Node Connection
To connect Trezor Suite to your own node, you’ll need three pieces of information:
- Address: Your node’s IP address, domain name, or
.onionaddress (for Tor) - Port: The communication endpoint (e.g.,
50001) - Protocol: Either
tfor TCP orsfor SSL/TLS encryption
These are combined into a single string formatted as: address:port:protocol
For example: 192.168.1.100:50001:t
or ex4mpl3avds34zbtf4xustmzei6nlr3g62fz7c7tp7iqemmpwjx7ktad.onion:50001:t
Step-by-Step Setup in Trezor Suite
- Open Trezor Suite Desktop (web version does not support custom backends).
- Go to Settings > Crypto > Bitcoin.
- Hover over the Bitcoin button and click the gear icon.
- From the dropdown, select Custom Electrum Server.
- Enter your connection string in the input field.
- Click Confirm.
You can add multiple custom servers. Trezor Suite will try each one if the primary connection fails.
Once saved, a new backend status icon appears in the top-right corner:
- Yellow dot: Connection pending
- Green dot: Successfully connected
Clicking the icon shows detailed connection status and allows quick access to backend settings.
Connecting via Tor Using Onion Addresses
Using .onion addresses enhances privacy by routing traffic through the Tor network. To connect:
- Use an onion address ending in
.onion - Port number (commonly
50001) - Protocol: Always
t(TCP) for Tor-based Electrum servers
Example: abc123xyz.onion:50001:t
⚠️ Important: You must enable Tor in Trezor Suite before connecting to an onion address. If disabled, the app will prompt you to turn it on. Without Tor enabled, connections to .onion addresses will fail.
If you have multiple backends configured, Trezor Suite automatically switches to non-Tor ones when Tor is off.
👉 Learn more about decentralized finance tools that prioritize user sovereignty
Practical Example: Connecting to an Umbrel Node
Umbrel is a popular self-hosted node platform that runs on devices like Raspberry Pi. It simplifies setting up Bitcoin and Lightning nodes with built-in Electrum server support.
Here’s how to connect Trezor Suite to an Umbrel node:
- On your Umbrel dashboard, go to Connect Wallet > Electrum Server.
- Copy the displayed connection string (in
address:port:protocolformat). - Open Trezor Suite and navigate to Bitcoin backend settings.
- Select Custom Electrum Server and paste the string.
- Confirm and wait for the green status indicator.
Now, all your balance checks and transaction broadcasts go directly through your private node—no intermediaries involved.
Building Your Own Full Node: Options & Considerations
Running your own full node strengthens the Bitcoin network and gives you unparalleled insight into transaction validation. Here are several ways to get started:
Option 1: Install Blockbook Locally
Blockbook) is a blockchain indexer developed by SatoshiLabs. Installable on Debian-based Linux systems, it provides fast balance lookups and integrates seamlessly with Trezor Suite via “Custom Blockbook Server” mode.
Option 2: Buy a Plug-and-Play Node
Companies offer pre-built nodes like NodeZero, Start9 Embassy, or RaspiBlitz kits. These are ideal for non-technical users who want a hassle-free setup but come at a higher cost than DIY options.
Option 3: Build a Raspberry Pi Node
Using a Raspberry Pi 4 or newer with Umbrel OS offers a low-cost, energy-efficient solution. Just ensure sufficient storage (at least 1TB SSD) and stable internet.
Option 4: Run Bitcoin Core on Your PC
While Trezor Suite does not currently support direct Bitcoin Core integration, running bitcoind locally is still a valid way to validate transactions independently. However, without an Electrum or Blockbook layer, it won’t work with most desktop wallets.
💡 Tip: Whichever method you choose, aim for high uptime. Nodes must stay online to stay synchronized and validate new blocks effectively.
Frequently Asked Questions (FAQ)
Q: Can I connect Trezor Suite to my node using the web app?
A: No. Only the desktop version of Trezor Suite supports custom backend connections.
Q: Does connecting to my own node make transactions faster?
A: Not necessarily. Transaction speed depends on network fees and mempool congestion, but your node ensures your transactions are broadcasted reliably without censorship.
Q: Is running a full node expensive?
A: Costs vary. A basic setup using a Raspberry Pi and external SSD may cost $150–$300 upfront, plus ongoing electricity and bandwidth.
Q: Do I need technical skills to run a node?
A: Basic comfort with command-line interfaces helps, but platforms like Umbrel provide intuitive interfaces suitable for beginners.
Q: Can I use multiple Electrum servers at once?
A: Yes. You can add several custom servers; Trezor Suite will automatically failover if one goes offline.
Q: What are core keywords for this topic?
A: Core keywords include Trezor Suite, full node, Electrum server, connect wallet, Bitcoin privacy, self-hosted node, hardware wallet, and Tor connection.
👉 Explore advanced crypto security practices backed by decentralized architecture
Final Thoughts
Connecting your Trezor wallet to your own full node is a powerful step toward true financial sovereignty. It removes reliance on third parties, protects your privacy, and contributes to the resilience of the Bitcoin network.
Whether you’re using a plug-and-play device like Umbrel or building a custom setup, the ability to control your data is now within reach—all thanks to enhanced features in Trezor Suite.
As development continues, expect even deeper integration with self-hosted infrastructure, giving users full command over their digital asset experience.