Wallet Logo

HODL Wallet : Bitcoin Wallet

Latest release: 1.12 ( 19th May 2020 ) 🔍 Last analysed 15th May 2022 . Not reproducible from source provided Not updated in a long time
4.1 ★★★★★
107 ratings
1st August 2018

Jump to verdict 

Help spread awareness for build reproducibility

Please help us spread the word, asking HODL Wallet : Bitcoin 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.

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 

On the App Store the provider claims:

Your Bitcoin are stored on your device and backed up to a Backup Recovery Key when you create a wallet. This means HODL Wallet can never stop you from accessing or sending your funds.

which is not very clear. The Backup part is a bit concerning but if they had access to that, the second sentence would be wrong. This should thus be a claim of being non-custodial.

HODL Wallet is free, open source

so in their source repository one could check the claim but as iPhone apps are all currently not reproducible, the app remains not verifiable.

(lw)

Verdict Explained

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 the answer is "no", we mark it as "Not reproducible from source provided".

Published code doesn’t help much if it is not what the published binary was built from. That is why we try to reproduce the binary. We

  1. obtain the binary from the provider
  2. compile the published source code using the published build instructions into a binary
  3. compare the two binaries
  4. 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 binary we can create and the binary we can find for download 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 binary 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.

But we also ask:

Was the product updated during the last two years?

If the answer is "no", we mark it as "Not updated in a long time".

Bitcoin wallets are complex products and Bitcoin is a new, advancing technolgy. Projects that don’t get updated in a long time are probably not well maintained. It is questionable if the provider even has staff at hands that is familiar with the product, should issues arise.

This verdict may not get applied if the provider is active and expresses good reasons for not updating the product.