Menu
The Chia Plot
  • Blog
  • How-To
  • About
  • Contact
  • Security
  • Discord
The Chia Plot

Lets talk about Nucle and Chia wallet security

Posted on August 23, 2021August 23, 2021 by Chris Dupres

Now that Nucle, Chia’s first SPV wallet, is in open beta and anyone can sign up lets talk about Chia wallet security a little bit. I have spoken before about how I don’t think security is very well understood in the cryptocurrency world, with lots of claims being made about one thing being more secure than another devoid of context and without a threat model. This is bad, and reminds me a little bit of general internet security 15 or 20 years ago.

There are two main threats to a cryptocurrency wallet, regardless of where it is hosted, and those are

  • someone will gain access to your wallet without permission
  • someone will spend coin from your wallet without having access

So all security decisions should be made those two scenarios in mind. Lets deal with the second threat first here, the idea that someone will be able to execute a spend without access to your wallet. On a centralized banking system the main way that would occur is a back end compromise where database level changes are made that move money from your account to another. Your primary protection from this is a series of laws, regulators and mandatory deposit insurance on banks. Basically if someone that isn’t you spends your money you should get it back.

In cryptocurrency the main defense to this threat is cryptographic. It would generally take longer than the lifetime of the earth to forge a proper transaction on a properly secured blockchain, so its not usually considered a major risk. The main risk here would be a software flaw that allows a malicious actor to make the wallet software with proper keys to create a transaction and spend coin without the wallet owner’s permission. This has happened before, even with hardware wallets like Ledger, and is a real threat.

That brings us to Nucle, and other online wallets. Right now there are two ways you can use a wallet online. The first, is Nucle where you control the keys and it works like a browser application where all encryption is handled by the browser and the Nucle servers don’t see your keys and cannot create a transaction on your behalf. That’s the theory, and the goal anyway. We will be able to confirm this once they open their source code, so for now we will assume they are telling the truth. The second is the wallets held on cryptocurrency exchanges. These are not really wallets in the sense that Nucle is, but they are functionally similar at a glance. An exchange wallet has none of the protection of Nucle. It is merely a database that stores values that correspond to your account, and any back-end compromise can lead to their coin being taken and leaving you with nothing. Because they also have none of the safety mechanisms that traditional banking systems offer. If anything does happen and they just don’t pay you out you are left with the civil court system, and that can be less than effective against shadowy organizations in sparsely regulated foreign countries.

So from that perspective Nucle offers significant security improvements over any Exchange hosted wallet. Minus a software bug and they actually do hold keys then it shouldn’t be possible for someone to spend without the key. So how safe is the key? Nucle supports 12 word mnemonics instead of the standard 24 word Chia Network wallet. So is it secure?

In a nutshell, yes. There is a really good writeup on BIP39 (the standard we are discussing here, thanks Speedmann) and if you read through it you will see that the difference between a 128bit (12 word) or 256bit (24 word) mnemonic are almost academic. In both cases they are hashed 2048 times with a salt to produce a SHA512 512bit seed value. Because of the salt 2 people using the same set of words will derive different seeds. This 512bit seed is then used to produce the key protecting your wallet. Is a 24 word key more secure? Technically yes. Will it matter in the near or intermediate future? Probably not. This is not a situation where the cipher strength is changed by the length of the pass phrase because the key is the same strength at the end. And because it takes so long to run a Password Based Key Derivation Function they are incredibly hard to brute force. They take some time to create, and with the standard 2048 word list the brute force requirements are below:

  • 12 words: 5.4445178707350154154139937189083e+39 (divided by half for probability of getting the key)
  • 24 words: 2.9642774844752946028434172162224e+79 (divided by half for probability of getting the key)

As you can see HUGE difference. But in either example it will take billions of years to brute force a key even using all the computing power in the world. So if you notice the heat death of the universe approaching it might be time to transfer your balance to a 24 word wallet. So in either case a user is highly unlikely to get access to your wallet through brute force, so your main exposure to the first threat is going to be losing or having your keys stolen. This comes down to personal and operational security, and that is a much longer post. In a nutshell, protect your keys as well as you can lest you end up like this person.

Because the actual wallets are cryptographically secure to the point of being more than good enough, it all comes down to the code. This is true with all wallet types, software hardware and cloud. Hardware wallets can have their firmware flashed to execute spends, online wallets like the Chia windows client can conceivably be exploited to initiate a spend from a logged in wallet using RPC and Nucle can possibly have your session hijacked and a spend executed on your behalf without the keys. These are possibilities for any system, and the likelihood will depend on the specifics of the code. But its a good idea to consider every system susceptible to compromise eventually. No code is perfect. So from a security perspective Nucle is perfectly fine for a hot wallet, but not for a cold wallet. And neither is the official Chia client nor any wallet I am aware of yet.

Related

Leave a Reply Cancel reply

Advertisement

Recent Posts

  • Crypto is burning down – Chia seems fine
  • Chia CAT upgrade fiasco part 2 – Was I wrong?
  • WTF just happened?? CAT1 to CAT2 “upgrade”
  • The era of the Chia NFT is upon us
  • Chia Blockchain 1.4.0 released – NFTs and DIDs oh my
  • Discussion
  • Facts About Farmers
  • How-To
  • Information
  • News
  • pools
  • Security
  • Trademark
  • Trading
  • Uncategorized

Dark Mode Switch

©2021 The Chia Plot - Donate XCH / MRMT / SBX @ xch1p4440d6zwu9ryta2vx073lq2ge3s29d37kskz6t34jp085e8srjqnk0gcr
We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits. By clicking “Accept All”, you consent to the use of ALL the cookies. However, you may visit "Cookie Settings" to provide a controlled consent.
Cookie SettingsAccept All
Manage consent

Privacy Overview

This website uses cookies to improve your experience while you navigate through the website. Out of these, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website. We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may affect your browsing experience.
Necessary
Always Enabled
Necessary cookies are absolutely essential for the website to function properly. These cookies ensure basic functionalities and security features of the website, anonymously.
CookieDurationDescription
cookielawinfo-checkbox-advertisement1 yearThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Advertisement".
cookielawinfo-checkbox-analytics11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Analytics".
cookielawinfo-checkbox-functional11 monthsThe cookie is set by GDPR cookie consent to record the user consent for the cookies in the category "Functional".
cookielawinfo-checkbox-necessary11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookies is used to store the user consent for the cookies in the category "Necessary".
cookielawinfo-checkbox-others11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Other.
cookielawinfo-checkbox-performance11 monthsThis cookie is set by GDPR Cookie Consent plugin. The cookie is used to store the user consent for the cookies in the category "Performance".
JSESSIONIDsessionUsed by sites written in JSP. General purpose platform session cookies that are used to maintain users' state across page requests.
viewed_cookie_policy11 monthsThe cookie is set by the GDPR Cookie Consent plugin and is used to store whether or not user has consented to the use of cookies. It does not store any personal data.
Functional
Functional cookies help to perform certain functionalities like sharing the content of the website on social media platforms, collect feedbacks, and other third-party features.
CookieDurationDescription
na_id1 year 1 monthThis cookie is set by Addthis.com to enable sharing of links on social media platforms like Facebook and Twitter
na_rn1 monthThis cookie is used to recognize the visitor upon re-entry. This cookie allows to collect information on user behaviour and allows sharing function provided by Addthis.com
na_sc_e1 monthThis cookie is used to recognize the visitor upon re-entry. This cookie allows to collect information on user behaviour and allows sharing function provided by Addthis.com
na_sr1 monthThis cookie is set by Addthis.com. This cookie is used for sharing of links on social media platforms.
na_srp1 minuteThis cookie is used to recognize the visitor upon re-entry. This cookie allows to collect information on user behaviour and allows sharing function provided by Addthis.com
na_tc1 year 1 monthThis cookie is set by the provider Addthis. This cookie is used for social media sharing tracking service.
ouid1 year 1 monthThe cookie is set by Addthis which enables the content of the website to be shared across different networking and social sharing websites.
Performance
Performance cookies are used to understand and analyze the key performance indexes of the website which helps in delivering a better user experience for the visitors.
CookieDurationDescription
d3 monthsThis cookie tracks anonymous information on how visitors use the website.
Analytics
Analytical cookies are used to understand how visitors interact with the website. These cookies help provide information on metrics the number of visitors, bounce rate, traffic source, etc.
CookieDurationDescription
__gads1 year 24 daysThis cookie is set by Google and stored under the name dounleclick.com. This cookie is used to track how many times users see a particular advert which helps in measuring the success of the campaign and calculate the revenue generated by the campaign. These cookies can only be read from the domain that it is set on so it will not track any data while browsing through another sites.
_ga2 yearsThis cookie is installed by Google Analytics. The cookie is used to calculate visitor, session, campaign data and keep track of site usage for the site's analytics report. The cookies store information anonymously and assign a randomly generated number to identify unique visitors.
_gat_gtag_UA_199099757_11 minuteThis cookie is set by Google and is used to distinguish users.
_gid1 dayThis cookie is installed by Google Analytics. The cookie is used to store information of how visitors use a website and helps in creating an analytics report of how the website is doing. The data collected including the number visitors, the source where they have come from, and the pages visted in an anonymous form.
CONSENT16 years 4 months 5 daysThese cookies are set via embedded youtube-videos. They register anonymous statistical data on for example how many times the video is displayed and what settings are used for playback.No sensitive data is collected unless you log in to your google account, in that case your choices are linked with your account, for example if you click “like” on a video.
Advertisement
Advertisement cookies are used to provide visitors with relevant ads and marketing campaigns. These cookies track visitors across websites and collect information to provide customized ads.
CookieDurationDescription
advanced_ads_browser_width1 monthThis cookie is set by Advanced ads plugin.This cookie is used to measure and store the user browser width for adverts.
anj3 monthsNo description available.
CMID1 yearThe cookie is set by CasaleMedia. The cookie is used to collect information about the usage behavior for targeted advertising.
CMPRO3 monthsThis cookie is set by Casalemedia and is used for targeted advertisement purposes.
CMPS3 monthsThis cookie is set by Casalemedia and is used for targeted advertisement purposes.
CMRUM31 yearThis cookie is set by Casalemedia and is used for targeted advertisement purposes.
CMST1 dayThe cookie is set by CasaleMedia. The cookie is used to collect information about the usage behavior for targeted advertising.
DSID1 hourThis cookie is setup by doubleclick.net. This cookie is used by Google to make advertising more engaging to users and are stored under doubleclick.net. It contains an encrypted unique ID.
i1 yearThe purpose of the cookie is not known yet.
IDE1 year 24 daysUsed by Google DoubleClick and stores information about how the user uses the website and any other advertisement before visiting the website. This is used to present users with ads that are relevant to them according to the user profile.
KADUSERCOOKIE3 monthsThe cookie is set by pubmatic.com for identifying the visitors' website or device from which they visit PubMatic's partners' website.
KTPCACOOKIE1 dayThis cookie is set by pubmatic.com for the purpose of checking if third-party cookies are enabled on the user's website.
mc1 year 1 monthThis cookie is associated with Quantserve to track anonymously how a user interact with the website.
test_cookie15 minutesThis cookie is set by doubleclick.net. The purpose of the cookie is to determine if the user's browser supports cookies.
uid1 year 1 monthThis cookie is used to measure the number and behavior of the visitors to the website anonymously. The data includes the number of visits, average duration of the visit on the website, pages visited, etc. for the purpose of better understanding user preferences for targeted advertisments.
uuid3 monthsTo optimize ad relevance by collecting visitor data from multiple websites such as what pages have been loaded.
uuid23 monthsThis cookies is set by AppNexus. The cookies stores information that helps in distinguishing between devices and browsers. This information us used to select advertisements served by the platform and assess the performance of the advertisement and attribute payment for those advertisements.
VISITOR_INFO1_LIVE5 months 27 daysThis cookie is set by Youtube. Used to track the information of the embedded YouTube videos on a website.
YSCsessionThis cookies is set by Youtube and is used to track the views of embedded videos.
yt-remote-connected-devicesneverThese cookies are set via embedded youtube-videos.
yt-remote-device-idneverThese cookies are set via embedded youtube-videos.
Others
Other uncategorized cookies are those that are being analyzed and have not been classified into a category as yet.
CookieDurationDescription
__gpi1 year 24 daysNo description
adImpCountpastNo description
C3UID5 yearsNo description available.
C3UID-9245 yearsNo description
fc5 months 27 daysNo description available.
pfpastNo description
pxs5 months 27 daysNo description available.
SAVE & ACCEPT
Powered by CookieYes Logo