Skip to main content

Accounts, contacts, and settings

Key sources​

A Core Web wallet can sign with several kinds of account, side by side:

  • Seed-phrase accounts — keys derived from a recovery phrase.
  • Seedless accounts — created with a Google or Apple sign-in; keys are held in a distributed signing service rather than a phrase the user must store. This is also the identity the MCP server authenticates.
  • Core Extension — Core Web can defer signing to the extension.
  • Hardware wallets — see the extension's hardware wallet docs.

Each account exposes addresses across the supported networks; dapps see whichever account the user activates.

Contacts​

A per-wallet address book with names and per-chain addresses, used for send flows and recipient display. With user permission, dapps can read and manage it through the contacts methods — useful for integrations that want to pre-populate known recipients rather than raw hex.

Settings developers touch​

  • Testnet mode — switches every network to its test variant; also switchable by dapps via avalanche_setDeveloperMode.
  • Custom networks — user-added EVM networks, the counterpart of wallet_addEthereumChain.
  • AI connectors — the agent policy.
  • Connected sites — per-dapp permissions, where users revoke access granted through eth_requestAccounts.