FuzeWLatest release: 1.2 ( 27th January 2019 ) 🔍 Last analysed 3rd December 2021 . No source for current release found Not updated in a long time
Help spread awareness for build reproducibility
Please help us spread the word discussing transparency with FuzeW 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 ¶
FuzeW refers to itself as a “wireless cryptocurrency hardware wallet.” It resembles a credit card, although it has both a screen and buttons.
It has a companion app for Android:
From the blog:
Security-Convenience compatible crypto wallet:
FuzeW - Secure as Ledger, Easy and Convenient as a mobile “Hot” wallet
FuzeW is a plastic, card-shaped hardware wallet that supports a wireless mobile connection via Bluetooth.
You can manage, send, and exchange your crypto assets anywhere securely that to its proprietary app, W manager.
We cannot find any public source code. It appears that this product is not verifiable.
Notably, according to the firmware release notes, FuzeW has last received a new update on 27th Jan 2019. This makes it obsolete by our definition.
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. You should still prefer actual open source licenses as a competing wallet won’t use the code without giving it careful scrutiny.
But we also ask:Was the product updated during the last two years? If not, we tag it Obsolete!
Bitcoin wallets are complex products and Bitcoin is a new, advancing technolgy. Projects that don’t get updated in a long time are probably not well maintained. It is questionable if the provider even has staff at hands that is familiar with the product, should issues arise.
This verdict may not get applied if the provider is active and expresses good reasons for not updating the product.
Share onTwitter Facebook LinkedIn
Or embed a widget in your website
<iframe src="https://walletscrutiny.com/widget/#appId=hardware/fuzew&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/fuzew&theme=auto&style=long" style="max-width:100%;width:342px;border:0;border-radius:10px;min-height:290px;"> </iframe>