Wallet Logo

BITHD Razor Pro

🔍 Last analysed 23rd November 2022 . No source for current release found
24th October 2022

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 the answer is "no", we mark it as "No source for current release found".

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. You should still prefer actual open source licenses as a competing wallet won’t use the code without giving it careful scrutiny.

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.

Help spread awareness for build reproducibility

Please help us spread the word discussing transparency with BITHD Razor Pro  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 product is the PRO version to the BITHD Razor Unreproducible! Discontinued

It features a thicker frame and support for Type-C USB.

According to the only linked-to documentation, the device is linked to the Bitpie Wallet No Source!

We were not able to find a new repository apart from the original BitHD repository. We tweeted what we believe to be the developers of this device.

Can the private keys be created offline?

The device is paired with the Bitpie Wallet app. If the Razor PRO is similar to the Razor, then the mnemonic phrases are displayed on the device after it is paired with the app.

We can see a demo of this for the Razor on YouTube.

Does the device display the receive address for confirmation?


Does the device have both input and output?”


Input: 2 Buttons Output: Screen (OLED 128*64)

The product does not offer a link to a different repository. Until such time that the developers respond to our question on twitter, we would have to assume that the firmware for the Razor Pro is different from the Razor, and is therefore not yet publicly available.