Wallet Logo

Bitcoin Wallet for COINiD

latest release: 1.8.0 ( 20th February 2021 ) last analysed  29th January 2020 Failed to build from source provided! 
4.4 ★★★★★
14 ratings
1 thousand
14th October 2018

Jump to verdict 

Help spread awareness for build reproducibility

Please help us spread the word discussing build reproducibility with Bitcoin Wallet for COINiD  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 

This app does not reveal much information on Google Play but

  • Complete Control
  • Hierarchical Deterministic

sounds like the standard non-custodial wallet.

The FAQ on their website is more explicit:

Do my private key ever leave my device? No, your private key never leaves your device. You are in full control of your private key.

And in the FAQ we find this gem:

Do you provide deterministic builds? Since we need to distribute the app via the App Store that is not possible. The source is however available on our Github so that anyone can review and compile it.

So let’s give it a try anyway …

The current version is 1.7.5. The build instructions in their entirety are:

COINiD Wallet

Proper readme coming soon. If you have any questions you can contact us on our Telegram or via Email.

Secrets.js

We are currently not including the secrets.js in the repo. If you want to compile the wallet to test it you need to add the following to src/config/secrets.js.

  export const p2pCommonSecret = '';
  export const encryptPrivateSalt = '';
  export const pinSecret = '';

That is not good but let’s see:

$ git clone git@github.com:COINiD/COINiDWallet.git
$ cd COINiDWallet/
$ git tag
v1.6.0
v1.7.0
v1.7.2
v1.7.3
v1.7.4
v1.7.5
$ git checkout v1.7.5
$ docker run --volume=$PWD:/mnt --workdir=/mnt --rm -it beevelop/cordova bash
root@c0a4b6139564:/mnt# echo "export const p2pCommonSecret = '';export const encryptPrivateSalt = '';export const pinSecret = '';" > src/config/secrets.js
root@c0a4b6139564:/mnt# apt update ; apt install python -y
root@c0a4b6139564:/mnt# npm install
root@c0a4b6139564:/mnt# yes | $ANDROID_HOME/tools/bin/sdkmanager "platforms;android-28"
root@c0a4b6139564:/mnt# cd android/
root@c0a4b6139564:/mnt/android# ./gradlew clean :app:assembleRelease
...
> Task :app:bundleReleaseJsAndAssets
warning: the transform cache was reset.
Loading dependency graph, done.
error While trying to resolve module `lottie-react-native` from file `/mnt/src/components/CheckBoxSelect.js`, the package `/mnt/node_modules/lottie-react-native/package.json` was successfully found. However, this package itself specifies a `main` module field that could not be resolved (`/mnt/node_modules/lottie-react-native/lib/index.js`. Indeed, none of these files exist:

  * `/mnt/node_modules/lottie-react-native/lib/index.js(.native||.android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx)`
  * `/mnt/node_modules/lottie-react-native/lib/index.js/index(.native||.android.js|.native.js|.js|.android.json|.native.json|.json|.android.ts|.native.ts|.ts|.android.tsx|.native.tsx|.tsx)`. Run CLI with --verbose flag for more details.

> Task :app:bundleReleaseJsAndAssets FAILED

FAILURE: Build failed with an exception.

* What went wrong:
Execution failed for task ':app:bundleReleaseJsAndAssets'.
> Process 'command 'node'' finished with non-zero exit value 1

* Try:
Run with --stacktrace option to get the stack trace. Run with --info or --debug option to get more log output. Run with --scan to get full insights.

* Get more help at https://help.gradle.org

Deprecated Gradle features were used in this build, making it incompatible with Gradle 6.0.
Use '--warning-mode all' to show the individual deprecation warnings.
See https://docs.gradle.org/5.1.1/userguide/command_line_interface.html#sec:command_line_warnings

BUILD FAILED in 25s
190 actionable tasks: 174 executed, 16 up-to-date

And that’s where we give it up and conclude with the verdict: not verifiable

(lw)

Verdict Explained

We encountered a build error while compiling from source code!

As part of our Methodology, we ask:

Can the product be built from the source provided? If not, we tag it Build Error! 

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.