QPocket: ETH TRON QKC Crypto Wallet with DAppslatest release: 5.4.2 ( 6th May 2021 ) last analysed 19th October 2021 No source for current release found
Help spread awareness for build reproducibility
Please help us spread the word discussing transparency with QPocket: ETH TRON QKC Crypto Wallet with DApps 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 ¶
From Google Play:
QPocket is a secure mobile crypto wallet that supports Ethereum (ETH) , ERC20, Tron (TRX) tokens and their DApps. It aims to provide users with a simple, secure and fully functional portal to blockchain, which offers asset management, DApps, payment, exchanges and more functions.
QPocket can also support BTC wallets. It advertises being able to use one crypto wallet, with multiple crypto assets.
Users can own Ethereum (ETH) , ERC20, Tron (TRX) accounts at the same time by creating only one HD wallet address. EOS, Bitcoin (BTC), Litecoin (LTC), DASH, Ripple (XRP) and more to come!
In the official website, QPocket says that it has the capability to support multiple HD wallets.
Users can import mnemonics created in other wallets and have infinite sub wallets for free.
We tried the app. We were provided with the 12-word mnemonic and then asked to save it.
The repositories last commit is from “Jun 18, 2020” and contains only 5 commits for version 5.3.1. On the other hand, the google play app was last updated in May 6, 2021, at version 5.4.2 and has had several versions before that.
Unfortunately, as this source code is outdated, we cannot verify this app.
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=android/com.quarkonium.qpocket&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=android/com.quarkonium.qpocket&theme=auto&style=long" style="max-width:100%;width:342px;border:0;border-radius:10px;min-height:290px;"> </iframe>