This app was first launched on 1st March 2018 and currently has more than 100000 downloads, a 4.2 stars rating from 733 users and the latest APK (version 1.11.4) was from 27th January 2020 and is newer than the below reviewed version of the app.
Our analysis was done on 10th November 2019 based on data found in their Playstore description and their website and their source repository. We discuss the issue with verification with the provider here.
We found these ways of contacting the developers:
The following Analysis is not a full code review! We plan to make code reviews available in the future but even then it will never be a stamp of approval but rather a list of incidents and bad coding practice. We cannot find and tell you all the dark secrets the wallet providers might have.
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.
Edge - Bitcoin, Ethereum, Monero, Ripple Wallet is the successor of Airbitz and claims to be non-custodial and open source.
The Playstore description points to this link as
their open source, where we are greeted with “This organization has no public
repositories.”. Not good. But … above we find
*** WE'VE MOVED. See
github.com/EdgeApp *** and sure enough,
this looks better.
So here we have to give up for now. We cannot find any claim of verifiability of the builds but worse, the wording of the build Requirements doesn’t sound as if it was well established what was needed to successfully build the wallet at all.
Edge is known to build with this exact tool set. Updated versions of these toolsets may break the build or app. If you have issues, try mirroring these exact versions.
Android Studio 3.1.3 is a requirement? Version 3.5.1 being the current version I would not be too happy to down-grade but for our standards of verification being easy, we would probably require the verification to be possible to automate meaning to at least work head-less in a docker container for example. A Docker container would allow to define all the versions nicely and we hope the wallet will provide such verification support soon.
Lastly the app can currently not be verified because the playstore version
1.10.1 is ahead of the latest tag
published on GitHub being
This wallet is currently not verifiable.
Not verifiable: The provided Open Source Code could not be verified to match the app released on Google Play
This verdict means that the provider did share some source code but that we could not verify that this source code matches the released app. This might be due to the source being released later than the app or due to the provided instructions on how to compile the app not being sufficient or due to the provider excluding parts from the public source code. In any case, the result is a discrepancy between the app we can create and the app we can find on GooglePlay and any discrepancy might leak your backup to the server on purpose or by accident.
As we cannot verify that the source provided is the source the app was compiled from, this category is only slightly better than closed source but for now we have hope projects come around and fix verifiability issues.
The app 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 app 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.