Wallet Logo

Legacy Hexa (do not download)

Latest release: 1.7.4 ( 3rd December 2021 ) 🔍 Last analysed 29th December 2021 . Failed to build from source provided! Not functioning anymore
3.7 ★★★★★
23 ratings
1 thousand
26th March 2020

Jump to verdict 

Help spread awareness for build reproducibility

Please help us spread the word discussing build reproducibility with Legacy Hexa (do not download)  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 

Update 2021-12-29: As the name implies, this app was deprecated by its successor Hexa Bitcoin App Build Error! .

The page footer on their website answers most of our questions:

Bitcoin Only Wallet | Best Android Bitcoin Wallet | IOS Bitcoin Wallet | Non Custodial Bitcoin Wallet | Simple Bitcoin Wallet | Multisig wallet | Stack Sats | Donate Bitcoin | Bitcoin Donation | Buy bitcoin in UK | Crypto wallet | Send bitcoin | Beginners bitcoin wallet | Shamir Secret Sharing Bitcoin Wallet

So it’s “Non Custodial Bitcoin Wallet”. There is also a link to their Github and while not equipped with a FOSS license, it is public source code of a wallet.

So the build instructions looked lacking from the start as there is no word about building the apk but only about running the app, we tried it nevertheless:

$ git clone https://github.com/bithyve/hexa
$ cd hexa/
$ git checkout v1.4.1
$ docker run --rm -v$PWD:/mnt --workdir=/mnt -it walletscrutiny/android bash
root@af2c99dc5b57:/mnt# apt update
root@af2c99dc5b57:/mnt# apt install curl npm rubygems -y
root@af2c99dc5b57:/mnt# curl -sS https://dl.yarnpkg.com/debian/pubkey.gpg | apt-key add -
root@af2c99dc5b57:/mnt# echo "deb https://dl.yarnpkg.com/debian/ stable main" | tee /etc/apt/sources.list.d/yarn.list
root@af2c99dc5b57:/mnt# apt update
root@af2c99dc5b57:/mnt# apt install yarn -y
root@af2c99dc5b57:/mnt# npm install npm@latest -g
root@af2c99dc5b57:/mnt# npm install -g rn-nodeify
root@af2c99dc5b57:/mnt# gem install cocoapods
...
Building native extensions. This could take a while...
ERROR:  Error installing cocoapods:
	ERROR: Failed to build gem native extension.
...
root@7a3a4f43290e:/mnt# yarn install
...
patch cocoapods
./setup.sh: 14: pod: not found
Done in 132.25s.

and as the above is only the good guesses out of 35 commands typed so far, this is where we give up and consider the app not verifiable due to lacking build instructions.

(lw)

Verdict Explained

We encountered a build error while compiling from source code!

As part of our Methodology, we ask:

Build Error!

Can the product be built from the source provided?

If the answer is "no", we mark it as "Failed to build from source provided!".

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.

But we also ask:

Defunct!

Is the product still supported by the still existing provider?

If the answer is "no", we mark it as "Not functioning anymore".

Discontinued products or worse, products of providers that are not active anymore, are problematic, especially if they were not formerly reproducible and well audited to be self-custodial following open standards. If the provider hasn’t answered inquiries for a year but their server is still running or similar circumstances might get this verdict, too.