As part of our Methodology, we ask:
Published code doesn’t help much if the app fails to compile.
We try to compile the published source code using the published build instructions into a binary. If that fails, we might try to work around issues but if we consistently fail to build the app, we give it this verdict and open an issue in the issue tracker of the provider to hopefully verify their app later.
The product 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 product 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.Show Older Reviews
The Analysis ¶
This does not represent a full code review.
Update 2022-01-24: The provided build instructions don’t work anymore as explained in this issue.
Update 2021-07-20: The provider appears to be working on a re-write of the app, so the former issue is not expected to get resolved on the old repository.
Here we test if the latest version can be verified, following the known procedure expressed in our test script (?):
fatal: Remote branch v1.4.2 not found in upstream origin
The provider failed to tag a revision with the latest version and the app therefore is not verifiable.
(lw)
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.
If you find something we should include, you can create an issue or edit this analysis yourself and create a merge request for your changes.