Win WalletLatest release: 2.6.4 ( 2nd July 2021 ) 🔍 Last analysed 15th November 2021 . No source for current release found
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 ¶
The original description is in Russian and has been translated to English. It claims that this wallet is self-custodial and that it provides the private keys to the wallet owners.
Win Wallet is a decentralized multi-currency crypto wallet for iOS. Information about private keys and passwords is kept only by wallet owners. The exchange takes place directly between users. The system cannot influence the process or steal funds.
It’s a small website with no mentions of source code or any social media links. From the homepage:
We do not store users’ cryptocurrency and fiat on our platforms, we do not have access to users’ wallets and passwords, we do not store information about users’ on our servers. We will continue to adhere to this concept in any market realities.
There’s no information on the website concerning the source code or a Github account or repository.
We downloaded the app to test it out. We were asked to set a 5-digit PIN to access the app. We were able to successfully create a BTC wallet, as well as backup the 12-word mnemonic. This app also lets you send and receive.
This is a self-custodial app, meaning that you are in control of the keys. On the other hand, searching their appID ‘com.wise.llc.wallet.app’ on Github does not return relevant results. With nothing to be found about source code, we conclude that this app is not verifiable.
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. You should still prefer actual open source licenses as a competing wallet won’t use the code without giving it careful scrutiny.
Share onTwitter Facebook LinkedIn
Or embed a widget in your website
<iframe src="https://walletscrutiny.com/widget/#appId=android/com.wise.llc.wallet.app&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.wise.llc.wallet.app&theme=auto&style=long" style="max-width:100%;width:342px;border:0;border-radius:10px;min-height:290px;"> </iframe>