Core Wallet is Ava Labs’ self-custody cryptocurrency wallet associated with the Avalanche ecosystem. It provides an interface for sending, receiving and managing supported blockchain assets and connecting to compatible decentralized applications (dApps). It is neither a blockchain nor an exchange: assets are recorded on their respective networks, not stored inside the application. It is also distinct from Bitcoin Core, the separate Bitcoin full-node software that includes wallet functionality.
How It Works
When a user sends assets through Core Wallet, the interface prepares a transaction specifying details such as the destination, network and amount. The wallet’s signing mechanism uses cryptographic keys to authorize the transaction. The signed transaction is submitted to the relevant network for processing and confirmation. A valid signature does not establish that the recipient or application is trustworthy.
Receiving assets requires a suitable public address on the correct network, not disclosure of private keys or recovery credentials. The wallet displays balances based on blockchain records. Knowing an address may let someone inspect its public activity, but does not give them authority to spend its assets.
Advertising: The following FinchTrade promotion opens a form to request a FinchTrade demo, not to create or recover a Core wallet. It does not establish any Core-related service or affiliation.
FinchTrade services
Get startedAssets and Application Connections
Core is available through a browser extension, mobile apps for iOS and Android, and a web interface. Its documented native networks include Avalanche C-, X- and P-Chains, Ethereum, Bitcoin and Solana, alongside supported EVM networks and Avalanche L1s. This describes network coverage rather than a promise that every token or operation works identically on every interface.
Core Wallet can connect users to compatible applications in the Avalanche ecosystem. An application may request an account connection, a message signature or a transaction approval. Connecting an account generally reveals its public address; it is not the same as authorizing a transfer. Token spending approvals can separately permit an application to move assets within the approved scope, potentially beyond the immediate interaction.
Core Wallet compatibility depends on the network, asset, operation and interface. Support should not be assumed to be identical across interfaces or to cover every EVM-compatible network. Changing the network view does not move assets between blockchains, and a token displayed on one network is not automatically usable on another.
Self-Custody and Security
Self-custody means users control transaction authorization rather than relying on an exchange to approve withdrawals. With Core Wallet, that control brings responsibility for protecting access and understanding the recovery method associated with the chosen setup. Recovery arrangements can differ, so one password-and-backup procedure should not be assumed to apply to every account. Losing required recovery information may make access impossible to restore.
Self-custody does not guarantee safety or privacy. Phishing, compromised devices and misleading signing requests can still cause losses, and public blockchain activity may be traceable. Users need to check the recipient, network and requested permissions before signing. Security warnings, where available, do not replace these checks.
Setup and Network Checks
Core Wallet setup needs to be understood in relation to the chosen interface and access method. Core documentation distinguishes recovery-phrase, seedless social-login and hardware-device arrangements. These are different ways to establish signing access, so instructions for one arrangement should not be treated as a universal recovery procedure. A backup or login method should be understood before it becomes necessary to recover access.
Receiving an asset also requires selecting the appropriate network and address rather than copying whichever address is most convenient. Core support notes that addresses can differ between Bitcoin, EVM networks and Avalanche X/P-Chains. The sending side must use a compatible network and destination. Displaying several networks in one wallet does not merge their address rules or make an incorrectly routed transfer reversible by support.