Enjin: NFT Crypto WalletLatest release: 1.15.1 ( 9th September 2021 ) 🔍 Last analysed 4th September 2021 . No source for current release found
Help spread awareness for build reproducibility
Please help us spread the word discussing transparency with Enjin: NFT Crypto 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 ¶
Update 2022-01-04: The iOS app is available again. (Twitter Screenshot)
Update 2021-08-26: This app is no more.
Enjin: Blockchain & Crypto Wallet description starts promising:
“Your private keys are your own”
They advertise advanced securing techniques among which are:
An extensive independent security audit and penetration test found no security issues.
(You can read the report here)
But source code isn’t available on their website. So the user is left with only one choice: trust.
Our verdict: not verifiable.
in-app browsing: “ENJOY SEAMLESS BROWSING Interact with any DApp with the single click of a button—without leaving the safety of your crypto wallet.”
looks very advanced, the list of features is tremendous. also an old player:
Founded in 2009 and based in Singapore, Enjin offers an ecosystem of integrated, user-first blockchain products that enable anyone to easily manage, explore, distribute, and integrate blockchain-based assets.
on their main page, they advertise advanced securing techniques amongst which are:
- Custom ARM instructions ensure that sensitive data is instantly deleted from your phone’s memory.
- Enjin Keyboard. Built from scratch to protect you from any form of data sniffing or keyloggers.
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=iphone/com.enjin.mobile.wallet&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=iphone/com.enjin.mobile.wallet&theme=auto&style=long" style="max-width:100%;width:342px;border:0;border-radius:10px;min-height:290px;"> </iframe>