Wallet Logo

Unstoppable Wallet

Latest release: 0.25.3 ( 24th June 2022 ) 🔍 Last analysed 7th August 2022 . Reproducible when tested Review might be outdated
3.7 ★★★★★
556 ratings
10 thousand
18th December 2018

Jump to verdict 

Older reviews (show 26 of 32 reproducible)

Help spread awareness for build reproducibility

Please follow Unstoppable Wallet and thank them for being reproducible  via their Twitter!

Disclaimer

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 questionable coding practice. Nasa sends probes to space that crash due to software bugs despite a huge budget and stringent scrutiny.

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.

The Analysis 

Here we test if the latest version can be reproduced, following the known procedure expressed in our test script (?):

===== Begin Results =====
appId:          io.horizontalsystems.bankwallet
signer:         c1899493e440489178b8748851b72cbed50c282aaa8c03ae236a4652f8c4f27b
apkVersionName: 0.24.2
apkVersionCode: 61
verdict:        reproducible
appHash:        50becb19846c2cd2f686a0ad40f2889f99793558f58941ab9a492f8fb817a899
commit:         fea4c5d96759a865408f92e661a13e10faa66226

Diff:
Only in /tmp/fromPlay_io.horizontalsystems.bankwallet_61/META-INF: MANIFEST.MF
Only in /tmp/fromPlay_io.horizontalsystems.bankwallet_61/META-INF: RELEASEK.RSA
Only in /tmp/fromPlay_io.horizontalsystems.bankwallet_61/META-INF: RELEASEK.SF

Revision, tag (and its signature):

===== End Results =====

which is what we want to see to give this wallet the verdict: reproducible

Thank you to Horizontal Systems for repeat donations

(lw)

Verdict Explained

The binary provided was reproducible from the code provided.

As part of our Methodology, we ask:

Does the binary we built differ from what we downloaded? If not, we tag it Reproducible

If we can reproduce the binary we downloaded from the public source code, with all bytes accounted for, we call the product reproducible. This does not mean we audited the code but it’s the precondition to make sure the public code has relevance for the provided binary.

If the provider puts your funds at risk on purpose or by accident, security researchers can see this if they care to look. It also means that inside the company, engineers can verify that the release manager is releasing the product based on code known to all engineers on the team. A scammer would have to work under the potential eyes of security researchers. He would have to take more effort in hiding any exploit.

“Reproducible” does not mean “verified”. There is good reason to believe that security researchers as of today would not detect very blatant backdoors in the public source code before it gets exploited, much less if the attacker takes moderate efforts to hide it. This is especially true for less popular projects.

But we also ask:

Does our review and verdict apply to their latest release? If not, we tag it Review Old!

Verdicts apply to very specific releases of products and never to the product as a whole. A new release of a product can change the product completely and thus also the verdict. This product remains listed according to its latest verdict but readers are advised to do their own research as this product might have changed for the better or worse.

This meta verdict is applied manually in cases of reviews that we identify as requiring an update.

This meta verdict applies to all products with verdict “reproducible” as soon as a new version is released until we test that new version, too. It also applies in cases where issues we opened are marked as resolved by the provider.

If we had more resources, we would update reviews more timely instead of assigning this meta verdict ;)