Archos Safe-T mini🔍 Last analysed 22nd August 2021 . No source for current release found
Help spread awareness for build reproducibility
Please help us spread the word discussing transparency with Archos Safe-T mini 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 ¶
Update 2021-08-22: As there is no claims of open source and nobody replied to our tweet, we consider this product closed source and therefore not verifiable for now. Just like the product’s successor:
The shop has a country picker to choose between France (default), Germany and UK. The product is shown as discontinued for Germany and UK.
The device has screen and buttons for transaction verification:
Every transaction is displayed on the screen and must be physically approved using hardware buttons.
On the provider website there is no claim about being open source but there is this repository according to which Archos Safe-T mini is a clone of but with no updates in three years.
Their Twitter account also has no activity since two years - with 13k followers.
There is more activity on their Facebook account but not regarding the Archos Safe-T mini. At least not the last two years.
As we are not sure if the GitHub account is even theirs, we asked on Twitter for clarification.
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.
Share onTwitter Facebook LinkedIn
Or embed a widget in your website
<iframe src="https://walletscrutiny.com/widget/#appId=hardware/archossafetmini&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/archossafetmini&theme=auto&style=long" style="max-width:100%;width:342px;border:0;border-radius:10px;min-height:290px;"> </iframe>