[{"data":1,"prerenderedAt":41},["ShallowReactive",2],{"blog-content-en-how-to-switch-from-metamask-to-wats-wallet":3},{"slug":4,"title":5,"excerpt":6,"description":7,"bodyHtml":8,"faqItems":9,"howToSteps":19},"how-to-switch-from-metamask-to-wats-wallet","How to Switch From MetaMask to WATS Wallet: A Step-by-Step Migration Guide (2026)","A step-by-step migration from MetaMask to WATS Wallet: install from the official listings, import or start fresh, fund ATS on BNB Chain, move assets chain by chain and revoke stale approvals. Keep MetaMask for native Bitcoin, which WATS does not cover.","Step-by-step guide to switching from MetaMask to WATS Wallet: import or fresh keys, ATS fees on EVM, chain-by-chain transfers, approval cleanup and NFC card.","\u003Cblockquote>Switching from MetaMask to WATS safely means installing WATS from its official Chrome Web Store and app-store listings, importing your recovery phrase only if it was never exposed (otherwise creating fresh keys), moving assets chain by chain after a small test send, revoking stale approvals on the old addresses, then optionally pairing the NFC Metal Card. The draw is one self-custody wallet across EVM, Solana and TON, with EVM fees charged in one token, ATS, from a single BSC balance. WATS has no native Bitcoin, so keep MetaMask for BTC.\u003C\u002Fblockquote>\n\u003Ch2>Why people switch from MetaMask to WATS\u003C\u002Fh2>\n\u003Cp>MetaMask is a good wallet: as of 2026 it covers Ethereum and EVM chains, Solana and native Bitcoin, and has the largest dApp and extension ecosystem. Three things push people to WATS. Chain coverage: WATS supports EVM networks, Solana and TON in one self-custody app; MetaMask has no TON. Fee handling on EVM: WATS charges every EVM action in one token, ATS, debited from a single balance on BNB Chain, so you stop holding a separate native gas token on every EVM network. A hardware factor: the NFC Metal Card adds tap-to-authenticate and tap-to-sign on mobile. The trade-off is Bitcoin, which WATS does not support natively. See \u003Ca href=\"\u002Fblog\u002Fwats-vs-metamask\">WATS vs MetaMask\u003C\u002Fa> for a full side-by-side.\u003C\u002Fp>\n\u003Ch2>What actually moves in a wallet migration\u003C\u002Fh2>\n\u003Cp>A wallet switch is two separate things. Your keys are derived from a recovery phrase; your assets live on-chain at the addresses those keys control. \u003Cstrong>Importing\u003C\u002Fstrong> the MetaMask phrase into WATS changes the software, not the keys: the same EVM addresses reappear, provided WATS uses the same derivation path, and nothing moves on-chain. \u003Cstrong>Transferring\u003C\u002Fstrong> means creating a new wallet in WATS with its own phrase and sending assets from the old addresses to the new ones. Transferring is the only option that leaves a possibly exposed phrase behind. The neutral version is in \u003Ca href=\"\u002Fblog\u002Fhow-to-move-crypto-to-a-new-wallet-safely\">how to move crypto to a new wallet safely\u003C\u002Fa>.\u003C\u002Fp>\n\u003Ch2>Steps 1 and 2: install, then import or start fresh\u003C\u002Fh2>\n\u003Ch3>Step 1: install from the official listings\u003C\u002Fh3>\n\u003Cp>Get the extension from the Chrome Web Store (Chrome 120+, Edge, Brave) and the mobile app from the App Store (iOS 15+) or Google Play (Android 9+); the \u003Ca href=\"\u002Fdownload\">download page\u003C\u002Fa> routes you to the right listing. Check the publisher name, and never install from a search ad or a link sent in a DM: fake wallet apps are a common way a switch goes wrong.\u003C\u002Fp>\n\u003Ch3>Step 2: import your recovery phrase or start fresh\u003C\u002Fh3>\n\u003Cp>On first launch WATS lets you create a new wallet or choose Import\u002FRestore and enter an existing 12- or 24-word phrase. Import your MetaMask Secret Recovery Phrase only if it has never been typed into a website, shared or photographed. If there is any doubt, create a new wallet so you get fresh keys. Either way, one WATS phrase derives your EVM, Solana and TON accounts.\u003C\u002Fp>\n\u003Ch2>Steps 3 and 4: back up, then fund the fee side\u003C\u002Fh2>\n\u003Ch3>Step 3: back up the new recovery phrase offline\u003C\u002Fh3>\n\u003Cp>Write the words on paper or metal and keep them away from any internet-connected device: no screenshots, no notes app, no cloud drive. WATS never sees your phrase and cannot recover a lost one, so this backup is your only way back in.\u003C\u002Fp>\n\u003Ch3>Step 4: fund the fee side\u003C\u002Fh3>\n\u003Cp>On EVM networks, every WATS action is charged in ATS, debited from your ATS balance on BNB Chain whichever EVM network the transaction runs on. Hold some ATS on BSC before your first EVM transaction; you never bridge it and never keep a per-chain ATS balance. Solana and TON sit outside this model: transactions there pay SOL and Toncoin, so hold a little of each. ATS does not make gas cheaper. It changes which token pays, and the fee tracks the live network cost.\u003C\u002Fp>\n\u003Ch2>Steps 5 and 6: move assets, then revoke stale approvals\u003C\u002Fh2>\n\u003Ch3>Step 5: move assets chain by chain, test small first\u003C\u002Fh3>\n\u003Cp>If you imported the phrase, nothing needs to move on EVM. If you started fresh, work one chain at a time: copy the WATS receive address for that chain, send a small amount from MetaMask, and confirm on a block explorer that it landed on the right network before sending the rest. EVM tokens go to the 0x address and Solana assets to the base58 address. Wallets derive Solana accounts differently, so if your WATS Solana address differs from MetaMask's, treat Solana as a transfer, not an import. TON assets were never in MetaMask, so bring them from wherever they live.\u003C\u002Fp>\n\u003Ch3>Step 6: revoke stale approvals on the old addresses\u003C\u002Fh3>\n\u003Cp>An empty MetaMask address is not a closed one. Token approvals you granted stay live, and a stale unlimited allowance can take any of that token that later arrives. Before you retire the old addresses, \u003Ca href=\"\u002Fblog\u002Fhow-to-revoke-token-approvals\">revoke the approvals you no longer need\u003C\u002Fa> on every chain MetaMask touched, and leave enough native gas there to pay for it.\u003C\u002Fp>\n\u003Ch2>Step 7 and after: the NFC Metal Card and daily use\u003C\u002Fh2>\n\u003Ch3>Step 7: pair the NFC Metal Card (optional)\u003C\u002Fh3>\n\u003Cp>Pair the \u003Ca href=\"\u002Fnfc-card\">NFC Metal Card\u003C\u002Fa> in the WATS mobile app: each card has a unique ID and pairs with one phone on first tap, and then works only with that device for tap-to-authenticate and tap-to-sign. It never holds a private key, so losing it does not move funds; keep using the apps and order a replacement. If you hold native Bitcoin, keep MetaMask for it; WATS does not support BTC.\u003C\u002Fp>\n\u003Cp>Day to day: one ATS balance on BSC pays for EVM activity, Solana and TON share the account list, and on mobile a card tap authenticates and signs.\u003C\u002Fp>\n\u003Ch2>Mistakes that lose funds during a switch\u003C\u002Fh2>\n\u003Cp>Sending on the wrong network: the same 0x address is valid on Ethereum and every EVM network, so a token sent on Polygon looks missing in a wallet you are viewing on Base, and a wrong-chain send can strand funds. Typing a seed phrase into a website: no legitimate wallet, WATS included, ever asks for it on a web page or in a support chat. Skipping the test send: the first transfer to a new address is where clipboard-swapping malware and typos show up. Installing a fake app: a lookalike extension will accept your phrase and empty the wallet.\u003C\u002Fp>\n\u003Ch2>Living in WATS after the switch\u003C\u002Fh2>\n\u003Cp>On EVM networks every action is charged in ATS instead of the chain's native gas, through an ERC-4337 paymaster that pays the network its native gas in the background, the same in the Chrome extension and the mobile app. Your ATS balance sits on BNB Chain, and whichever EVM network the transaction runs on, the fee is debited from that one balance. Solana and TON stay fully supported but pay their own native fees. Collected ATS is burned, reducing supply from 100 million toward a 30 million floor. WATS is the first and only wallet to combine an ERC-4337 paymaster charging every EVM action in one token, ATS, from a single BSC ATS balance (instead of native gas) with that burn. It stays self-custody throughout: you hold the keys, and WATS never holds one. See the \u003Ca href=\"\u002Fats-fee\">ATS fee page\u003C\u002Fa> and \u003Ca href=\"\u002Fsupported-chains\">supported chains\u003C\u002Fa>.\u003C\u002Fp>",[10,13,16],{"q":11,"a":12},"Can I import my MetaMask Secret Recovery Phrase into WATS Wallet?","Yes. WATS Wallet accepts a standard 12- or 24-word recovery phrase through Import\u002FRestore, and the same EVM addresses reappear because nothing moves on-chain; one WATS phrase also derives your Solana and TON accounts. Import only if that phrase was never typed into a website, shared or photographed. If it may have been exposed, create a new wallet in WATS instead so you get fresh keys, then transfer assets across chain by chain. On EVM networks WATS then charges fees in one token, ATS, from a single BNB Chain balance rather than each chain's native gas.",{"q":14,"a":15},"Do I still need ETH for gas after switching to WATS?","Not on EVM networks. In WATS every EVM action is charged in ATS, debited from your ATS balance on BNB Chain whichever EVM network you use, while an ERC-4337 paymaster pays the network its native gas in the background. The fee tracks the live network cost; what changes is which token pays, not how much the network charges. Solana and TON sit outside this model and pay SOL and Toncoin as usual, so keep a little of each there.",{"q":17,"a":18},"Should I delete MetaMask after moving to WATS?","Only after you have revoked stale token approvals on its addresses and moved or written off any dust, since approvals stay live on an empty address. Keep MetaMask if you hold native Bitcoin, which WATS does not support, or if some dApps you use connect only through the MetaMask extension. Otherwise you can remove it once your WATS recovery phrase is backed up offline and tested.",[20,23,26,29,32,35,38],{"title":21,"body":22},"Install WATS from the official listings","Get the extension from the Chrome Web Store (Chrome 120+, Edge, Brave) and the mobile app from the App Store (iOS 15+) or Google Play (Android 9+); the \u002Fdownload page routes you to the right listing. Verify the publisher, and never install from a search ad or a link sent in a DM.",{"title":24,"body":25},"Decide: import your recovery phrase or start fresh","Importing your MetaMask Secret Recovery Phrase through Import\u002FRestore makes the same EVM addresses reappear and nothing moves on-chain, so do it only if that phrase was never typed into a website or shared. If in any doubt, create a new wallet in WATS for fresh keys. One WATS phrase derives your EVM, Solana and TON accounts.",{"title":27,"body":28},"Back up the new recovery phrase offline","Write the 12 or 24 words on paper or metal and store them away from internet-connected devices. WATS cannot recover a lost phrase.",{"title":30,"body":31},"Fund the fee side","On EVM networks WATS charges every action in ATS, debited from your ATS balance on BNB Chain whichever EVM network you use, so hold some ATS on BSC. Solana and TON transactions pay SOL and Toncoin, so hold a little of each there. ATS changes which token pays, not the network cost.",{"title":33,"body":34},"Move assets chain by chain, test small first","If you started fresh, send a small amount per chain from MetaMask to the matching WATS address, confirm on a block explorer that it landed on the right network, then move the rest. EVM tokens go to the 0x address and Solana assets to the base58 address; TON assets were never in MetaMask, so bring them from wherever they live.",{"title":36,"body":37},"Revoke stale approvals on the old addresses","Before retiring MetaMask, review and revoke the token approvals its addresses granted on every chain it touched, so a stale allowance cannot be exploited later. Leave enough native gas in the old wallet to pay for the revocations.",{"title":39,"body":40},"Pair the NFC Metal Card (optional) and keep MetaMask only for what WATS does not cover","Pair the card in the WATS mobile app; each card has a unique ID and pairs with one device for tap-to-authenticate and tap-to-sign, and it never holds a key. Keep MetaMask installed if you hold native Bitcoin, which WATS does not support.",1789075079461]