D'CENT Biometric Walletlatest release: v2.16.7.bdd9 ( 25th November 2021 ) last analysed 4th December 2021 No source for current release found
Help spread awareness for build reproducibility
Please help us spread the word discussing transparency with D'CENT Biometric Wallet 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.
The Analysis ¶
Private keys can be created offline - ✔️
Private keys are created when creating a new wallet.
The process for initialization can be found on the D’CENT user guide:
Step 1. Select Language and Create Wallet
- Power on D’CENT Biometric Wallet
- Select Language
- Select “Create a Wallet”
Step 2. Register PIN and Fingerprint
- Register a new PIN
- Verify your PIN
- Register Fingerprint
- Verify Fingerprint
Step 3. Write down the recovery seeds
- Before you begin - What are recovery seeds
- Write down the recovery seeds
- Recovery seeds verification
Step 4. Completing the Intitial Setup
- Check for the latest Firmware
Private keys are not shared - ✔️
The device can connect via BlueTooth or USB to an Android or iOS app by the same developer.
Device displays receive address for confirmation - ✔️
The device has a 1.1 inch OLED display (128x128 pixels)
Interface - ✔️
The device has a large enough display to show the public address of the wallet as well as the keys. There are also buttons to help the user navigate the options in the device.
Code and Reproducibility
As with the associated mobile app, there are no outward claims that the D’CENT wallet is open source. While they do have several repositories on GitHub and one pertaining to their ‘Biometric Firmware’, these merely include images or bin files that have no build instructions or other information.
Without public source of the reviewed release available, this product cannot be verified!
As part of our Methodology, we ask:Is the source code publicly available? If not, we tag it No Source!
A wallet that claims to not give the provider the means to steal the users’ funds might actually be lying. In the spirit of “Don’t trust - verify!” you don’t want to take the provider at his word, but trust that people hunting for fame and bug bounties could actually find flaws and back-doors in the wallet so the provider doesn’t dare to put these in.
Back-doors and flaws are frequently found in closed source products but some remain hidden for years. And even in open source security software there might be catastrophic flaws undiscovered for years.
An evil wallet provider would certainly prefer not to publish the code, as hiding it makes audits orders of magnitude harder.
For your security, you thus want the code to be available for review.
If the wallet provider doesn’t share up to date code, our analysis stops there as the wallet could steal your funds at any time, and there is no protection except the provider’s word.
“Up to date” strictly means that any instance of the product being updated without the source code being updated counts as closed source. This puts the burden on the provider to always first release the source code before releasing the product’s update. This paragraph is a clarification to our rules following a little poll.
We are not concerned about the license as long as it allows us to perform our analysis. For a security audit, it is not necessary that the provider allows others to use their code for a competing wallet.
Share onTwitter Facebook LinkedIn
Or embed a widget in your website
<iframe src="https://walletscrutiny.com/widget/#appId=hardware/dcentbiometric&theme=auto&style=short" name="_ts" style="min-width:180px;border:0;border-radius:10px;max-width:280px;min-height:30px;"> </iframe>
<iframe src="https://walletscrutiny.com/widget/#appId=hardware/dcentbiometric&theme=auto&style=long" style="max-width:100%;width:342px;border:0;border-radius:10px;min-height:290px;"> </iframe>