Overview
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.
How the integration works (architecture)
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]
Step-by-step: Connect tezos wallet ledger nano s to Galleon (How to)
This is a practical flow I use in my testing. Follow these steps in order and pause to confirm each screen on your device.
- Update device firmware and the Tezos app. See firmware updates and apps manager problems.
- Install the Tezos app using your device manager application (the app manager on your desktop).
- Unlock your device and open the Tezos app on it. Keep the app open.
- Open Galleon and choose the option to connect a hardware wallet. Pick the device type that matches your hardware.
- When Galleon shows an address, verify that the address matches the one displayed on your hardware wallet screen before accepting. Always confirm the address on the device.
- To send or delegate, create the operation in Galleon, then confirm the details on the hardware wallet and approve physically.
If something fails at step 3 or 4, go to the troubleshooting section below.
See also: nano-s-setup-step-by-step.
Common problems & fixes (galleon ledger not detecting)
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):
- Is the device unlocked and the Tezos app open? If not, open it.
- Is another manager app occupying the device (blocking the connection)? Close it.
- Is the USB cable or adapter faulty? Try a different, data-capable cable.
- Are you using a compatible OS/browser or the Galleon desktop app? Try the desktop app instead of a browser.
- Is firmware or the Tezos app out of date? Update them.
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.
Tezos ledger delegation: how to delegate safely
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):
- In Galleon, choose the account you want to delegate.
- Select the "Delegate" action and pick a baker (Galleon will show a list or let you enter an address).
- Adjust suggested fee if needed (Galleon often fills this automatically).
- Confirm the delegation operation in Galleon and then review the operation on your device. The device will show operation details — confirm only if the address and amount match.
Two safety notes:
- Delegation does not move funds to the baker. Your private keys remain in the secure element.
- For contract interactions or certain token operations you may be prompted to enable extra options in the Tezos app (for example, contract data or blind signing). Only enable these after you understand the risk.
More on staking and delegation in the staking-delegation guide.
Firmware, apps and verification (tezos ledger troubleshooting)
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:
- Use the device manager application to install updates.
- Never download firmware from unknown sources.
- When a firmware update requires device interaction, pay attention to the device screen prompts and the exact text you are asked to approve.
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.
Seed phrase, passphrase and backup reminders
Two short facts I emphasize to everyone who stores Tezos long-term:
- Treat your seed phrase (12 or 24 words, depending on your device) like the master key to a safe deposit box. Protect it offline and consider a metal backup plate.
- The optional passphrase (often called the 25th word) changes the account derivation. If you use one, note it down securely. Lose the passphrase and you lose access — even with the seed phrase.
Explore recovery workflows: seed-phrase-management, passphrase-25th-word, and how to recover-from-seed.
Advanced tips, multisig and compatibility
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:
- Mobile OTG: some phones require specific USB-OTG adapters and drivers. See usb-otg-bluetooth.
- Bluetooth: if your device supports Bluetooth, be cautious — read the security implications on connectivity-security.
FAQ
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.
Conclusion & next steps
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.
Back to wallet integration hub