All articles
Address hierarchy
When using the default settings, Trezor Suite connects to SatoshiLabs’ open-source backend Blockbook, which also serves a blockchain explorer.
Backend settings can be changed via Settings > Coins, and then clicking on the settings gear icon for a particular coin, which is revealed on hover; e.g. for Bitcoin:
Clicking this reveals the Backends window:
On discovery, Trezor Suite first shuffles the default addresses randomly and takes them one by one until a successful connection is made. This is expected behavior that prevents overflow of one specific connection.
If you have enabled Tor and are running a node over the onion router, your custom backend connection will automatically attempt to connect to .onion addresses first.
Custom backends can be setup using the drop-down menu at the top of the Backends window:
Learn more about setting up custom backends in Trezor Suite in the following articles:
- Custom backend in Trezor Suite
- Full node via Electrum server
- Custom backend in Trezor Suite
- Full node via Electrum server
The backend address hierarchy in Trezor Suite is implemented in such a way that if you have set up multiple custom backends, Trezor Suite will:
- Immediately try to connect to the first local custom address listed.
- If unsuccessful, Suite will cycle through any remaining localhost addresses.
- If localhost addresses are unsuccessful, Trezor Suite will then search for Tor addresses.
Trezor users can connect to their own node when using the Trezor Suite desktop app, but not the web application.