EOA support comes to Flow Wallet Extension

Social media

Flow Wallet is meant to feel instantly familiar to anyone in Web3, while still showing off what makes Flow powerful and unique. To do that well, your accounts need to work the way you expect: compatible with other wallets, aligned with EVM standards, and easy to interact with between apps and chains.

That’s why this release is a big one: we’re bringing Externally Owned Accounts (EOAs) to Flow Wallet Extension.

Adding EOAs makes Flow and Flow Wallet feel familiar to anyone coming from Ethereum or other EVM chains, reduces friction when moving between wallets, and keeps Flow Wallet aligned with expected Web3 standards and UX, while still supporting Flow-native features like Cadence accounts and Cadence-owned accounts (COAs).

In version 3.1.0, Flow Wallet Extension now supports three kinds of accounts side-by-side:

  • EOAs
  • Cadence-owned accounts (COAs)
  • Cadence accounts

This support unlocks better compatibility with your other favourite crypto wallets, with familiar mental models for EVM users, and more flexibility for how you use Flow.

Let’s break down what’s new and what you’ll see in the extension after you update.

What’s an EOA on Flow?

If you’ve used Ethereum or other EVM chains, you already know EOAs:

  • They’re derived from a 12-word seed phrase.
  • They have a 42 character 0x... style address.
  • They can be imported/exported across different wallets that support the same derivation path.

With version 3.1.0, Flow Wallet Extension now creates and manages EOAs that work on Flow EVM.

What changes after updating?

After updating to 3.1.0:

  • New users of Flow Wallet Extension will automatically get:
    • An EOA (labelled EVM account)
    • A Cadence account
An EOA account in Flow Wallet
  • Existing users of Flow Wallet Extension will now see:
    • Their new EOA
    • Their existing COA (labelled EVM Flow account)
    • Their Cadence account
A COA account in Flow Wallet

You don’t need to do any special steps - the extension handles everything for you and simply shows your new EOA alongside your existing accounts.

What happens to my COA?

If you’ve already been using Flow EVM through Flow Wallet, you already have a Cadence-owned account (COA). This is an EVM account on Flow that’s controlled by your Cadence account.

Here’s how COAs behave after the update:

  • Your COA will continue to work as normal.
  • You’ll see it listed alongside your new EOA and your Cadence account.
  • Once your COA is empty (contains no detected assets), it will no longer be displayed in Flow Wallet Extension. If it receives any assets, it will reappear.
  • You can still always select to use your COA to connect to your favourite apps on Flow, even if it has no assets and is no longer displayed.

This keeps things clean for the long term: you can gradually move over to use your EOA, and once your COA is no longer needed, it quietly disappears from Flow Wallet's UI.

Use the same seed phrase in Flow Wallet and MetaMask

One of the biggest benefits of EOAs is interoperability with other wallets.

With this release:

  • You can take your MetaMask seed phrase, and import it into Flow Wallet Extension, and access the same EOA on Flow’s EVM.
  • You can take your Flow Wallet Extension seed phrase, plug it into MetaMask, and access that same EOA there too.

That means:

  • No more one-off EVM addresses just for Flow.
  • No custom, Flow-only account formats.
  • Just standard EVM EOAs you can use across different wallets that support the same path.

Why this matters

Adding EOAs to Flow Wallet Extension does a few important things:

  • Makes Flow and Flow Wallet feel familiar to anyone coming from Ethereum or other EVM chains.
  • Reduces friction when moving between wallets.
  • Keeps Flow Wallet with expected Web3 standards and UX, while still supporting Flow-native features like Cadence accounts and COAs.

This is another step toward making Flow Wallet a clear, open-source reference for what a great wallet on Flow can be, usable by everyday users, and powerful for developers.