WanWalletlatest release: 5.0 ( 25th April 2021 ) last analysed 30th November 2021 No source for current release found
Help spread awareness for build reproducibility
Please help us spread the word discussing transparency with WanWallet via their Twitter!
Do your own research!
Try out searching for "lost bitcoins", "stole my money" or "scammers" together with the wallet's name, even if you think the wallet is generally trustworthy. For all the bigger wallets you will find accusations. Make sure you understand why they were made and if you are comfortable with the provider's reaction.
The Analysis ¶
UPDATE 2021-11-23 There’s no source code for the android app on Github, making the app not verifiable.
WanWallet was developed by Wanchain Foundation. It says that it supports Wanchain Galaxy Consensus Staking, which they also call “PoS Staking.”
You can manage your Wanchain assets and stake your Wancoins to receive staking rewards using Wanchain Wallet.
Wanchain Wallet is a non-custodial wallet, which means you own the keys and you are in control. Wanchain Foundation will never ask you for your HD seed phrase under any circumstances.
We tried the app. We are immediately greeted with the option to create a wallet or import one.
We chose to create a wallet and were asked to enter a password. Then, we are provided with a 12-word seed phrase, and told to record it in a safe place, preferably offline. The app noting that:
the Wanchain team will never ask for your seed phrase.
Wanchain has a Github account with repositories for apps and SDKs. Their repository for the desktop wallet is publicly available source code with build instructions.
At the moment, we will wait for the source-code to be tested and proved reproducible before making a verdict.
Without public source of the reviewed release available, this product cannot be verified!
As part of our Methodology, we ask:Is the source code publicly available? If not, we tag it No Source!
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.
Share onTwitter Facebook LinkedIn
Or embed a widget in your website
<iframe src="https://walletscrutiny.com/widget/#appId=android/com.wanchain.WanWallet&theme=auto&style=short" name="_ts" style="min-width:180px;border:0;border-radius:10px;max-width:280px;min-height:30px;"> </iframe>
<iframe src="https://walletscrutiny.com/widget/#appId=android/com.wanchain.WanWallet&theme=auto&style=long" style="max-width:100%;width:342px;border:0;border-radius:10px;min-height:290px;"> </iframe>