Edge - Bitcoin, Ethereum, Monero, Ripple Walletlatest release: 2.0.15 last analysed 10th November 2019
Help spread awareness for build reproducibility
Please help us spread the word, asking Edge - Bitcoin, Ethereum, Monero, Ripple Wallet to support reproducible builds 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 ¶
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.
We could not verify that the provided code matches the binary!
As part of our Methodology, we ask:Is the published binary matching the published source code? If not, we tag it
Published code doesn’t help much if it is not what the published app was built from. That is why we try to reproduce the binary. We
- obtain the binary from the provider
- compile the published source code using the published build instructions into a binary
- compare the two binaries
- we might spend some time working around issues that are easy to work around
If this fails, we might search if other revisions match or if we can deduct the source of the mismatch but generally consider it on the provider to provide the correct source code and build instructions to reproduce the build, so we usually open a ticket in their code repository.
In any case, the result is a discrepancy between the app we can create and the app we can find on the app store 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.
Share onTwitter Facebook LinkedIn
Or embed a widget in your website
<iframe src="https://walletscrutiny.com/widget/#appId=android/co.edgesecure.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/co.edgesecure.app&theme=auto&style=long" style="max-width:100%;width:342px;border:0;border-radius:10px;min-height:290px;"> </iframe>