If users previously used the Avalanche wallet with their Ledger, they may not see all of their funds automatically when connecting the Ledger to Core web.
One potential solution is to ensure you’re on the correct derivation path. To do this…
Make sure the private key and recovery phrase for the account in the Avalanche Wallet are stored safely. The recovery phrase will be needed to log into Core. If users connected to the Avalanche wallet with a Ledger, they will need their Ledger close by to connect to Core.
Ensure that you are using Core extension as this is the only extension that supports assets on the X-Chain and P-Chain.
If you are already using Core Extension, reset the recovery phrase on Core Extension to restart the onboarding process.
Begin the onboarding process into Core Extension with Ledger.
When selecting the derivation path during onboarding, ensure that you select “BIP44” rather than “Ledger Live”.
Complete the onboarding process.
Connect your Core Extension to Core Web to ensure to see if your assets are now viewable.
If you are still experiencing issues, reach out to our product support team through the chatbox on the lower right-hand side of this screen.
The Avalanche wallet used the BIP44 derivation path when connecting Ledger devices. On the Core extension, users are able to choose the derivation path they want Core to use when connecting to their Ledger: BIP44 or Ledger Live. Core extension will choose the Ledger Live derivation path by default.
When Core extension uses the Ledger Live derivation path, users will be able to see their Ledger Live natively stored assets that are on an EVM chain if the applicable network is added to Core. However, they might not see the full history of X and P chain activity that was done through the Avalanche Wallet.
If this happens, users can disconnect their Ledger from Core extension by clicking the “Reset Recovery Phrase” option when the wallet is locked and re-setup the wallet with the Ledger by selecting the BIP44 derivation path. For more information, please check out this article.
For any additional questions, please view our other knowledge base articles or contact a support team member via the chat button.