Wallet Logo

Bitriel: Crypto & Bitcoin Wallet

Latest release: 3.4.0 ( 15th February 2022 ) 🔍 Last analysed 7th March 2022 . Not reproducible from source provided Not functioning anymore
4.2 ★★★★★
96 ratings
10 thousand
22nd February 2021

Jump to verdict 

Help spread awareness for build reproducibility

Please help us spread the word, asking Bitriel: Crypto & 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 

Update 2022-02-26: This app is not available anymore.

App Description

Digital wallet management for cross-chain assets, staking and governance operations, collection and self-owned private key.

Google Play Critical Reviews

Adenu Godspower
★☆☆☆☆ April 21, 2021
Hello BITRIEL, I have downloaded wallet and done all the needful but I am not seen any sel token each I claim. If you guys are not real then don’t allow someone waste his/her time and resources referring friends to download your app. I am still waiting for the airdrop but if i didn’t get it then I will delete your app and move on.

childish forever
★★☆☆☆ May 14, 2021
Everytime, I’m trying to get my free token but it always says 👉Failed to connect to Selendra remote node “” What this mean? I do submitted the required info to get the free airdrops,! I will edit my reviews soon.

The Site

Experience the Power of DeFi with Bitriel

  • Launch App button - redirects to app.bitriel.com (This site can’t be reached)
  • Read More button - does not elicit any response from the browser

About Us Section

The Selendra platform is used to build, deploy, and employ decentralized, peer-2-peer applications, as simple as the web and mobile applications we use today.

Terms of Use

The company is based in Cambodia.

Bitriel describes the wallet as “Selendra”

Selendra wallet, the Wallet: an open source, non-custodial (meaning the cryptographic keys of the user is stored on user’s own device) wallet software to be used for transactions on the Stellar network.

External references

The service facilitated an airdrop for their token called SEL and this was documented on Youtube.

The App

Once we downloaded the app, we are presented with the option to create or import a wallet. We were provided with a 12-word seed phrase. We were then asked to provide a username and a pin.

The dashboard shows at least 5 cryptocurrencies and tokens in this order:

  • SEL
  • SEL (v2 - BEP-20)
  • KGO
  • BNB
  • BTC

The BTC Wallet

There are only two options for the BTC Wallet: Transfer and Recieved (sic)

Transfer

Allows the user to transfer assets. The fields for Transfer are: Scan wallet, Fill wallet, Invite friend.

Fill Wallet

  • Receiver address
  • Asset (includes a dropdown menu with options: SEL, DOT, BNB, ETH, SEL (BEP-20), KGO (BEP-20) and BTC
  • Amount
  • Button for “Request Code”

Received

Once clicked it displays a QR code with a Native SegWith Bech32 Address that is prefixed by bc1.

The mnemonic provided upon opening the app seems to be for the entire wallet which supports multiple cryptocurrencies and tokens. It is not exclusive for the Bitcoin wallet.

Verdict

The bitriel repository seems to have been forked from Selendra which explains why in some cases bitriel is referred to as Selendra. We were only able to find the repository on github by searching as we were not able to find a direct link from the app’s homepage.

Verification

We were not able to verify this app.

(dg)

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:

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.