Wallet Logo

Mycelium Bitcoin Wallet

Google Play App Store Website Check your version

Latest release found by WalletScrutiny: 3.22.0.2 / 2.12

Developer
Mycelium Developers (Android)
MRD X-Change GmbH (iPhone)
X LinkedIn Facebook Reddit
Released
Android: 1st July 2013
iPhone: 17th December 2014
Source code
Android: github
iPhone: github
Custody
Self-custodial: The user holds the keys

Our wallet review process

We examine wallets starting at the code level and continue all the way up to the finished app that lives on your device. Provided below is an outline of each of these steps along with security tips for you and general test results.

Passed all 7 tests

We answered the following questions in this order:

Is this product the original?

The answer is "yes".
If the answer were "no", we would mark it as "Fake" and the following would apply:

The answer is "no". We marked it as "Fake".

We did not ask this question because we failed at a previous question.
If the answer were "no", we would mark it as "Fake" and the following would apply:

The bigger wallets often get imitated by scammers that abuse the reputation of the product by imitating its name, logo or both.

Imitating a competitor is a huge red flag and we urge you to not put any money into this product!

The product cannot be independently verified. If the provider puts your funds at risk on purpose or by accident, you will probably not know about the issue before people start losing money. If the provider is more criminally inclined he might have collected all the backups of all the wallets, ready to be emptied at the press of a button. The product might have a formidable track record but out of distress or change in management turns out to be evil from some point on, with nobody outside ever knowing before it is too late.
Is it a wallet?

The answer is "yes".
If the answer were "no", we would mark it as "Not a wallet" and the following would apply:

The answer is "no". We marked it as "Not a wallet".

We did not ask this question because we failed at a previous question.
If the answer were "no", we would mark it as "Not a wallet" and the following would apply:

If it’s called “wallet” but is actually only a portfolio tracker, we don’t look any deeper, assuming it is not meant to control funds. What has no funds, can’t lose your coins. It might still leak your financial history!

If you can buy Bitcoins with this app but only into another wallet, it’s not a wallet itself.

Is it for bitcoins?

The answer is "yes".
If the answer were "no", we would mark it as "A wallet but not for Bitcoin" and the following would apply:

The answer is "no". We marked it as "A wallet but not for Bitcoin".

We did not ask this question because we failed at a previous question.
If the answer were "no", we would mark it as "A wallet but not for Bitcoin" and the following would apply:

At this point we only look into wallets that at least also support BTC.

Can it send and receive bitcoins?

The answer is "yes".
If the answer were "no", we would mark it as "Can't send or receive bitcoins" and the following would apply:

The answer is "no". We marked it as "Can't send or receive bitcoins".

We did not ask this question because we failed at a previous question.
If the answer were "no", we would mark it as "Can't send or receive bitcoins" and the following would apply:

If it is for holding BTC but you can’t actually send or receive them with this product then it doesn’t function like a wallet for BTC but you might still be using it to hold your bitcoins with the intention to convert back to fiat when you “cash out”.

All products in this category are custodial and thus funds are at the mercy of the provider.

The product cannot be independently verified. If the provider puts your funds at risk on purpose or by accident, you will probably not know about the issue before people start losing money. If the provider is more criminally inclined he might have collected all the backups of all the wallets, ready to be emptied at the press of a button. The product might have a formidable track record but out of distress or change in management turns out to be evil from some point on, with nobody outside ever knowing before it is too late.
Does the product allow self-custody?

The answer is "yes".
If the answer were "no", we would mark it as "Custodial: The provider holds the keys" and the following would apply:

The answer is "no". We marked it as "Custodial: The provider holds the keys".

We did not ask this question because we failed at a previous question.
If the answer were "no", we would mark it as "Custodial: The provider holds the keys" and the following would apply:

A custodial service is a service where the funds are held by a third party like the provider. The custodial service can at any point steal all the funds of all the users at their discretion. Our investigations stop there.

Some services might claim their setup is super secure, that they don’t actually have access to the funds, or that the access is shared between multiple parties. For our evaluation of it being a wallet, these details are irrelevant. They might be a trustworthy Bitcoin bank and they might be a better fit for certain users than being your own bank but our investigation still stops there as we are only interested in wallets.

Products that claim to be non-custodial but feature custodial accounts without very clearly marking those as custodial are also considered “custodial” as a whole to avoid misguiding users that follow our assessment.

We have to acknowledge that a huge majority of Bitcoiners are currently using custodial Bitcoin banks. If you do, please:

  • Do your own research if the provider is trust-worthy!
  • Check if you know at least enough about them so you can sue them when you have to!
  • Check if the provider is under a jurisdiction that will allow them to release your funds when you need them?
  • Check if the provider is taking security measures proportional to the amount of funds secured? If they have a million users and don’t use cold storage, that hot wallet is a million times more valuable for hackers to attack. A million times more effort will be taken by hackers to infiltrate their security systems.
The product cannot be independently verified. If the provider puts your funds at risk on purpose or by accident, you will probably not know about the issue before people start losing money. If the provider is more criminally inclined he might have collected all the backups of all the wallets, ready to be emptied at the press of a button. The product might have a formidable track record but out of distress or change in management turns out to be evil from some point on, with nobody outside ever knowing before it is too late.
Is the source code publicly available?

The answer is "yes".
If the answer were "no", we would mark it as "No source for current release found" and the following would apply:

The answer is "no". We marked it as "No source for current release found".

We did not ask this question because we failed at a previous question.
If the answer were "no", we would mark it as "No source for current release found" and the following would apply:

A wallet that claims to not give the provider the means to steal the users’ funds might actually be lying. In the spirit of “Don’t trust - verify!” you don’t want to take the provider at his word, but trust that people hunting for fame and bug bounties could actually find flaws and back-doors in the wallet so the provider doesn’t dare to put these in.

Back-doors and flaws are frequently found in closed source products but some remain hidden for years. And even in open source security software there might be catastrophic flaws undiscovered for years.

An evil wallet provider would certainly prefer not to publish the code, as hiding it makes audits orders of magnitude harder.

For your security, you thus want the code to be available for review.

If the wallet provider doesn’t share up to date code, our analysis stops there as the wallet could steal your funds at any time, and there is no protection except the provider’s word.

“Up to date” strictly means that any instance of the product being updated without the source code being updated counts as closed source. This puts the burden on the provider to always first release the source code before releasing the product’s update. This paragraph is a clarification to our rules following a little poll.

We are not concerned about the license as long as it allows us to perform our analysis. For a security audit, it is not necessary that the provider allows others to use their code for a competing wallet. You should still prefer actual open source licenses as a competing wallet won’t use the code without giving it careful scrutiny.

The product cannot be independently verified. If the provider puts your funds at risk on purpose or by accident, you will probably not know about the issue before people start losing money. If the provider is more criminally inclined he might have collected all the backups of all the wallets, ready to be emptied at the press of a button. The product might have a formidable track record but out of distress or change in management turns out to be evil from some point on, with nobody outside ever knowing before it is too late.
Is the decompiled binary legible?

The answer is "yes".
If the answer were "no", we would mark it as "Obfuscated" and the following would apply:

The answer is "no". We marked it as "Obfuscated".

We did not ask this question because we failed at a previous question.
If the answer were "no", we would mark it as "Obfuscated" and the following would apply:

When compiling source code to binary, usually a lot of meta information is retained. A variable storing a masterseed would usually still be called masterseed, so an auditor could inspect what happens to the masterseed. Does it get sent to some server? But obfuscation would rename it for example to _t12, making it harder to find what the product is doing with the masterseed.

In benign cases, code symbols are replaced by short strings to make the binary smaller but for the sake of transparency this should not be done for non-reproducible Bitcoin wallets. (Reproducible wallets could obfuscate the binary for size improvements as the reproducibility would assure the link between code and binary.)

Especially in the public source cases, obfuscation is a red flag. If the code is public, why obfuscate it?

As obfuscation is such a red flag when looking for transparency, we do also sometimes inspect the binaries of closed source apps.

As looking for code obfuscation is a more involved task, we do not inspect many apps but if we see other red flags, we might test this to then put the product into this red-flag category.

The product cannot be independently verified. If the provider puts your funds at risk on purpose or by accident, you will probably not know about the issue before people start losing money. If the provider is more criminally inclined he might have collected all the backups of all the wallets, ready to be emptied at the press of a button. The product might have a formidable track record but out of distress or change in management turns out to be evil from some point on, with nobody outside ever knowing before it is too late.

Distribution

Google Play Website

Build Verifications

If you have a binary for a version that doesn't appear on the list, you can dropselect the file here to register it so somebody can verify its reproducibility:

Drop binary file to verify

or
Learn more

Platform notes

On the Google Play Store, there are many apps that have Bitcoin in their name or description but don’t allow the user to use Bitcoin or they don’t look like Bitcoin wallets but turn out to be. We run our tests and document our findings.

Android

Trade from and to other crypto currencies

Trade from and to other crypto currencies

Exchange one crypto currency for another. You “receive Xcoin to your Ycoin account” while in the background the wallet sends your Ycoin address to a service provider which gives it an Xcoin address which it then displays. Funds sent to that Xcoin address - to that service provider - are then sold for Ycoin and the returns are sent to the wallet’s Ycoin address.

Easily accept receiving more coins without actually holding them.

  • Sometimes the service is less favorable in its fees when used through a wallet integration than when using the service’s website.
  • Some of those services require registration which links your transactions to your ID.
  • The exchange provider might not deliver, making it complicated to prove what happened, who to talk to and how to ultimately recover funds.

Why we list it for this wallet

In-app exchange and trading

Source: Website

Disclaimer: Authors of this project have contributed to Mycelium.

App Description

Mycelium Bitcoin Wallet is a non-custodial mobile wallet for Android that supports Bitcoin, Ethereum, and ERC-20 tokens such as USDT and USDC. It provides full user control over private keys, HD wallet support (BIP32/BIP39/BIP44), and watch-only functionality for integrating with cold storage solutions. Mycelium supports hardware wallets including Trezor, Ledger, and KeepKey, as well as direct spending from paper wallets or imported keys. Additional features include dynamic transaction fees, BIP70 payment request support, BitID authentication, and encrypted PDF key backups. The wallet also includes Local Trader for peer-to-peer in-person Bitcoin trading, and can optionally connect via Tor for enhanced privacy.

This app is source available.

Full SegWit Support

Full SegWit Support

SegWit which is short for “Segregated Witness” was an August 2017 upgrade to the Bitcoin protocol which came with new address types.

Full SegWit Support means that the wallet can both send to and receive to all SegWit address types, including bech32 starting with “bc1…”.

  • Receiving to SegWit addresses provides fee savings, as sending these funds is possible using less base-block space. In Bitcoin, transaction fees are proportional to the transaction size in bytes.
  • Receiving to bech32 addresses provides more fee savings than P2SH Segwit addresses.
  • Sending to SegWit addresses is sometimes required in order to use more modern tools that dropped support for legacy addresses, often because of another core property of SegWit transactions: They are not malleable, meaning that the transaction ID cannot be changed “in transit” (on unconfirmed transactions).

Why we list it for this wallet

SegWit: native (Bech32) and P2SH compatible

Source: Website

TOR - The Onion Router

TOR - The Onion Router

TOR is a tool to shield the IP address of communicating parties. When communicating with a node on the TOR network, the communication is also necessarily end to end encrypted but not when communicating to a server on the internet that does neither use TOR nor ssl (https). Modern Androids allow to put apps behind a local TOR node independently of the provider offering TOR features. While this can be desirable to shield one’s IP address, it also might expose unencrypted data to different, probably more aware third parties. It also does not replace more advanced TOR features in which the wallet creates multiple TOR identities for different requests.

  • Privacy: TOR shields the client’s IP address and thus his real world location or identity from servers it talks to.
  • Speed: TOR means bouncing messages around a bit more with extra encryption. That makes it slower.

Why we list it for this wallet

For enhanced privacy and availability you can connect to our super nodes via a tor-hidden service ( *.onion* address)

Source: README

Hierarchically Deterministic

Hierarchically Deterministic

All accounts and keys are derived from one masterseed as defined in BIP 32, BIP 39, BIP 44, BIP 49, BIP 84 and BIP 86. While some wallets might use different definitions and not all support SegWit or Taproot, we only consider this feature as given if

  • the backup is a BIP 39 mnemonic
  • the funds are recoverable on a competitor’s product correctly implementing those standards
  • no address reuse
  • simple backup
  • no vendor lock-in

Why we list it for this wallet

HD enabled - manage multiple accounts and never reuse addresses (Bip32/Bip44 compatible)

Source: README

Unlimited Accounts

Unlimited Accounts

The user can create or restore secondary BTC accounts

  • Accounting: Multiple accounts allow for easier separation of funds.
  • Privacy: Using an account with a positive balance at all time makes it relatively easy for blockchain analysis companies to determine the full history of the wallet. By using multiple accounts, emptying them at times, the user can retain some privacy.

Why we list it for this wallet

Multiple HD accounts, private keys, external xPub or xPriv accounts

Source: README

NFC (Near Field Communication)

NFC (Near Field Communication)

The wallet supports Near Field Communication (NFC) for wireless interaction with hardware wallets, payment terminals, or signing cards. NFC enables tap-to-sign or tap-to-pay functionality over a very short range (typically a few centimeters) without cables or QR codes.

  • Convenience: Quick tap interaction — no cables to connect or QR codes to scan.
  • Hardware wallet compatibility: Some hardware signing cards communicate exclusively via NFC.
  • Requires NFC hardware on both devices.
  • Very short range limits usability compared to QR-based air-gapped setups.

Why we list it for this wallet

NFC

Source: Website

iPhone

Disclaimer: The authors of this project have contributed to Mycelium Android.

This app has public source code which is independent of their Android version.

The provider claims:

100% control over your private keys, they never leave your device unless you export them.

but so far nobody reproduced the build, so the claim is not verifiable.

Full SegWit Support

Full SegWit Support

SegWit which is short for “Segregated Witness” was an August 2017 upgrade to the Bitcoin protocol which came with new address types.

Full SegWit Support means that the wallet can both send to and receive to all SegWit address types, including bech32 starting with “bc1…”.

  • Receiving to SegWit addresses provides fee savings, as sending these funds is possible using less base-block space. In Bitcoin, transaction fees are proportional to the transaction size in bytes.
  • Receiving to bech32 addresses provides more fee savings than P2SH Segwit addresses.
  • Sending to SegWit addresses is sometimes required in order to use more modern tools that dropped support for legacy addresses, often because of another core property of SegWit transactions: They are not malleable, meaning that the transaction ID cannot be changed “in transit” (on unconfirmed transactions).

Why we list it for this wallet

SegWit: native (Bech32) and P2SH compatible

Source: Website

TOR - The Onion Router

TOR - The Onion Router

TOR is a tool to shield the IP address of communicating parties. When communicating with a node on the TOR network, the communication is also necessarily end to end encrypted but not when communicating to a server on the internet that does neither use TOR nor ssl (https). Modern Androids allow to put apps behind a local TOR node independently of the provider offering TOR features. While this can be desirable to shield one’s IP address, it also might expose unencrypted data to different, probably more aware third parties. It also does not replace more advanced TOR features in which the wallet creates multiple TOR identities for different requests.

  • Privacy: TOR shields the client’s IP address and thus his real world location or identity from servers it talks to.
  • Speed: TOR means bouncing messages around a bit more with extra encryption. That makes it slower.

Why we list it for this wallet

TOR network support to mask IP address and location

Source: Website

Hierarchically Deterministic

Hierarchically Deterministic

All accounts and keys are derived from one masterseed as defined in BIP 32, BIP 39, BIP 44, BIP 49, BIP 84 and BIP 86. While some wallets might use different definitions and not all support SegWit or Taproot, we only consider this feature as given if

  • the backup is a BIP 39 mnemonic
  • the funds are recoverable on a competitor’s product correctly implementing those standards
  • no address reuse
  • simple backup
  • no vendor lock-in

Why we list it for this wallet

Option to display derivation address path for BIP44 HD accounts

Source: Website

Unlimited Accounts

Unlimited Accounts

The user can create or restore secondary BTC accounts

  • Accounting: Multiple accounts allow for easier separation of funds.
  • Privacy: Using an account with a positive balance at all time makes it relatively easy for blockchain analysis companies to determine the full history of the wallet. By using multiple accounts, emptying them at times, the user can retain some privacy.

Why we list it for this wallet

Multiple accounts - you can have unlimited number of USDT, Bitcoin, Tron, Ethereum, and TRC20/ERC20 accounts.

Source: Store

Advanced UTXO Control

Advanced UTXO Control

The wallet offers advanced control over which Unspent Transaction Outputs (UTXOs) are spent. This goes beyond simple coin selection — it may include the ability to freeze or exclude specific UTXOs (e.g., dusting attacks or tainted coins), label UTXOs, or select inputs manually. The user does not necessarily need full visibility of all UTXOs, but has meaningful control over what gets spent.

  • Privacy: Prevent spending from UTXOs linked to unwanted transaction history, or avoid merging coins from different sources in one transaction.

  • Dust protection: Mark suspicious incoming transactions as “do not spend” to avoid revealing your wallet’s full UTXO set.

  • Fee optimization: Strategically select inputs to manage transaction size and fees.

Why we list it for this wallet

Full UTXO control.

Source: Store

Custom Node Connection

Custom Node Connection

The wallet can be configured to connect to a user-specified, independently operated Bitcoin node — such as Bitcoin Core, Electrum Server, or other compatible full node software — instead of the wallet provider’s default servers. The key requirement is that the node is clearly independent from the wallet vendor: a third-party node the user controls or trusts.

  • Privacy: Transaction queries go to your own node rather than a third-party server, so no provider learns your wallet addresses or balances.

  • Security: No risk of a provider lying about your balance or the state of the network.

  • Sovereignty: Full independence from wallet provider infrastructure.

  • Requires running and maintaining your own Bitcoin node.
  • More complex initial setup compared to using the provider’s default servers.

Why we list it for this wallet

Connection to your own Bitcoin node.

Source: Store

Fingerprint Authentication

Fingerprint Authentication

Fingerprint authentication in Bitcoin wallets enhances security by adding a biometric layer to the access control mechanisms. This feature leverages the unique patterns of a user’s fingerprint to grant access to the wallet, making unauthorized access significantly more difficult. Biometric authentication is generally faster and more convenient than traditional methods like passwords or PINs, as it eliminates the need to remember complex combinations. This form of authentication is particularly useful in mobile wallet applications, where ease of access and security are paramount. Fingerprint authentication minimizes the risk of phishing or brute force attacks that typically target password-based systems. Furthermore, it can be combined with other forms of security measures, like PINs or passwords, to create a multi-factor authentication system for added security. The use of biometric data, however, raises concerns regarding privacy and data security. Users must be assured that their biometric data is stored securely and not vulnerable to unauthorized access or breaches.

  • Enhanced security through a unique, non-replicable form of identification
  • Convenience and speed of access compared to traditional methods
  • Reduced risk of phishing and brute force attacks

Potential privacy concerns and dependency on device hardware capabilities.

Why we list it for this wallet

PIN protection with randomized keypad or biometric authentication.

Source: Store

NFC (Near Field Communication)

NFC (Near Field Communication)

The wallet supports Near Field Communication (NFC) for wireless interaction with hardware wallets, payment terminals, or signing cards. NFC enables tap-to-sign or tap-to-pay functionality over a very short range (typically a few centimeters) without cables or QR codes.

  • Convenience: Quick tap interaction — no cables to connect or QR codes to scan.
  • Hardware wallet compatibility: Some hardware signing cards communicate exclusively via NFC.
  • Requires NFC hardware on both devices.
  • Very short range limits usability compared to QR-based air-gapped setups.

Why we list it for this wallet

NFC

Source: Website

Trade from and to other crypto currencies

Trade from and to other crypto currencies

Exchange one crypto currency for another. You “receive Xcoin to your Ycoin account” while in the background the wallet sends your Ycoin address to a service provider which gives it an Xcoin address which it then displays. Funds sent to that Xcoin address - to that service provider - are then sold for Ycoin and the returns are sent to the wallet’s Ycoin address.

Easily accept receiving more coins without actually holding them.

  • Sometimes the service is less favorable in its fees when used through a wallet integration than when using the service’s website.
  • Some of those services require registration which links your transactions to your ID.
  • The exchange provider might not deliver, making it complicated to prove what happened, who to talk to and how to ultimately recover funds.

Why we list it for this wallet

In-app exchange and trading

Source: Website

Product page updated by Leo Wandersleb, Daniel Andrei R. Garcia

>

Do your own research

In addition to reading our analysis, it is important to do your own checks. Before transferring any bitcoin to your wallet, look up reviews for the wallet you want to use. They should be easy to find. If they aren't, that itself is a reason to be extra careful.

Share on Social Media