Yeqela kokuqukethwe

Leli khasi litholakala ngesiNgisi kuphela.

Security: Keys, Data and Signing

How FxWallet handles your mnemonic phrase and keys, what the app sends to FxWallet and third parties, how signing works and which parts are open source.

Last reviewed: 12 November 2026. Applies to FxWallet 3.4.0 for Android and iOS. Where earlier versions behave differently, this page says so.

In short

This page explains how FxWallet handles your keys and data. Each statement is based on the app’s code as of the version above.

  • FxWallet is a self-custody wallet. Your mnemonic phrase and private keys are created on your phone and FxWallet never receives them, so FxWallet cannot sign transactions for you or restore your wallet.
  • Transactions are signed on your phone. For built-in networks, FxWallet’s servers provide your balances, prepare some of the transactions you sign and broadcast them.
  • The app sends FxWallet’s servers your public wallet addresses, for Bitcoin-family networks your extended public keys (xpubs), and device information. Mixpanel receives usage analytics only, not your wallet addresses.
  • Gas Card and token-paid network fees use FxWallet’s own accounts, whose keys are held in AWS KMS. These accounts pay fees for transactions you sign; they cannot sign for you or change what you signed.
  • The FxWallet app is closed source. The libraries it uses for address generation, transaction signing and QR-code signing are open source.

Your keys

Who holds my keys?

You do. The app generates your mnemonic phrase on your phone; new wallets use a 12-word BIP39 mnemonic phrase. Keys are derived with the standard BIP32/BIP44 paths (SLIP-10 for Solana), so your mnemonic phrase can be restored in other wallets that use the same paths.

FxWallet has no feature that uploads your mnemonic phrase to FxWallet or to a cloud drive, and cannot restore your wallet. From app 3.4.0, your phone’s system backup, restore and phone-transfer tools do not carry your wallets to a new phone; use the app’s own transfer between phones, or your mnemonic phrase. If you lose your phone, your mnemonic phrase is the only way to restore your wallet. Write it down and keep it offline.

Where are my mnemonic phrase and private keys stored?

On your phone, in the app’s own storage, encrypted.

From app 3.4.0, the wallets you create, import or receive from another phone, and existing wallets once the app has upgraded their protection, are encrypted with a key that the app generates at random on this phone. That key is protected by the phone’s system key storage (the Keychain on iOS, the hardware-backed Keystore on Android), which does not leave the phone, so wallet data that is copied off the phone, or restored from a system backup onto another phone, cannot be decrypted there.

  • With biometrics, the key can be used only after the phone has confirmed your fingerprint or face; after they change, it takes the phone’s screen-lock passcode.
  • With a password, the key is locked with your password together with a secret held by the phone’s security hardware, so the password alone, or a copy of the app’s data, does not open the wallets on another device.
  • Wallets from earlier versions are upgraded to this protection by the app itself, where the phone meets the requirements for it. Where it does not, a wallet keeps its earlier protection, and the app’s Security screen says that the protection has not been upgraded.

Do they ever leave my phone?

FxWallet never receives your mnemonic phrase or private keys. What the app sends to FxWallet is derived from your keys: signatures, signed transactions, public keys and addresses. Aleo is the one exception; see What FxWallet’s servers see. From app 3.4.0, you can also copy your wallets to your new phone over your local network, as described below.

How do the password and biometrics work?

  • The app does not store your wallet password and never sends it to FxWallet. FxWallet cannot reset it; if you forget it, reset the app and import your mnemonic phrase again.
  • From app 3.4.0, after every 5 wrong passwords the app makes you wait before you can try again, up to 1 hour at a time; wrong passwords never erase your wallets.
  • Showing your mnemonic phrase or exporting a private key always asks you to authenticate again. The mnemonic phrase stays hidden until you tap to show it, and that screen has no copy button. If you copy a private key, the app does not clear your clipboard.
  • After you authenticate to sign, the app can sign again from the same wallet for up to 2 minutes without asking; each signature restarts the 2 minutes.
  • In biometrics mode, you can also require biometrics when the app starts.
  • From app 3.4.0, if the fingerprints or face enrolled on the phone change while FxWallet unlocks with biometrics, everything that needs your keys, such as sending, signing, showing the mnemonic phrase and transferring to another phone, is paused for 24 hours, so that a fingerprint or face added by someone else cannot be used at once. The time is checked online, not against the phone’s clock, and afterwards you confirm with the phone’s screen-lock passcode.
  • From app 3.4.0, keep the phone’s screen lock on while FxWallet unlocks with biometrics: if the lock is removed, the wallets on that phone can no longer be opened, and have to be reset and then imported with the mnemonic phrase or transferred from another phone that still holds them.

Can I move my wallets to a new phone?

From app 3.4.0, you can move your wallets from your old phone to a new one with Transfer to another phone. Both phones must be on the same Wi-Fi network or hotspot, and the transfer does not go through FxWallet’s servers. The new phone shows a QR code; the old phone asks you to authenticate before it scans the code; and the 6-digit code shown on the old phone is entered on the new one. The data is end-to-end encrypted between the two phones, and the new phone protects your wallets with its own biometrics or password.

Use it only between your own phones: anyone who asks you to scan a transfer code, or to tell them the code, is a scammer.

What does Reset do?

Reset removes every wallet from the app on this phone. You confirm it by typing RESET; it does not ask for your password. The app also tells FxWallet’s servers that this phone’s wallets were removed, and keeps retrying until they confirm; the servers mark those records as deleted. A wallet removed by Reset can be restored only from its mnemonic phrase or private key.

Deleting a single wallet, or all wallets from wallet management, asks you to authenticate.

Signing transactions

Where are transactions signed?

On your phone. Transactions and messages are signed on your phone, and only the signed result leaves it. FxWallet’s servers never sign with your keys.

What do FxWallet’s servers do when I send?

For built-in networks, the app uses FxWallet’s servers to read balances and fees, prepare some unsigned transactions and broadcast the transactions you sign. For networks you add yourself, the app broadcasts directly to the RPC node you entered.

Does the app check what the servers prepare?

  • For standard EVM actions (token transfers, approvals and revokes, NFT transfers and batch sends), the app rebuilds the transaction data on your phone and refuses to sign if the server’s data differs. After signing, it checks the signed transaction against what you confirmed.
  • For other networks, such as Bitcoin-family networks, TRON, Solana and TON, and for swaps, bridges and token-paid fees, the app signs transactions assembled from data that FxWallet’s servers provide, and does not fully check that data on your phone. For these, you rely on FxWallet’s servers to prepare the transaction correctly.

What do I see before I sign?

  • When you send from the app, the confirmation screen shows the amount, the full recipient address, the network and the fee.
  • For DApp and WalletConnect requests, the confirmation screen shows the network, the fee and any amount of the network’s native coin that you send. Token approvals, and Permit and Permit2 signature requests, show the token, the spender, the amount and the expiry, and the app checks the spender: an approval to an address reported as a scam or sanctioned is blocked, and an approval to a personal address needs an extra confirmation. Some swap, bridge and batch-transfer calls are decoded. For other contract calls, the screen shows the full contract address and the raw data, but not what the call does. Typed-data requests that name a different network than the one you are on cannot be confirmed.
  • Sign-In with Ethereum requests are refused when the account in the message is not the one you are signing with. In the in-app browser, they are also refused when the site does not match the domain in the message.
  • Requests that use eth_sign are always signed as prefixed messages, so a website cannot obtain a signature over a raw hash. DApps cannot ask the app to sign EIP-7702 authorizations.
  • In-app EVM swaps above a value set by FxWallet are simulated before you confirm, using Tenderly through FxWallet’s servers. If the simulation reports a failure, or predicts that you would receive far less than quoted, the swap cannot proceed. Solana swaps are checked only for whether they would succeed. If the simulation service does not answer, the swap is not held back. DApp and WalletConnect transactions are not simulated.

What risk warnings does the app show?

  • Before you send on a built-in EVM network, FxWallet’s servers check the recipient. The app labels addresses reported as scams or sanctioned, addresses that look like one you sent to before, contracts and new addresses. For a high-risk address you must confirm before continuing; the app does not block the transfer.
  • On other networks, the app only shows a notice when GoPlus reports the address.
  • In the in-app browser, a website that FxWallet has confirmed as phishing is blocked; a website that FxWallet does not know, or that is flagged, is covered and cannot connect to your wallet until you choose to continue.
  • A WalletConnect connection to a site reported as malicious is rejected.
  • In the in-app swap, buying a token flagged as a honeypot, a fake token or a scam is blocked, and so are swaps with a price impact above FxWallet’s limit.

How does cold wallet mode work?

You can use a spare phone as an offline signer: install FxWallet on it, keep it offline, create or import your wallet there, and connect it to FxWallet on your everyday phone by scanning a QR code. Hardware & Cold Wallets shows how the two phones work together.

  • The online phone receives only public keys and addresses.
  • Requests and signatures travel between the phones as animated QR codes in the BC-UR format. The online phone checks each returned signature before broadcasting.
  • The offline phone refuses to open or sign a request while it is connected to a network, and cancels an open request if it goes online. The app does not otherwise block networking.
  • On the offline phone, the recipient and the amount are decoded from the transaction itself on every supported network. Only the network fee shown for TRON, Litecoin, Dogecoin and Bitcoin Cash comes from the online phone.
  • Supported networks: EVM networks, Bitcoin, Litecoin, Dogecoin, Bitcoin Cash, Solana, TRON, the Cosmos networks (Cosmos Hub, Kava and Sei), Alephium, Sia and ScPrime.

Which hardware wallets are supported?

Hardware wallets connect by QR code only; there is no Bluetooth or USB connection, and Ledger and Trezor are not supported.

  • Keystone: EVM networks, Bitcoin, Bitcoin Cash, Dogecoin, Solana, TRON, the Cosmos networks and XRP Ledger.
  • Goldshell and other devices that use the same QR format: the networks listed for cold wallet mode, and Kaspa where the device supports it.
  • The keys stay on the device. The app shows the request as a QR code and broadcasts the signature the device returns.

Can I review token approvals?

Yes. You can review and revoke ERC-20 token approvals in the app, under Approvals. The approval list comes from DeBank through FxWallet’s servers, which send DeBank your address. Each revoke is a transaction you sign and pay for; with Batch Revoke you go through several in a row, and an account upgraded with EIP-7702 can revoke several in a single transaction.

Where is my signing history stored?

The signing history for cold, hardware and watch-only wallets is stored only on your phone. From app 3.4.0, moving to a new phone copies it to the new phone.

Gas Card and sponsored network fees

Whose keys pay the network fee?

FxWallet’s. Gas Card and token-paid network fees use accounts owned by FxWallet. Their private keys are held in AWS Key Management Service (KMS) and are used only through KMS signing requests. These are FxWallet’s operating keys, not your keys, and they cannot sign for your wallet.

What happens when I pay with a Gas Card?

You still sign your own transaction on your phone. FxWallet first sends the needed amount of the network’s native coin from its account to your address, then broadcasts your signed transaction unchanged. Your Gas Card balance is kept in FxWallet’s records, not on-chain.

What happens when I pay the network fee with a token?

On supported networks you can pay the network fee with a token. The first time you do this on a network, the app upgrades your account with EIP-7702 so that it uses a smart-account contract chosen by FxWallet. You then sign a batch that contains your transaction and a token payment to FxWallet; FxWallet submits it and pays the network fee. The upgrade stays on your account until you revoke it on the EIP-7702 page in the app, which is a transaction you pay for in the native coin.

What can the sponsor do, and what can it not do?

The sponsor can see your signed transaction before it is broadcast, decide when to broadcast it or not broadcast it at all, and collect the fee you agreed to: the Gas Card deduction or the token payment you signed.

The sponsor cannot sign for you or change a transaction you signed. A Gas Card transaction is broadcast exactly as you signed it; it can be included only once and only on the network you signed it for.

What if FxWallet’s servers are unavailable?

Gas Card and token-paid fees need FxWallet’s servers, and so does sending on built-in networks. If FxWallet’s servers are unavailable, your funds stay on-chain under your keys, and you can restore your mnemonic phrase in another wallet that uses the same derivation paths.

Open source

Is FxWallet open source?

The FxWallet app is closed source, so its builds cannot be independently reproduced today.

These parts are not public: how the mnemonic phrase is generated and stored, the password and biometrics, the choice of derivation paths, confirmation screens and risk warnings, the network layer, and FxWallet’s servers.

These parts are public:

  • fx-wallet-packages: crypto_wallet_util, used for address generation and transaction signing on more than 20 networks; bc_ur_dart, the QR format used for cold and hardware wallets; flutter_web3_webview, the in-app browser’s wallet connection; and k_chart_flutter, for charts.
  • aleo_dart: the Dart layer of the Aleo integration.
  • App 3.4.0 uses crypto_wallet_util 2.1.2, bc_ur_dart 0.1.30 and flutter_web3_webview 1.1.1 as published on pub.dev, and aleo_dart at commit 05eaa9b.

What FxWallet’s servers see

To show your balances, history and prices, the app sends your wallet’s public addresses to FxWallet’s servers (for Bitcoin-family chains, the account’s extended public key), with an identifier for your device. The addresses are public on the blockchain in any case. The servers never receive your mnemonic phrase or private keys. For Aleo, the app also sends the account’s view key to FxWallet’s Aleo sync service so that it can find your records: a view key can read your Aleo records and balances, but cannot spend them.

  • From app 3.4.0, push notifications are delivered by Apple’s push service on iOS and by Google’s Firebase Cloud Messaging on Android. Each issues a token for your device, which FxWallet’s servers keep in order to send them. Earlier versions of the app use OneSignal.
  • Product analytics are sent to Mixpanel under an anonymous ID: the features you use and amount ranges in US dollars, not your wallet addresses.
  • A DApp you connect to, directly or through WalletConnect, sees the address you connect with.
  • The Privacy Policy sets out how FxWallet handles personal data.

Verify the app you install

  • Install FxWallet from the App Store (developer DXP COMPUTING POWER FOUNDATION PTE. LTD.), Google Play (developer ECHOINFI PTE. LTD.) or this site.
  • Before you install the APK from this website, check its SHA-256 against the value on the download page.
  • FxWallet support never messages you first, and never asks for your mnemonic phrase or private key.
  • FxWallet’s official accounts are listed on the About page.

If your wallet is compromised

If you typed your mnemonic phrase into a site or an app, or signed something you do not recognise, act at once: move your assets to a new wallet with a new mnemonic phrase, and revoke any approval you did not mean to give. What to do if your wallet is compromised describes each step.

Esikhungweni Sosizo

Thola i-FxWallet

Mahhala ku-iPhone naku-Android.