This guide explains how to pair a hardware wallet with the Galleon Tezos wallet (desktop) and how to troubleshoot the common issues people run into. I’ve tested this flow on multiple machines and devices. What I want to do is teach you the step-by-step process and show practical fixes when Galleon and your device don't play nice.
Short version: keep the Tezos app installed on your device, have the device unlocked and open to the Tezos app, and use a compatible connection method (USB / USB-OTG). But there’s more to learn. Read on for worked examples and progressive troubleshooting.
Galleon acts as the wallet interface. Your hardware wallet stores the private keys inside a secure element and only signs operations after you confirm them on the device (a physical confirmation step). Galleon builds the unsigned transaction and sends it to the device to be signed. The device never exposes private keys.
Why this matters: an attacker who controls your computer cannot extract private keys — they can only offer a transaction for you to confirm on-device. That’s the model. (Air-gapped signing workflows are possible but outside this basic pairing guide.)
![Device connected - placeholder]
This is a practical flow I use in my testing. Follow these steps in order and pause to confirm each screen on your device.
If something fails at step 3 or 4, go to the troubleshooting section below.
See also: nano-s-setup-step-by-step.
Why won’t Galleon detect my hardware wallet? Short answer: connection, app state, or driver/browser issues. Long answer: read the checklist and worked examples.
Checklist (diagnostic order):
Table: quick fixes
| Symptom | Likely cause | Quick fix |
|---|---|---|
| Galleon shows "no device" | Device locked or wrong app | Unlock device, open Tezos app |
| Device detected but address mismatch | Wrong derivation/passphrase | Verify passphrase and account index |
| Intermittent disconnects | Cable or USB power | Swap cable, avoid hubs |
| Connection blocked | Desktop manager using device | Quit manager, retry |
Worked example (real case):
A colleague saw "no device" on Galleon. The Tezos app on the device was closed. Opening the Tezos app fixed it immediately. Simple, but common.
And yes, closing the desktop manager that was keeping the device busy fixed it for another user. But check the cable first.
If you still see problems, consult the usb-otg-bluetooth, chrome-app-browser-issues and mobile-android-troubleshoot pages depending on your setup.
Delegation keeps your XTZ in your account while letting a baker validate on your behalf. You keep custody. That’s the useful security property.
Step-by-step example (delegation):
Two safety notes:
More on staking and delegation in the staking-delegation guide.
Firmware and app updates close security holes and add compatibility. I recommend updating before first use or when you encounter odd behavior.
How I verify updates:
If an update goes wrong, consult advanced-firmware-recovery and follow the recovery flow. Recovering from firmware issues typically requires your seed phrase, so have your backup plan ready.
Two short facts I emphasize to everyone who stores Tezos long-term:
Explore recovery workflows: seed-phrase-management, passphrase-25th-word, and how to recover-from-seed.
For higher security, consider multi-signature setups. Tezos supports contract-based multisig schemes. Galleon and hardware wallets can participate in multisig flows, but wallet compatibility matters. If you plan this, read multisig-setups first.
Other compatibility notes:
Q: Can I recover my crypto if the device breaks?
A: Yes — if you have a correct seed phrase and passphrase (if used). See recover-from-seed.
Q: What if the company behind the hardware wallet goes bankrupt?
A: Your keys are in the secure element and are recoverable via seed phrase on a compatible device. Store your seed phrase in a safe, redundant way. See lost-device-company-bankrupt.
Q: Is Bluetooth safe for a hardware wallet?
A: Bluetooth adds convenience but also additional attack surface. For long-term cold storage I prefer wired or air-gapped flows. Read usb-otg-bluetooth and connectivity-security.
Q: Galleon is not detecting my hardware wallet — what's the single most common fix?
A: Open the Tezos app on your device and make sure no other application is holding the device connection. Then reconnect.
Getting Galleon working with a hardware wallet is straightforward when you follow the checklist: firmware up-to-date, Tezos app installed and open, the device unlocked, and a healthy cable/connection. In my experience, most "not detected" problems are simple to fix once you run the diagnostic order above.
Read the step-by-step setup if you’re starting from unboxing: setup-unboxing. If you run into errors, the troubleshooting-index and error-codes-index pages are good next stops.
Want a guided walkthrough? Try the step-by-step setup and test with a small amount of XTZ first — it's how I always train new users. Safe storing.