Defiantlatest release: 1.2.7 ( 12th November 2021 ) last analysed 15th November 2021 No source for current release found
Help spread awareness for build reproducibility
Please help us spread the word discussing transparency with Defiant 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 ¶
Defiant allows you to secure, manage, and exchange cryptocurrencies like Bitcoin, Ethereum, and much more from a easy-to-use wallet that puts you in control of your assets.
Here’s why Defiant is unique:
YOUR KEYS, YOUR CONTROL Defiant is a self-custodial wallet. Only you can access your assets. Your keys and crypto always stay in your control.
When we installed the app, it first asked to create a pin. Then it asked whether we wanted to “Import” or “Create a Wallet”. We chose create a wallet, then we were given a 12-word backup.
There was no mention that the project was open source. In the case that we may have missed something, we tried searching for Defiant app’s appID ‘ar.com.andinassmart.defiant’ on Github, but it yielded 0 repositories. We also tried searching for ‘Defiant App’ with 2 unrelated repositories.
We have to conclude that this is not an open source project. If the source code is not publicly available, then the app cannot be verified.
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/ar.com.andinasmart.defiant&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/ar.com.andinasmart.defiant&theme=auto&style=long" style="max-width:100%;width:342px;border:0;border-radius:10px;min-height:290px;"> </iframe>