What if all of my AVAX is not visible when connecting a Ledger to Core web?
What if all of my AVAX is not visible when connecting a Ledger to Core web?
The Avalanche Wallet uses the BIP44 derivation path, and Core extension uses the Ledger Live derivation path by default. If users do not manually select the BIP44 derivation path when setting up their Core extension, they may not see all of the AVAX associated with their wallet.
Users should try clearing their Core extension wallet and reconnecting their Ledger while choosing the BIP44 derivation path. For more information on how to do so, please refer to this article.
Why do the X and P Chain addresses look different? Why is there only 1 address?
Why do the X and P Chain addresses look different? Why is there only 1 address?
In the Avalanche Wallet, the X and P Chain addresses were dynamic and changed after each use. In Core web, they are static and will not change after each use. Users can see the X/P Chain address in the Portfolio.
NOTE: When sending to an X-Chain address seen in Core web, users will need to add the “X-” prefix to the address. Note the capitalization in the prefix.
Why can’t I see my Bitcoin network funds in my Portfolio?
Why can’t I see my Bitcoin network funds in my Portfolio?
Core extension is the only compatible extension option to view your Bitcoin network assets in Core web. As an alternative, users can search their Bitcoin address in the search bar to view the balance if their Bitcoin funds are in a Bitcoin wallet not connected to their currently connected browser extension.
For any additional questions, please view our other knowledge base articles or contact a support team member via the chat button.