Wallet type
Compare EOA wallets with smart wallets, check which networks are ready for smart wallets, and move the organisation to smart wallets once.
Wallet type sets the kind of wallet every user of the organisation holds, on every network. An EOA wallet, or externally owned account, is a plain wallet controlled by one key. A smart wallet is a contract wallet with weighted signers, approval policies, and recovery. The organisation starts on EOA wallets unless it chose smart wallets during onboarding.
Come here when the organisation needs approval rules, key recovery, or batched operations. EOA wallets already issue and transfer assets, so the move is optional. It is also one-way: once the organisation uses smart wallets, the platform does not accept a move back.
Who pays gas is a separate choice per network, made on Transaction funding.
Steps
Compare the wallet types
Open Organisation settings, then Infrastructure, then Wallet type. The page states that the setting applies to every wallet in the organisation, on every network. A badge names the current type: EOA wallets or Smart wallets.
On EOA wallets, the first card reads EOA wallets with Current · nothing to do. The next card, Advanced accounts: smart wallets, holds a table that compares the two types:
| Aspect | EOA wallets | Smart wallets |
|---|---|---|
| Signing | One key per wallet signs every write. | Weighted signers and approval policies per wallet. |
| Gas | Self-pay or Relayer-paid, per network. | Self-pay or Paymaster-paid, per network. |
| Recovery | The key is the wallet. Lose it, lose access. | Recovery signers can replace a lost key. |
| Batched operations | One write per transaction. | Several writes in one operation. |
| Needs on the network | Nothing extra. A forwarder for Meta-tx. | An EntryPoint and a bundler. |
The table names any active network that has no EntryPoint and bundler yet. Below the table, the card states how many of the organisation's active networks are ready for smart wallets.
Review the migration
Select See what the switch involves. The Migrate to smart wallets sheet opens. Nothing starts until you confirm at the bottom.
The sheet warns that writes pause for a few minutes. Writes already in flight finish first, and anything new waits and resumes on its own.
Under Before you start, the sheet lists each active network of the organisation as Ready or Not ready. A network is ready when its EntryPoint and bundler are in place. A network that is not ready keeps its writes on EOA wallets until it is. A last row states that every network starts on Self-pay after the switch.
When a write on the organisation relayer is paused or still in flight, the sheet lists it under A relayer write has not finished. A paused write waits for relayer funds: top up the relayer on that network, or cancel the write. A cancelled write is not sent again, so submit it again after the switch. The sheet reads readiness again each time it opens, so a write that finished in the meantime no longer shows.
Under What happens, the sheet lists the steps:
- A smart wallet deploys for every existing wallet, on each ready network.
- Each existing key becomes the signer of its smart wallet. Holdings stay where they are.
- Every network starts on Self-pay. You switch on a paymaster per network afterwards under Transaction funding.
- When some networks are not ready, the sheet names them. They stay on EOA wallets until they have an EntryPoint and a bundler.
Start the migration
Type MIGRATE in the field under Type MIGRATE to confirm. Start migration stays unavailable until the field holds that word. It also stays unavailable, with the reason under it, while no network is ready for smart wallets or a relayer write has not finished. The switch would queue writes that cannot land, so the platform refuses it and spends no gas. Select Start migration, or Not now to close the sheet without a change.
The Console confirms with Migration to smart wallets started. and closes the sheet. When the start fails, the sheet shows the reason and the organisation stays on EOA wallets. Without the right role, the field and the button are unavailable, and the sheet reads Only an admin, gas manager or system manager can start the migration.
What the platform does on the switch
Before the switch, the platform grants each smart wallet the on-chain roles its signing wallet holds. When roles have drifted and you do not hold the system admin role, the platform stops the switch and the failure names the smart wallets that need the grant.
When the organisation paid gas through the relayer on a network, the relayer stops paying for new writes and keeps its balance. It shows as Idle under All wallets on Transaction funding, where an admin can withdraw the balance.
A write from an EOA wallet that was queued before the switch still goes through the relayer, and the relayer pays its gas. This covers a write that waits for its wallet checker across the switch. A write queued after the switch follows the network's new gas payer. Keep enough in the relayer for those queued writes before you withdraw its balance.
The switch is organisation wide. Each network follows once it has an EntryPoint and a bundler.
After the migration
The page reads Smart wallets since and the date the organisation's wallet type was saved, followed by This cannot be switched back. Gas is set per network under Transaction funding. When the date is unknown, it reads Smart wallets. The page names any active network that has no EntryPoint yet, where wallets stay EOA wallets.
The summary also counts the networks ready for smart wallets, for example 2 of 3 networks ready for smart wallets. The table What each wallet type gives you stays on the page for reference.
Tokens needing role migration
For the network selected in the sidebar, the page lists tokens whose participants still hold roles on their signing addresses rather than on their smart wallets. Each row shows the token, the affected participant count, and the token admins. Each token's admin runs the migration from that token's page. When no token needs a role migration, the page does not show this section.
Troubleshooting
Wallet type is missing from the sidebar
The deployment does not offer smart wallets, or you do not hold the Admin, Gas Manager, or System Manager role. Without the feature, the page's address opens Transaction funding.
Start migration stays unavailable
Type MIGRATE exactly, in capitals. Without the Admin, Gas Manager, or System Manager role, the button stays
unavailable. The button also stays unavailable while no network is ready for smart wallets, or while a relayer write
has not finished. Top up the relayer or cancel the write, then open the sheet again.
The migration fails to start
The sheet shows the reason. The platform also needs an owner or administrator membership of the organisation, or the platform administrator role. When the failure names smart wallets whose roles drifted, ask a holder of the system admin role to start the migration. When it names a relayer write that has not finished, top up the relayer or cancel that write, then start again. When the switch waits for its own write, start again once that write lands. When it says the organisation's system is not indexed yet, wait until the network's system finishes indexing, then start again.
A network still uses EOA wallets after the migration
That network has no EntryPoint or bundler yet. Its wallets stay EOA wallets until the network is ready.
Wallet type could not be read
The organisation's wallet type did not load. Retry from the error card on the page.