Official Ledger-on-iPhone explainer

How NOVA connects and signs with Ledger on iPhone

NOVA uses Apple's native iOS 18 accessory picker to authorize a nearby Bluetooth Ledger, discovers standard Solana accounts, imports only public account data, and sends supported signing requests back to the hardware device.

Connection flow

Pair, discover, import, then sign

1

Authorize with Apple's picker

NOVA asks AccessorySetupKit for matching Bluetooth service profiles. The system picker handles discovery and user authorization; NOVA then uses Core Bluetooth for the transport.

2

Discover Solana addresses

With the Solana app open, NOVA reads account indices 0 through 4 by default using the standard 44'/501'/index' derivation pattern and retries transient device timing failures.

3

Import public account data

The selected address is stored as a view-style wallet marked hardware-backed. NOVA retains the account index and preferred device binding; signing remains a Ledger operation.

Current route matrix

Hardware support is action-specific

RouteCurrent source statusImportant boundary
Solana message signingHardware path presentThe request is sent to the selected Ledger account index and still requires device approval.
Direct SOL transferUnsigned transaction builder plus Ledger signingNOVA omits memo and priority-fee instructions for Ledger compatibility in this path.
SPL-token transferSupported with route limits“Send max” is not supported for Ledger token transfers.
SwapSupported when the provider route can be prepared for external signingQuick-swap and incompatible transaction routes can be rejected; try the full swap surface or another route.
Native stakingNot claimed as user-reachableLower-level Ledger stake builders remain in source, but the current native staking feature and navigation were removed.
Privacy Cash transferNot supported for hardware walletsUse a software wallet only after evaluating that separate custody and privacy tradeoff.
Safari extension signingNot supportedHardware accounts can sync for visibility, but the current Safari signing footer restricts signing to software wallets.
Hyperliquid bridge deposit or withdrawalNot supported yetDo not assume Solana transaction support extends to every app-specific signing path.
Nyomi trigger, prediction, cleanup, and generic action pathsSeveral hardware-signing hosts are not wiredNyomi can inspect some hardware-wallet state or start connection, but capability availability is checked per action.

Declared device profiles

What NOVA's picker knows how to discover

Nano X

Bluetooth service profile declared in current source.

Stax and Flex

Separate Bluetooth service profiles and product labels declared.

Nano Gen5

Normal and recovery-mode profiles declared. Recovery mode is recognized and blocked until the device returns to normal mode.

This is a source-level compatibility declaration, not a completed hardware matrix. Firmware, Ledger Solana app version, iOS version, Bluetooth state, transaction shape, and route provider can change an actual result.

Evidence and corrections

What this page proves—and what it does not

The connection, account discovery, device profiles, import bookkeeping, signing path, and route exclusions come from current NOVA source. Apple documents the system accessory picker and Ledger documents its Solana hardware-wallet security model. This page does not prove a Bluetooth session, firmware combination, imported account, readable device display, signature, provider acceptance, broadcast, or finality.

  1. Apple AccessorySetupKit documentation
  2. Apple accessory picker documentation
  3. Ledger's official Solana wallet guide
  4. Solana Foundation wallet directory
  5. Official NOVA U.S. App Store listing
  6. NOVA proof and correction methodology

This page applies only to NOVA - Solana Wallet, App Store ID 6753857720, published by 404 ENTERPRISES, LLC.

Send factual corrections to hi@nshield.org. Never include a recovery phrase, private key, PIN, pairing secret, or signing payload.

View NOVA on App StoreRead transaction checks