Core web: Why I don't see all of my assets that I'm expecting to see?

Core supports two derivation paths for Ledger: BIP44 and Ledger Live. Connecting a Ledger directly to Core web uses the BIP44 derivation path. For more information, please check out this article to determine which derivation path the funds are on.

Core derives its own Bitcoin network address regardless of how the wallet is set up (a mnemonic or Ledger in Core extension, or a Ledger connected directly to Core web).

Users who have funds in Ledger Live's application WILL NOT see these funds when connecting their Ledger devices to Core extension or Core web due to Core's unique derivation path. If users want to see or use their Bitcoin funds in Core, they will need to send the Bitcoin from Ledger Live to the address seen in Core extension or Core web.

If a user's connected wallet is connected a testnet network, they will not see their mainnet funds. Core web will default to Dark Mode (if not already enabled) and a green banner will be visible indicating that Testnet mode is on.

The wallet that predated Core, the Avalanche Wallet, used dynamic addresses for the X-Chain and the P-Chain. These addresses changed after each use, which caused the total wallet balance of AVAX to be spread across more addresses than the user realized.

Core web's Portfolio page displays the active balance across the top-most derived address on the Avalanche C, X, and P-Chains. This may cause users to see a smaller active account balance, and a larger wallet balance below it (seen in the bottom left of the Core web UI).

These funds are still safe in the wallet, just not on the top-most derived account. To consolidate funds onto the top-most account and make them visible on the portfolio page, users are encouraged to cross-chain transfer the funds back to the C-Chain.