Skip to main content

Ledger Hardware Wallet User

This page has not been fully updated to represent the latest state of the Helium Network following the migration to Solana on April 18, 2023.

Video Walkthrough


Installing the Helium-Solana App

Update your Ledger firmware to at least 2.1.0 before you start.

As of now, we are still waiting on Ledger to release our app. Until then, to install you must follow these steps:

  1. Open Ledger Live.
  2. Go to Settings (top right corner)
  3. Click Experimental Features
  4. Enable Developer Mode
  5. Install the Helium-Solana app as you normally would.
  6. Close Ledger Live

Migrating

The following utility will migrate all tokens from the Helium derivation path 44'/904'/n'/0' to the Solana derivation path 44'/501'/n'/0'.

Ledger users will need to update their Helium Ledger App to a version that's pending release. This upcoming version will use the Solana private key derivation path that moves all your tokens and balances over to Solana. You may need to uninstall any Solana Ledger Apps during the Wallet migration process.


Migration Tool

Your public key will change on Solana, but the private key will remain the same. Note this app only works with Chrome, Brave, or other Chromium-based web browsers.

Close Ledger Live

Before starting these steps, close the Ledger Live application or the transactions will fail.

1
Connect Solana Ledger

Open the Solana App on your ledger. Be sure to enable blind signing in the Ledger Settings. Select the account number you would like to migrate. Then click the button below.

Account Number
2
Connect Helium-Solana Ledger
3
Keep Helium-Solana Ledger Connected and Seed Wallet on Solana
4
Sign Transactions with Helium-Solana
5
Sign Transactions with Solana
6
Send Migration Transactions

Derivation Paths and your new Public Key

The Helium Ledger App uses ED25519 keys, similarly to Solana, but at a different derivation path.

This means that, while seed phrases are the same, private keys are different on Solana.

In order to get around this, when you run the migration, the migration application will ask you to use the old derivation path to approve sending all of your Hotspots, tokens, etc. to the new derivation path.