Nash: Spend, save & invest
Latest release: 13.4.1 ( 31st October 2022 ) đ Last analysed 30th April 2021 . No source for current release foundHelp spread awareness for build reproducibility
Please help us spread the word discussing transparency with Nash: Spend, save & invest 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 statement in the description from the play store below is a claim only the user has access to the private keys.
Nash doesnât take control of your funds â unlike Coinbase, Kraken or Binance. Weâre the only fully-featured exchange where you can trade Bitcoin without giving up your private keys.
With keys in control of the user, we need to find the source code in order to check reproducibility. However we are unable to locate a public source repository.
Our verdict: As there is no source code to be found anywhere, this wallet is at best a non-custodial closed source wallet and as such not verifiable.
(ml)
Verdict Explained
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.
Share on
Twitter Facebook LinkedInOr embed a widget in your website
<iframe
src="https://walletscrutiny.com/widget/#appId=android/io.nash.app&theme=auto&style=short" name="_ts"
style="min-width:180px;border:0;border-radius:10px;max-width:280px;min-height:30px;">
</iframe>
and
<iframe
src="https://walletscrutiny.com/widget/#appId=android/io.nash.app&theme=auto&style=long"
style="max-width:100%;width:342px;border:0;border-radius:10px;min-height:290px;">
</iframe>