Ledger Nano X review

Consider the workflow: Nano X makes most sense to investigate when a compatible phone connection over Bluetooth is useful to you.

  • USB-C and Bluetooth hardware signing
  • Secure Element with physical confirmation
  • Standard recovery phrase plus optional separate service

Updated

At a glance

Strengths

  • Bluetooth supports compatible mobile signing workflows
  • Physical confirmation helps review signing requests
  • USB-C provides a wired connection option
Show 2 more
  • Works with compatible third-party application workflows
  • Optional recovery service is separate from standard recovery

Trade-offs

  • Bluetooth does not prevent phishing or deceptive approvals
  • Recovery phrase protection remains the user’s responsibility
  • Asset and network support require model-specific checking
Show 2 more
  • Mobile use depends on phone compatibility and charge
  • Network and provider costs vary by transaction

Overview

Who is Ledger Nano X for?

Consider the workflow: Nano X makes most sense to investigate when a compatible phone connection over Bluetooth is useful to you. If you plan to use only USB on a desktop, compare simpler alternatives rather than treating wireless connectivity as an automatic upgrade.

Recovery matters more than convenience: understand your recovery phrase, transaction confirmation and the separate, optional Ledger Recover service. Bluetooth and a Secure Element do not remove phishing, approval or backup risks.

Compare the Trezor Model T and our Nano X versus Model T guide, checking current model support in each case. This is AI-assisted documentation research, not a device test.

What Ledger Nano X does

Ledger Nano X is a hardware signing device with USB-C and Bluetooth connectivity. This Ledger Nano X review focuses on mobile convenience, transaction confirmation, recovery responsibilities and the costs around self-custody. The device helps protect signing keys while compatible software supplies the interface; cryptocurrency balances remain recorded on their respective blockchains.

For example, Bitcoin or Ethereum remains on its respective network. The Ledger device does not contain the coins or replace the blockchain account: it protects the private-key material used to authorize transactions. Companion software can display balances and prepare transactions, while the Nano X is used to review and sign them.

A hardware wallet reduces some forms of key exposure, but it does not eliminate phishing, unsafe approvals, compromised software or the need to protect a recovery backup. Bluetooth is a connection method, not a safety guarantee. Before buying, check the exact asset, network, application and phone or desktop workflow you intend to use.

Key features

  • USB-C and Bluetooth connectivity
  • Secure Element and physical transaction confirmation
  • Companion software and third-party application workflows
  • Optional Ledger Recover service with separate terms and eligibility

Main features

Decision point What it means
Device type Hardware signing device; Bluetooth does not make every use case “cold” or safe.
Connectivity USB-C and Bluetooth. Wireless use depends on a compatible phone workflow and a charged device.
Signing authorization Secure Element and physical confirmation on the device.
Assets and applications Check the exact asset, network and application catalogue before transferring funds.
Companion software Check current official desktop, mobile and third-party application support.
Recovery Standard recovery-phrase workflow; Ledger Recover is optional and separate.

Using Ledger Nano X for everyday transactions

Companion software and device signing

Ledger’s companion software and compatible third-party applications provide the account interface; the Nano X authorizes signatures. A software balance is therefore not the same thing as private keys stored in the app. The device should remain the place where you verify and approve the transaction.

Bluetooth can make a mobile workflow more convenient, but USB-C remains a practical fallback when wireless connection, phone compatibility or battery charge is inconvenient. Check current iPhone, Android, desktop and application requirements before relying on a mobile-only setup. The device’s battery and charging needs are practical considerations, not evidence of a different security model.

How to read a transaction before approving

For a normal Bitcoin or Ethereum transfer, compare the recipient address, amount, selected network and fee with your intention. An Ethereum transaction may also involve a token contract rather than a simple ETH payment. If the application or device shows an unfamiliar chain, address or amount, reject it and investigate rather than assuming the software is correct.

For a decentralised application, approval may grant a contract permission to spend a token, while a transaction may exchange assets, deposit funds or interact with a protocol. Read the permission and contract details shown by the device as far as the supported workflow allows. A familiar website, correct wallet balance or Bluetooth connection does not make an unfamiliar dApp request safe.

Installation and setup

  1. Purchase through an official or authorised channel and inspect the package. Do not use a device or recovery material that appears altered, and do not accept a recovery phrase supplied by another person.
  2. Set the device PIN and generate or record the recovery phrase only as directed by the device. Check every word and store the backup offline. Never photograph, email or paste it into software.
  3. Install companion software from an official source and add only the applications required for your intended assets. Check current compatibility for the exact network.
  4. Receive a small amount first where appropriate, then verify the account, address, network and transaction details on the device before approving.

Ledger Nano X versus other Ledger models

Model Practical distinction What to check
Nano X USB-C and Bluetooth; wireless use depends on the phone and compatible application workflow. Phone compatibility, charging, application support and transaction confirmation.
Original Nano S A separate, older model; it is not another name for Nano S Plus. Current software functionality, recovery guidance and migration requirements.
Nano S Plus A separate model from both Nano X and the original Nano S, generally considered when wired use is sufficient. Current official connectivity, applications and recovery documentation.

Choose Nano X when Bluetooth-supported mobile signing is useful and its supported assets and applications match your needs. Consider Nano S Plus or another device when wireless connectivity is unnecessary, or when a different interface, support lifecycle or recovery approach better fits your threat model. Do not choose from a headline coin count alone.

Who Ledger Nano X suits

  • Users who value Bluetooth-supported mobile signing
  • Self-custody users willing to manage recovery securely
  • People needing its supported assets and applications
  • Users who will verify transactions on the device

Who should consider alternatives

  • Users who do not need wireless connectivity
  • Buyers seeking a different interface or code approach
  • Anyone unwilling to manage a recovery backup
  • Users whose required network lacks suitable application support

Source-based research for this update uses Ledger’s Nano X specification, Bluetooth security explanation, Ledger Recover information and device and application policy. We have not recorded a hands-on test, lab audit or recovery simulation for this update. For a wired alternative, read our original Nano S review; for a different device interface, compare Trezor Model T.

Fees & costs

Device cost versus transaction cost

A hardware wallet is a signing device, not a subscription to free blockchain transactions. Separate the purchase or replacement cost from costs incurred when buying, swapping, staking or moving assets. A transaction preview may include a network fee even when the manufacturer does not charge a separate signing fee.

Cost component What to compare
Device or replacement Current official availability, authentic seller, taxes, shipping and warranty.
Network transaction The selected blockchain, transaction size, congestion and final signing preview.
Buy, sell or swap integration Provider charge, exchange spread, payment method, minimum amount and regional terms.
Staking or optional services Provider or validator costs, eligibility, risks and separate service terms.

A network fee may apply when moving cryptocurrency, depending on the selected blockchain and transaction. Compare the final amount received, not only an advertised fee. A swap can involve provider charges and network fees, potentially on more than one chain. Staking through a supported application introduces provider and network risks; owning the device does not establish eligibility or guarantee a return. Read the current provider quote and official documentation before signing, and do not use an old review’s price or asset count as today’s offer.

Safety & risks

Bluetooth is a connection, not a security guarantee

Ledger describes the Secure Element and physical confirmation as central to Nano X signing authorization. Bluetooth transports communication between the device and compatible software; it does not make an unsafe transaction safe. A malicious website can still ask a legitimate hardware wallet to approve a deceptive transfer, contract interaction or token permission.

  • Check the destination, network, amount and supported transaction details on the device.
  • Use official device and companion software, and treat unexpected firmware prompts cautiously.
  • Keep recovery words out of websites, chat messages, screenshots and ordinary software forms.
  • Understand permissions before connecting to DeFi, NFT or other third-party applications.
  • Keep a secure backup and a practical wired option if the mobile workflow is unavailable.

Recovery and passphrase decisions

The recovery phrase controls access to the wallet and must be protected independently of the Nano X. A device PIN protects access to the device; it is not a replacement for the recovery backup. If you use an additional passphrase or hidden-wallet feature, document the recovery arrangement privately and understand that losing the passphrase can make the associated account unrecoverable.

Ledger Recover is optional and subject to separate current terms and eligibility requirements. Review those terms before deciding whether it suits you. It is not interchangeable with the ordinary recovery-phrase workflow, device access or a balance shown in companion software.

Hardware signing separates key use from ordinary software, but it does not remove backup exposure, supply-chain risk, phishing or misunderstood application behaviour. This is source-based research, not a lab audit, Bluetooth attack simulation or hands-on recovery test.

Risk Passport

A compact due-diligence snapshot built from tracked evidence. It is not a price forecast or investment advice.

This card summarizes tracked data, not product safety. A high score does not establish solvency, regulatory compliance, security, or a successful hands-on test.

Status
These labels describe the tracked facts in this card. Checked facts can rely on an accepted primary or third-party source; they do not mean that independent sources agree on every claim, or that the product passed a security or hands-on test.
Tracked facts checked
Evidence score
A 0–100 evidence score from a versioned rules model. It combines coverage, source quality and selected signals. It is not a probability of safety, a security audit, a solvency opinion or an investment recommendation.
98 / 100
Tracked data coverage
The share of this model's tracked fields with available values. 100% covers that limited field set only; it does not mean that fees, custody, KYC, reserves or security have all been assessed.
100%

Last checked Nov 16, 2026

How the evidence score is calculated

What drives the score
Component scores that feed the total. Each row is one dimension of the open scoring model.

  • Evidence coverage 100
  • Data quality 90
  • Development activity 100
Checks and testing scope

Checks & hands-on

Desk checks look at public pages and repos. Hands-on checks need a real device or account run — we leave those Not run until we actually do them.

Desk checks use public pages and repos. Device and account tests stay Not run until TokenScouts records a real hands-on result — we do not invent them.

3 pass · 0 fail · 3 not run · 0 unavailable

  • Pass Firmware / companion repo is public on GitHub Desk check
    Checked from public documentation or URLs without creating an account.
    HTTP 200 Source
  • Pass Official product site responds Desk check
    Checked from public documentation or URLs without creating an account.
    HTTP 200 Source
  • Pass Recovery / seed phrase docs are public Desk check
    Checked from public documentation or URLs without creating an account.
    HTTP 200 Source
  • Not run Device unboxing and first-time setup Hands-on
    Requires a real product run (device, signup, deposit, withdrawal, etc.). We never invent these results.
    Not performed yet — TokenScouts does not invent device/account test results
  • Not run Receive and send a small on-chain transfer Hands-on
    Requires a real product run (device, signup, deposit, withdrawal, etc.). We never invent these results.
    Not performed yet — TokenScouts does not invent device/account test results
  • Not run Firmware update path exercised on device Hands-on
    Requires a real product run (device, signup, deposit, withdrawal, etc.). We never invent these results.
    Not performed yet — TokenScouts does not invent device/account test results
Incident history

Incidents

Curated incident notes with sources. This is a starting checklist, not a complete history. Missing entries are not proof of safety.

Curated incident notes with sources. Newest first — expand for the full curated list.

  • HIGH
    Our editorial priority for attention (low → critical), not an official regulator grade.
    supply chain Ledger Connect Kit supply-chain compromise (2023)

    In December 2023 a malicious release of the Ledger Connect Kit NPM package drained funds from users who interacted with affected dapps. Hardware seed storage was not directly compromised; the attack targeted web connectors.

  • MEDIUM
    Our editorial priority for attention (low → critical), not an official regulator grade.
    policy Ledger Recover feature controversy (2023)

    Ledger Recover optional seed backup feature sparked community concern about firmware update paths and recovery model trust assumptions, even for users who never opt in.

Latest updates

Bounded updates when tracked evidence moves. Replaces only this marked section — not a full article rewrite.
Read the latest weekly update

Verified evidence notes from tracked sources. Updates when material signals change.

November 2026 research update

Ledger Live showed frequent repository activity during the November 2–9 monitoring window. At the end of the period, the repository was recorded with 627 stars and 169 open issues, and its latest verified release tag was live-mobile@4.26.1 (released November 6, 2026, according to the supplied GitHub data). Ledger’s official Nano X page and account-recovery documentation were reachable when checked.

These repository and availability signals do not replace hands-on testing or establish the quality, security, or impact of individual changes. No new device test, audit, incident, fee, or price information was provided in this update.

Release and research notes

Research notes

Short automated notes from public GitHub releases for the linked repo. Useful signal, not a rewrite of this review.

Automated notes from public GitHub releases for the linked repository. Not a full newsroom feed — and not an automatic rewrite of this review.

  • Release live-mobile@4.22.0

    4.22.0 #

    GitHub
Tracked data changes

Tracked changes

Material field-level changes (value or verification status). Market noise below our thresholds is filtered out.

Material moves in the fields we monitor — newest first. Expand for the full tracked history.

  • GitHub open issues 185 188
    Updated GitHub
  • GitHub last push 2026-11-15 2026-11-15
    Updated GitHub
View earlier tracked changes

  • GitHub last push 2026-11-15 2026-11-15
    Updated GitHub
  • GitHub last push 2026-11-15 2026-11-15
    Updated GitHub
  • GitHub open issues 184 185
    Updated GitHub
  • GitHub last push 2026-11-15 2026-11-15
    Updated GitHub
  • GitHub open issues 183 184
    Updated GitHub
  • GitHub last push 2026-11-15 2026-11-15
    Updated GitHub
  • GitHub last push 2026-11-14 2026-11-15
    Updated GitHub
  • GitHub open issues 185 183
    Updated GitHub

  • GitHub last push 2026-11-14 2026-11-14
    Updated GitHub
  • GitHub open issues 183 185
    Updated GitHub

Questions & answers

What does Bluetooth change on Ledger Nano X?

Bluetooth provides a connection for a compatible phone workflow. It does not replace checking and physically confirming transaction details on the device. USB-C can be a practical fallback when the phone, wireless connection or device charge is inconvenient. Secure Element protection and user confirmation do not prevent phishing or deceptive approvals.

Is Ledger’s companion app the same thing as the Ledger device wallet?

No. Companion software supplies the interface for viewing accounts and preparing transactions, while the Nano X is the hardware used to authorize signatures. Balances remain recorded on their respective blockchains, and private-key protection depends on the device and recovery arrangement rather than on a displayed software balance.

How should I check a Bitcoin or Ethereum transaction?

Compare the recipient, amount, selected network and fee with your intention on the device. Ethereum activity may involve token transfers, contracts or permissions rather than a simple ETH payment. For an unfamiliar dApp request, understand what access or action you are authorizing; reject anything that is unclear or inconsistent.

Is Ledger Recover required to use Nano X?

No. Ledger Recover is optional and separate from the ordinary recovery-phrase workflow. It is subject to separate current terms and eligibility requirements. Review those terms before deciding whether it suits you, and do not treat it as interchangeable with keeping and protecting your own recovery phrase.

Is Nano X the same device as Nano S Plus?

No. Nano X and Nano S Plus are different devices, and the original Nano S is a separate older model. Nano X’s relevant distinction is USB-C plus Bluetooth, while your choice should also consider current application support, phone or desktop workflow, recovery guidance and whether wireless use is actually useful.

Does Nano X eliminate transaction and swap fees?

No. A network fee may apply when moving cryptocurrency, depending on the selected blockchain and transaction. Buy or swap integrations can add charges or spreads, while staking and optional services can have separate costs. Review the full quote, network and final amount received before signing.

Sources

The evidence ledger: each row is a fact, its value, how strongly we trust it, and where it came from. Etherscan rows are observed on-chain contract checks, not a full audit.

How we check evidence — on-chain rows link to the public explorer when a contract is tracked.

Source records · 7 verified · 2 observed · checked independently · not financial advice

View evidence and source links
Field Value Status
Verified = cross-checked or primary source. Observed = seen but not yet confirmed. Conflict = sources disagree. Stale = older than our freshness window.
Source As of
Latest release date 2026-11-12 Verified GitHub 2026-11-16
Latest release live-mobile@4.28.0 Verified GitHub 2026-11-16
GitHub open issues 188 Verified GitHub 2026-11-16
GitHub last push 2026-11-15 Verified GitHub 2026-11-16
GitHub stars 628 Verified GitHub 2026-11-16
Official Site Reachable yes Verified desk_http 2026-11-16
Recovery Docs Reachable yes Verified desk_http 2026-11-16
Official Site Reachable Http Status 200 Observed desk_http 2026-11-16
Recovery Docs Reachable Http Status 200 Observed desk_http 2026-11-16