This review contains affiliate links. If you buy via these links, I may earn a commission at no extra cost to you. It doesn’t change what I say about the product.
I’ll be honest about where I’m coming from before I tell you anything about this device. I’m a Bitcoin-only person. I’ve been self-custodying since 2017, I run a full node at home, and I use a Coldcard as my primary signing device. That context matters because the Ledger Nano X is, in many ways, built for a different kind of user than me — and I want to be fair to what it actually is rather than grade it against my own preferences.
I’ve spent time with the Nano X at local Bitcoin meetups, borrowed one from a friend who uses it daily for a mixed portfolio of Bitcoin and a few altcoins, and reviewed this device extensively from Ledger’s public documentation, their GitHub repositories (where code is selectively published), and publicly available security audits. I don’t own one as a daily driver. I’ll note where that matters.
With that out of the way: the Ledger Nano X is not a bad device. For a specific type of user — someone who wants mobile Bluetooth pairing, runs a mix of crypto assets, and trusts Ledger’s Secure Element implementation — it’s competent hardware. The trust tradeoffs are real and worth understanding, but they’re tradeoffs, not disqualifying failures. Let me walk through everything.
What’s in the box and first impressions
The Nano X ships in a sealed box with a USB-C cable, a getting-started card pointing you to Ledger Live, and three paper cards for your seed phrase. The packaging is clean — more consumer electronics than cypherpunk tool, which reflects Ledger’s market positioning accurately. The device itself is aluminum and plastic, roughly 72mm long, and feels more substantial than the older Nano S. The USB-C connector is a welcome upgrade from the Nano S Plus’s micro-USB.
The OLED screen is small — two lines of text, 128x64 pixels. You navigate with two hardware buttons on the top edge. If you’re coming from a touch-screen device, this takes a few minutes to get used to, but it’s not difficult. The left button scrolls backward, the right button scrolls forward, and pressing both simultaneously confirms a selection. Simple enough.
One thing my friend pointed out: the battery. The Nano X has a 100 mAh internal battery for Bluetooth operation, which is good for roughly 8 hours of active use. This is the feature that enables wireless phone pairing, and it matters if that’s your use case. Most other hardware wallets in this price range are bus-powered only.
Setup: Ledger Live, seed generation, PIN
You set up the Nano X through Ledger Live, their desktop and mobile application. The onboarding flow is guided and genuinely beginner-friendly. You create a PIN (4-8 digits), generate a 24-word BIP-39 seed phrase, and write it down on the provided cards. The device generates the seed internally and displays it word by word on the screen.
A few practical notes from watching someone set this up for the first time. The two-button navigation means confirming each word requires pressing both buttons simultaneously — on a first setup, people frequently mispress and trigger a scroll instead. Not a serious problem, but expect a learning curve of a few minutes. The firmware update during initial setup is mandatory and requires an internet connection through Ledger Live; you can’t skip this, which means first-run requires a connected computer.
The PIN setup is fine. Four digits minimum is less than I’d want, but eight digits is available. The device wipes itself after three incorrect PIN attempts, which is the correct behavior.
Seed verification — where the device quizzes you on your seed phrase to confirm you wrote it down correctly — is part of the guided setup. This is good practice and Ledger implements it well. I’ve seen cheaper hardware wallets skip this step.
On firmware verification: Ledger’s Genuine Check feature, accessible through Ledger Live, uses a cryptographic attestation to confirm the device shipped from Ledger and hasn’t been tampered with at the hardware level. The attestation key is in the Secure Element. This is meaningful supply-chain protection, though it requires trusting Ledger’s attestation infrastructure.
Security architecture: Secure Element, the open-vs-closed question
The Nano X uses an ST33K1M5 Secure Element certified at CC EAL5+. The Secure Element handles key storage, seed generation, and cryptographic signing. In hardware wallet terms, this is the good stuff — EAL5+ is a serious certification, the same class used in bank cards and passports. The seed never leaves the Secure Element in plaintext during normal operation.
Here’s where the conversation gets more nuanced. Ledger’s firmware is closed-source. The Operating System (BOLOS) that runs on the Secure Element is not publicly auditable. The apps that run on top of BOLOS — the Bitcoin app, the Ethereum app — are open source and available on GitHub. But the underlying OS that mediates between your keys and those apps is not.
Ledger’s position has always been that open-sourcing the Secure Element OS would compromise the security certifications and provide a roadmap for attackers. That’s a defensible argument from a certain security model, but it requires trusting Ledger as an organization rather than verifying the code yourself. For many people, that’s an acceptable tradeoff. For Bitcoin-only purists who want to verify the complete stack, it’s not.
The comparison here: Trezor’s entire firmware is open source and independently auditable. Coldcard’s firmware is also open source. Both accept that the tradeoff between transparency and SE certification is worth making differently than Ledger does. Neither approach is obviously wrong — they reflect different threat models and different trust assumptions.
Bitcoin-specific UX: send, receive, native SegWit, Taproot, PSBT
For day-to-day Bitcoin use, the Nano X performs adequately. The Bitcoin app (version 2.x as of this writing) supports:
- Legacy (P2PKH) addresses
- SegWit wrapped (P2SH-P2WPKH)
- Native SegWit (P2WPKH, bech32)
- Taproot (P2TR, bech32m)
Native SegWit and Taproot support arrived in the Bitcoin app updates in 2021-2022, so the address-type coverage is now solid. In Ledger Live, receiving Bitcoin is straightforward: you verify the address on the device screen (important — always verify on-device), and the address copies to your clipboard.
PSBT (Partially Signed Bitcoin Transaction) support exists, but it’s not the primary workflow Ledger pushes. If you want to use the Nano X with external software like Sparrow Wallet or Electrum, you can. The flow involves connecting via USB (Bluetooth doesn’t work with most desktop wallets for security reasons), putting the device in the Bitcoin app, and letting the external wallet communicate with it via Ledger’s HID protocol. I’ve tested this at meetups and it works, but it’s clearly secondary to the Ledger Live workflow. Sparrow Wallet has first-class Ledger support, which helps.
For multisig, the Nano X can participate as one of N signers, but Ledger Live itself doesn’t offer a native multisig coordinator. You’d use Sparrow or Electrum for that. The device handles the signing correctly once set up.
Lightning support
The Ledger Nano X does not have native Lightning Network support in any direct sense. You cannot run an LN node on the device or hold Lightning channel keys on it directly.
The workarounds people use: Blue Wallet (mobile) can use a Ledger-secured on-chain wallet for channel funding transactions, but the Lightning keys themselves live in the phone’s software. Muun Wallet takes a different approach where it treats Lightning as a UX layer over on-chain transactions, meaning your Ledger can sign the underlying on-chain activity. These are usable compromises but they’re not Lightning hardware wallet support in the way that, say, a dedicated node setup provides.
If Lightning is a primary use case for you, the Nano X is not the right device. For Lightning self-custody, you want a dedicated node solution (Umbrel, Start9, myNode) where you control the channel keys on a full node.
The 2020 data breach: customer database leak
In July 2020, Ledger disclosed that their e-commerce and marketing database had been breached. Approximately 1 million email addresses were exposed, and around 272,000 customers had their full names, postal addresses, and phone numbers leaked. The data appeared on public forums and torrent sites.
This was not a compromise of the hardware wallet firmware or the cryptographic keys. Your Bitcoin was not at risk from this breach if you were using the device correctly. But the implications are real and worth being clear about:
If you ordered a Ledger before mid-2020, your name and home address are likely in a dataset circulating among malicious actors. This is a physical security consideration. People holding significant Bitcoin amounts at known addresses are targets for physical attacks — the so-called “$5 wrench attack.” In the months following the leak, Ledger customers reported targeted phishing emails, phone calls, and in several documented cases, physical threats.
The company’s response was criticized as too slow and insufficiently transparent about the full scope. They eventually offered a bug bounty program and updated their security practices, but the data remains out there.
Practical mitigation for anyone who bought a Ledger pre-2020 and holds significant value: consider a PO box or business address for future hardware purchases, be aware of phishing attempts, and take your physical security posture seriously.
The 2023 Ledger Recover controversy
In May 2023, Ledger announced Ledger Recover — a subscription service (approximately $9.99/month) that would allow users to back up their seed phrase by splitting it into encrypted shards and distributing those shards to three custodians: Ledger itself, Coincover, and an unnamed identity verification provider (later identified as Escrowtech).
The community reaction was immediate and negative, for a specific technical reason: the announcement revealed that Ledger’s firmware was capable of extracting and transmitting seed material from the Secure Element. Ledger had previously given the strong impression that this was architecturally impossible — that the seed never left the Secure Element in any form.
To be precise about what Recover actually does: the seed phrase is split into three encrypted shards using Shamir’s Secret Sharing (SLIP-39 variant), each shard is encrypted with a key that requires identity verification to access, and recovery requires two of three custodians to cooperate. The seed material is transmitted over the device’s USB connection during the backup process, encrypted, to Ledger’s servers.
Ledger’s defense was technically accurate: the Recover feature is opt-in, requires user action and identity verification, and the seed is encrypted before leaving the device. But the controversy revealed something more fundamental: the firmware architecture allows seed extraction in principle. Whether this capability could be activated without user consent (through a malicious firmware update, for example) became a serious open question. Because the firmware is closed-source, there is no way to verify independently that the extraction capability cannot be triggered without explicit user consent.
Ledger subsequently committed to open-sourcing more of their firmware stack, including BOLOS. As of early 2026, partial open-sourcing has occurred, but the full OS is still not publicly auditable.
This controversy doesn’t make the Nano X a bad device for most users. But it materially affects my recommendation for Bitcoin-only holders with high security requirements. If you’re holding significant amounts of Bitcoin and your primary threat model includes nation-state-level firmware attacks, the inability to verify the complete firmware is a meaningful gap.
My honest take: who should buy this, who should look elsewhere
Buy the Nano X if: You hold Bitcoin alongside a variety of altcoins (ETH, SOL, etc.) and want a single device. You want Bluetooth mobile pairing and use Ledger Live’s mobile app. You want a widely supported device with good customer service. You’re not running a paranoid threat model where firmware auditability is required.
Look elsewhere if: You’re Bitcoin-only. The Nano X’s strength — broad altcoin coverage — is irrelevant to you, and the weaknesses (closed firmware, seed extraction capability, customer data breach) are more significant. If you’re Bitcoin-only and privacy-conscious, the Trezor Safe 5 is the better pick: open-source firmware, SLIP-39 Shamir backup, and SatoshiLabs has no firmware-level breach history. If you’re running a maximum-security air-gapped setup, the Coldcard Mk4 is the device the Bitcoin security community converges on.
Look elsewhere if: You ordered a Ledger before mid-2020 and live at the address on that order. Your physical security posture needs reassessment regardless of which wallet you use going forward.
Alternatives
- Trezor Safe 5 review — Open-source firmware, Bitcoin-first UX, Secure Element in the newer model. Better for Bitcoin purists.
- Coldcard Mk4 review — Air-gapped, Bitcoin-only, dual Secure Elements, PSBT-native. Maximum-security option.
- See also: Ledger vs Trezor vs Coldcard comparison for a side-by-side breakdown.
Verdict
The Ledger Nano X is a well-made consumer hardware wallet with genuine advantages in mobile usability and altcoin coverage. The CC EAL5+ Secure Element is real hardware-level protection, and the device works reliably for what it’s designed to do.
The tradeoffs are also real. Closed-source firmware means trusting Ledger’s implementation rather than verifying it. The 2020 data breach left customer physical details in circulation. The 2023 Recover controversy revealed that seed extraction is architecturally possible from the firmware layer. These are facts, not FUD.
My rating of 3.5 out of 5 reflects a device that’s competent for its intended market but carries trust assumptions I personally don’t want to make with my Bitcoin stack. For a general-purpose crypto holder who values mobile convenience and altcoin breadth: the Nano X is fine. For a Bitcoin-only holder optimizing for verifiability and sovereignty: look at the alternatives.
Sources:
- Ledger’s Bitcoin app source code: github.com/LedgerHQ/app-bitcoin-new
- Ledger’s July 2020 data breach disclosure: ledger.com/blog/july-2020-e-commerce-and-marketing-data-breach-update
- Ledger Recover announcement (May 2023): ledger.com/recover
- CC EAL5+ evaluation: ANSSI certification records, public summary
- Sparrow Wallet Ledger integration: sparrowwallet.com/docs/hardware-wallets.html