Wallet Logo

Bitcoin Wallet by Bitorzo.com
(Actually "Bitcoin Wallet". For details read below.)

latest release: 3.1.3 last analysed  11th April 2021 Not reproducible from source provided  
4.0 ★★★★★
26 ratings
1thousand
22nd July 2020

Jump to verdict 

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 

This app is self-custodial:

Main features:

  • Private keys never leave your device, and strongly encrypted on it!

and a Bitcoin wallet (the app’s name is “Bitcoin Wallet”).

On their website there’s also a link to the source code on GitHub and there we can find … build instructions:

Android (armeabi-v7a): flutter build apk
Android (arm64-v8a): flutter build apk --target=android-arm64

So lets see:

$ git clone https://github.com/Bitorzo/Bitorzo
$ cd Bitorzo
$ docker run -it --volume $PWD:/mnt --workdir /mnt --rm beevelop/cordova bash
# apt update
# apt install xz-utils -y
# tar xf ./flutter_linux_2.0.1-stable.tar.xz 
# flutter/bin/flutter build apk
...
Because every version of manta_dart from git depends on decimal ^1.0.0 and bitorzo_wallet_flutter depends on decimal ^0.3.5, manta_dart from git is forbidden.
So, because bitorzo_wallet_flutter depends on manta_dart from git, version solving failed.
Running "flutter pub get" in mnt...                                     
pub get failed (1; So, because bitorzo_wallet_flutter depends on manta_dart from git, version solving failed.)

This message is slightly different to what Emanuel got but we both failed to build the app from the source with the build instructions as provided.

The app is therefore not verifiable.

(lw, em)

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 not, we tag it Unreproducible!  

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

  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 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.

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.