- Neon builds a transaction (for NEO or a NEP-5 token contract call).
- Neon sends the unsigned payload to the hardware wallet.
- The hardware wallet displays the transaction details and requires an approval on-device.
- The device returns a signature and Neon broadcasts the signed transaction.
This same flow applies to NEP-5 transfers: Neon builds the smart-contract call; the device signs the transaction that moves token ownership on the blockchain.
Before you start — checklist
- A Ledger Nano S (or compatible hardware wallet).
- Neon wallet desktop app or Chrome build (see the CityOfZion repo above).
- A data-capable USB cable and a working port.
- Firmware and NEO app installed on your device — update firmware only from official sources (firmware-updates).
- Your seed phrase backed up in a secure form (paper + metal backup if possible) — see seed-phrase and metal-backup-plates.
And have patience; the first connection can be fiddly on some systems.
Step-by-step: connect a Ledger Nano S to Neon
Note: UI labels change between releases. Treat this as a guided flow rather than exact button labels.
- Install or open the Neon desktop app (or Chrome build). Repo: https://github.com/CityOfZion/neon-wallet
- On the device, install and open the NEO app (via your device manager). Unlock the device with your PIN.
- In Neon choose the option to add/import an account and select "Connect hardware wallet" (or similar wording). Neon should enumerate addresses derived from the device.
- Pick the address you want to use and add it to Neon. Neon will query the network for balances and token holdings.
- To send NEO or a NEP-5 token, create the transfer in Neon. When you click "Sign" the device will show details — confirm amount and destination on the device screen before approving.
I noticed that the device screen shows only essential transaction details (amount, destination, and sometimes the contract hash). Read the device screen carefully. Why risk it? If the on-device values match Neon, approve; otherwise reject and investigate.
Managing NEP-5 tokens in Neon
NEP-5 is the classic token standard on NEO (NEP-17 supersedes some cases). Many tokens still use NEP-5. Neon maintains a token list and usually allows adding custom tokens by contract hash.
How to add a token (typical steps):
- Find the token contract hash from the token project or a block explorer (verify from multiple sources).
- In Neon open token management and add a custom token by pasting the contract hash.
- Neon will show balances for tokens that conform to NEP-5 (or NEP-17 if supported).
And if a token isn't visible after adding it, double-check the contract hash and the token standard. Use the token project's documentation (or an explorer) to confirm which NEP applies.
Import key vs hardware signing (security trade-offs)
People searching for "ledger nano s neo wallet import key" are often asking whether they can move a private key out of the device into Neon. Technically you can import a private key or WIF into Neon so Neon controls the key in software. But doing that negates hardware security: the key becomes exposed to the host OS and any malware.
Key points:
- Proper hardware-wallet use prevents private key export. If a tool claims to export a device's private key, treat it as malicious.
- Importing keys is convenient (hot wallet) but reduces security. For long-term storage, prefer on-device signing.
If you must import for short-term convenience, move only small amounts and make sure you understand recovery steps (see backup-and-recovery).
Troubleshooting: Neon not detecting Ledger Nano S
Common causes and fixes:
- Cable problem (many cables are charge-only). Try a known good data cable.
- Device is locked or the NEO app is not open on the device. Unlock and open the app.
- Browser/OS issues: some Neon builds rely on WebUSB or U2F (see MDN WebUSB: https://developer.mozilla.org/en-US/docs/Web/API/WebUSB_API). Try the desktop build or a different browser.
- Out-of-date firmware or Neon app. Update both first (firmware-updates).
If "neon wallet ledger nano s" still fails to connect, try another machine and check the Neon repo issues for similar reports. But never share your seed phrase while troubleshooting.
Security checklist and best practices
- Seed phrase: keep offline and backed up in more than one secure location. Think of your seed phrase like the master key to a safe deposit box.
- Passphrase (25th word): powerful but risky. Only use a passphrase if you fully understand that it creates a separate wallet not recoverable from the seed alone — see passphrase-25th-word.
- Buying: obtain devices only from trusted sellers; tampered devices are a real attack vector — see where-to-buy-safely.
- For large sums consider multi-signature (multi-signature) setups or geographic distribution — check multisig-compatibility.
But don't overcomplicate for small balances; security should match the value you're protecting.
Quick comparison table
| Setup |
Private keys stored |
NEP-5 token support |
Recovery method |
Typical use |
| Hardware wallet + Neon |
On device (secure element) |
Yes (Neon UI) |
Seed phrase (offline) |
Long-term holdings, higher security |
| Import private key into Neon |
On desktop (hot) |
Yes |
WIF / seed in software |
Short-term access, trading |
| Mobile wallet |
On phone |
Varies |
Seed phrase / backup |
Convenience, small amounts |
See also: third-party-wallets and backup-and-recovery.
FAQ
Q: Can I recover my crypto if the device breaks?
A: Yes. With a valid seed phrase you can restore to another compatible hardware wallet or a software wallet. See restore-recovery.
Q: What happens if the company behind my hardware wallet goes bankrupt?
A: Your seed phrase is what matters. As long as you control the seed and can obtain a compatible wallet or import to a trusted alternative, funds remain recoverable (see company-risk).
Q: Is Bluetooth safe for a hardware wallet?
A: Bluetooth increases attack surface. For high-value holdings prefer USB or an air-gapped workflow — see connectivity-usb-bluetooth-nfc.
Conclusion & next steps
Using a Ledger Nano S with Neon gives a practical trade-off: Neon provides NEO and NEP-5 UI while the hardware wallet keeps keys isolated. In my testing, on-device signing removes a large class of host-based risks. I recommend testing the whole flow with a small amount, confirming on-device prompts, and backing up your seed phrase before moving larger balances.
For firmware, recovery, and more detailed device setup see firmware-updates, restore-recovery, and seed-phrase. If you run into connection errors, check troubleshooting-connection and chrome-extension-issues.
If you'd like a walk-through of a full receive/send cycle or help adding a specific NEP-5 token, check the Neon repo above and our related guides.
