In this episode of Bitcoin, Explained, hosts Aaron van Wirdum and Sjors Provoost discuss Hierarchical Deterministic (HD) Wallets, mnemonic codes, and - especially - the new SeedQR format which allows users to store their mnemonic codes as QR codes. Aaron and Sjors start the episode by recapping what HD Wallets (also known as private key seeds) are, and why they are preferred over regular private key backups. Next, they briefly explain why mnemonic codes (also known as seed phrases) are a popular solution for encoding and storing private key seeds. The Bitcoin, Explained hosts then go on to discuss SeedQR. SeedQR is a new format that allows Bitcoin users to encode and store their mnemonic code as a QR code. This means that mnemonic codes can be stored in a computer-readable format; any compatible device (like a hardware wallet with a camera) should be able to scan the QR code, and import all associated private keys. This could be useful for backups. but it could also be used so that wallets (including hardware wallets, but also mobile or desktop wallets) no longer have to store private keys at all. The QR code could be scanned when the wallet is used to send a transaction, after which the private keys could be forgotten by the device altogether. (SeedSigner is an open source, do-it-yourself hardware wallet that does exactly this.) Finally, Sjors goes over some of the intricacies of formatting a seed phrase to fit in a compact QR code, and some of the efficiency gains SeedQR uses to accomplish this. Chapters 00:00:00 Bitcoin Amsterdam announcement 00:01:41 SeedQR, steel backups and SeedSigner 00:04:28 Why early Bitcoin wallets needed repeated backups 00:07:01 BIP 32: HD wallets and a single seed 00:08:13 BIP 39: mnemonic words and language compatibility 00:12:04 12 versus 24 words: security and backup trade-offs 00:15:18 SeedQR for backups and wallets without stored keys 00:18:30 Drawing SeedQR by hand: size and error correction 00:23:08 Compact SeedQR encoding and scanner compatibility 00:25:14 Human-readable backups and better error correction
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
Aaron van WirdumLive from Utrecht, this is Bitcoin.
Sjors ProvoostExplained.
Aaron van WirdumHey, Sjors.
Sjors ProvoostHello.
Aaron van WirdumSo, here we are. After weeks of you complaining to me, DMing me, asking me every week, week after week, Aaron, Aaron, Aaron. I want Nigel Farage to come to Amsterdam. Nigel Farage needs to be a speaker at Bitcoin Amsterdam. Finally, Sjors, I can tell you, he's coming.
Sjors ProvoostOkay. I think I heard the rumor earlier today and I was like...
Aaron van WirdumOkay he'll be there so it's a happy day for you Sjors, I know he's your favorite politician.
Sjors ProvoostHe is?
Aaron van WirdumOkay and you dear listeners if you want to see Nigel the great Nigel Farage I'm in case anyone doesn't know this I'm being a bit sarcastic but in case you want to come to Bitcoin Amsterdam
Sjors ProvoostDoes he even have a passport to travel outside the UK?
Aaron van WirdumYeah I I don't know why he would want to right But let me finish my thought. If you want to come and if you want to meet Nigel Farage or at least hear him speak, use the promo code Sjorsnado. Let's see if anyone out there can remember Sjorsnado and use it as a promo code. You'll get 10% off.
Sjors ProvoostOkay.
Aaron van WirdumThat's my sort of, I'm now just shilling the conference before we start the episode. I hope you don't mind too much.
Sjors ProvoostThat's what we did last time.
Aaron van WirdumYeah, I think this is the third time. All right, let's move on. Sjors, today you've got a new hobby.
Sjors ProvoostI have a new hobby.
Aaron van WirdumWhat am I looking at here?
Sjors ProvoostYou're looking at an anvil.
Aaron van WirdumYou've got an actual miniature anvil on your desk right here.
Sjors ProvoostThat's right.
Aaron van WirdumAnd you're using that for what exactly?
Sjors ProvoostWell, right now I'm just using it as a nice decorative element. But I want to hobby around a bit with these QR codes that you can basically put in steel plates.
Aaron van WirdumRight. You're going to hammer your private keys into steel.
Sjors ProvoostOr some testnet private key probably, but we'll see.
Aaron van WirdumFair enough. Yes. Well, so the specific thing we're going to discuss is SeedQR. This is something you proposed.
Sjors ProvoostYes.
Aaron van WirdumI'd never heard of it. I don't know where you found it. And I think you didn't remember where you found it either.
Sjors ProvoostI remember.
Aaron van WirdumOh, where did you find it?
Sjors ProvoostYeah, I was on Twitter as I sometimes do.
Aaron van WirdumAs usual.
Sjors ProvoostAnd I was doom scrolling. And then I saw this really cool video of somebody writing down with pen and paper a QR code, just with regular pen and paper, and scanning it, and it actually worked. So I was quite surprised to see that you can actually draw it by hand, and quite sloppily even.
Aaron van WirdumWhy is that surprising? That doesn't surprise me at all.
Sjors ProvoostI was expecting it to be very sensitive. So if you don't print it with a computer and the squares are not perfectly square, then I thought it wouldn't work. But it turns out now you can do pretty sloppy work, and it still works.
Aaron van WirdumRight so basically you you can draw out a grid and start you know coloring some of the…
Sjors ProvoostYeah, but I think he didn't even draw out a grid here. So yeah, it was just roughly.
Aaron van WirdumOh, and it still works?
Sjors ProvoostYep.
Aaron van WirdumThat's actually pretty interesting then. So this was someone using SeedQR? Does this tie in?
Sjors ProvoostYeah, so I was wondering like, what is that? You know, what's behind that? What's the standard or maybe a proposed standard? And yeah, so there's apparently something out there called SeedQR. And the context in which it's used is a device. I guess we'll get to that later. It's called the device called the SeedSigner. And that is not really a company. It's just an open standard for how you can make your own device. So you buy, I think it's a Raspberry Mini or Arduino, something like that. Very tiny computer, has a little camera on it, and
Sjors Provoostyou install some software on it that's open source. And then you can use that to scan a QR code. And this QR code will then convert into your 12 words or 24 words.
Aaron van WirdumOkay.
Sjors ProvoostAnd vice versa, you can use a keyboard, or it's not really a keyboard, just a couple of buttons to enter your 24 or 12 words, and it'll show you a QR code, and you can then draw that QR code on a piece of paper. That's kind of what it does.
Aaron van WirdumRight.
Sjors ProvoostWe're getting a little ahead of ourselves, but that's what I was looking at.
Aaron van WirdumYeah, let's just take this one step at a time, and then we'll get to whatever you're talking about in a minute.
Sjors ProvoostOkay.
Aaron van WirdumSounds good.
Sjors ProvoostSounds good.
Aaron van WirdumAll right. There we go. So first of all, Sjors, how do people make sure they don't lose their Bitcoin?
Sjors ProvoostThey make backups.
Aaron van WirdumGreat.
Sjors ProvoostOr they become a no-coiner.
Aaron van WirdumWell, so people used to make backups. You know, back in the days, we all made backups, which basically meant you literally backed up every private key you had, right?
Sjors ProvoostYeah, so I'm using the word backup very broadly. But back in the day, you actually had to make a backup in the more narrow sense that you click the button that says make backup and you store the backup somewhere else. So if you were using the old Bitcoin client before it was called Bitcoin Core, it came with a wallet. Yes, in order to not lose your coins, you had to make a backup of the wallet. But not just once. Initially, every time you made a new receive address, it would be a completely random receive address. So you'd have to make a backup every time
Sjors Provoostyou received coins. Or at some point, I think it was improved, so it would make 100 receive addresses in the background. And you'd make a backup of those 100 addresses. If you forgot to do that, you would suddenly lose all your coins if you restored an old backup.
Aaron van WirdumRight okay so the problem with this for one is you need a lot of well maybe not a lot but you need to back up a bunch of data one for each transaction one for each receiving transaction because ideally of course you make a new address for each transaction as we've explained like three episodes ago I think.
Sjors ProvoostWe've mentioned it a couple of times.
Aaron van WirdumIt's also somewhat everyone knows.
Sjors ProvoostAnd so you didn't have to do it every transaction. I think you would have to do it every 100 transactions or something, and they would just make 100 backups, something like that. But anyway, if you forgot to do that, your coins, not only do you use new receive addresses, even if you use the same receive address every time, when you're sending coins, you create a change address, your wallet. And your wallet will create new change addresses because it's very disciplined. And so when you hit change address number 101 or whatever it was, and you don't have a backup of number 101, now all your coins went to this new change address and
Sjors Provoostthey're all gone.
Aaron van WirdumIf your computer crashes or something yeah yeah okay so this was improved we're just gonna have to kind of rush through this because we've discussed it before and I think we've even had entire episodes about some of this stuff like for example the thing we're gonna mention now are seeds I think we've had a whole episode it was like episode it was an early episode what is an xpub?
Sjors ProvoostYeah that's a famous episode.
Aaron van WirdumIs it a famous episode?
Sjors ProvoostNo, I don't know.
Aaron van WirdumI think all of our... Well, actually, none of our episodes are famous, I'd say. BIP 32, that's seeds. So what is seed? Am I saying that right? No, no, no, I'm saying it wrong.
Sjors ProvoostSeed, yes, but it's not a mnemonic. So basically, a seed just means one key that creates all the other keys. So it's like a plant seed.
Aaron van WirdumRight, yep.
Sjors ProvoostAnd so what BIP 32 did is you create this one master seed, master key, or whatever you want to call it. And that's the thing you backup, which is the first thing you do when you get the new wallet. You backup this master seed and you're good. Then what happens is you have a tree of derivations, basically, so that each address is unique, but it is all derivable from this one seed. So that's how you can restore it.
Aaron van WirdumJust to jog my own memory, really. I mean, if I don't remember, probably some of our listeners don't. Is it essentially just the case that you... generate a first private key and then you hash the private key and the hash and the hash and the hash and that's just new private keys or is it a bit more complicated?
Sjors ProvoostIt is a bit more complicated but it really boils down to that you right hash it and maybe you add the number one and there's some some nuance there but yeah.
Aaron van WirdumThat's essentially the gist of it all right.
Sjors ProvoostIt's deterministic so your wallet will know what to do.
Aaron van WirdumRight.
Sjors ProvoostOnce it gets a seed. It will know how to find the addresses that you've used before.
Aaron van WirdumSure okay now then I guess the problem here again we're rushing through it a bit through this part. The problem here is that remembering even the seed, even the first private key is a little bit hard. Not for you, of course, but for regular people like me and most of our listeners, we don't actually remember that kind of stuff. So we need something that's a bit easier.
Sjors ProvoostWell, so the thing is, initially with the Bitcoin client, you would just back up on a USB stick or something like that, right? It'd still be a digital backup. And so some people would prefer to have a backup that's physical, that's probably written on a piece of paper. And that means, yeah, then it gets really cumbersome to start writing these hexadecimal things down, if you can even find them. Right.
Aaron van WirdumIt's not even about memory. You shouldn't even use your memory. You should write it down either way. But we need an easier way to write it down.
Sjors ProvoostYeah. And I guess that's another thing. So then there was this idea called BIP 39, which is a mnemonic. And the idea is really you just take the letters or the hexadecimal numbers and you just map them onto words. So there's 4,000 words and each...
Aaron van WirdumNo, there's 2,048 words, I think.
Sjors ProvoostOkay. Some... Those just map onto the numbers.
Aaron van WirdumIt's 2 to the 12th. 2 to the power of 12th. That's 2048.
Sjors ProvoostThat sounds like 4,000. 2 to the power of 10 is 1,000.
Aaron van WirdumNo, I'm pretty sure. I looked it up this afternoon. So I think it's 2048 words. But there may be several standards, right? Aren't there several?
Sjors ProvoostWell, I'm talking about BIP 39.
Aaron van WirdumMe too.
Sjors ProvoostSo there's a number of words, which we'll have to look up. And they really, those words just represent numbers, essentially. So that's that simple.
Aaron van WirdumBasically, it's just the first word is number 0000. They all have four numbers, right? And then the second word is 0001, and that's all the way through.
Sjors ProvoostExactly. Now, there is a little caveat there. It works one way, as in you start with the numbers. So the numbers are the seed you generated, essentially, your computer generated, and then they are converted to words. But when you use it, it's actually not using the words. Sorry, it's not going back to the numbers. So when you enter the words, the next step in order to create this hierarchical wallet is to just process the words as they are written and hash that.
Sjors ProvoostIt's a little implementation detail that you generally don't have to worry about unless you want to do translations. So basically the first address of your wallet is derived. So you start with this random numbers. Those are turned into words, and those words pasted behind each other, and maybe with a little password behind it, those are hashed, and that's where the first key comes from. But that means that if you have, say, a German alternative for this BIP 39,
Sjors Provoostthat... If you start with the same numbers, but now you start to write German words, and when you hash the German words, you're going to get a different key than when you hash English words. So you cannot translate one seed into another. That makes no sense.
Aaron van WirdumRight. Okay.
Sjors ProvoostAnd this is relevant because that's one reason why I don't think it's a good idea for people to use BIP-39 in other languages. Because in that case, you may have one piece of software that will understand what to do with the German words, but your other piece of software that you may want to use later, your other wallet, will not understand it. Because most of the support is for the English words.
Aaron van WirdumRight. Okay, well, I didn't know that. Is it important for the rest of the episode?
Sjors ProvoostIt's not important for the rest of the episode. It is one of those things that if we ever had to redo these standards, that we should do better.
Aaron van WirdumRight. I do have another question. So some seeds have 12 words and some have 24. I think these are the two most common amounts of words. Why is there a difference? Is one just more secure?
Sjors ProvoostYeah, it's more bits. So 12 words means 128 bits. Of random data. So basically throwing coins. Yeah, you're basically throwing 128 coins.
Aaron van WirdumFor heads of tails, yeah.
Sjors ProvoostYes. Or if you have 24 words, you're effectively throwing 256 coins, heads of tails. And that is not twice as secure. That is like...
Aaron van WirdumA lot more secure.
Sjors ProvoostYeah.
Aaron van WirdumWhat's the numbers, Sjors?
Sjors ProvoostWell, I don't know.
Aaron van WirdumFrom the top of your head, come on.
Sjors ProvoostIt's basically twice as many bits of security.
Aaron van WirdumYeah.
Sjors ProvoostBut... It takes a lot more time to brute force it. Because every bit you add means it takes twice as long to brute force it. If you want to guess what somebody's mnemonic is, you try one combination of words, you try another, you try another, you try another. And if it's a two-bit system, if it's a two-bit seed, well, then you just have to try four times. But if it is a 4-bit seed, you don't have to try 8 times, you have to try 16 times.
Aaron van WirdumSo is 12 enough then? Why don't all wallets just use... If some wallets use 24, why don't they all use 24?
Sjors ProvoostI mean, ultimately, it's better to have more bits of security. If there's no trade-off, why not? Right and ultimately in the long run you know the worry is that as computers get faster or as problems are found you need more bits to be really secure and maybe one day we'll reach the point where 128 bit is not secure anymore but then 256 will last us a bit longer so it's it's that kind of long-term thinking.
Aaron van WirdumIs it maybe also partly a human problem like some people will cut their seed in half thinking if they hide them in different places then they're good but then if [unclear] if someone…
Sjors ProvoostYeah so then you're getting really in trouble right because six if you have a 12 word seed and you cut it in two that's six words each and that is only 64 bits of entropy that's still that's still a lot but it might be within the realm of something you can crack because again Twice as long does not mean that it takes twice as long to crack it. It means it takes exponentially longer to crack it.
Aaron van WirdumYep.
Sjors ProvoostSo that's indeed one of the risks, but I don't think that's the reason. So basically, you could say that the limit of Bitcoin, the way it's architected, is 256 bits. And that is because the hashes of a block, as well as the elliptic curve, all use 64 bits, 256 bits. So if you have a way to crack a 256-bit number, like find the private key, etc., that's basically the security level anyway. So you might as well use that.
Aaron van WirdumBroken Bitcoin itself, yeah.
Sjors ProvoostYeah. So that's why I guess that's one argument to say, well, then why don't you use seeds that are at that limit? It makes no sense to go beyond it, but it also makes no sense to stay below it. All things equal. Because you do have to write these things down or do something else with it. And if that's too much work, then people won't do it. And then you just lose your coins. So the benefit of 12 words is that people are more likely to write them down.
Aaron van WirdumOkay, now let's get to the meat of this episode. I think that was a long recap of stuff that people already knew, or at least most people already knew most of that. So now we're getting to SeedQR, and this is your hobby project. So I guess Sjors, just explain what it is.
Sjors ProvoostYeah, so as far as I know, it's a proposed standard, and there are some tools that are using it. And the idea is that you take these 12 to 24 words, and rather than writing them down as words, you convert them into a QR code. Because remember, these things represent numbers. So you just take the word, find the corresponding number, and now you have a bunch of numbers. And if you have a bunch of numbers, essentially, if you have 128 bits of data or 256 bits of data, you can squeeze that into a very small QR code.
Aaron van WirdumRight. So right now a lot of people are storing their Bitcoin essentially, their private keys as a list of, or at least their backup as a list of words. And according to, with this standard, they could backup their keys as a QR code, which they...
Sjors ProvoostYeah. And so one benefit of that could be...
Aaron van WirdumIs that new? I mean, I've never heard of it, but it sounds like a fairly obvious thing to do, but it's new.
Sjors ProvoostYeah. I mean, it really depends on your use case, right? So if you have your keys in some very far away cold storage place in the middle of the Antarctica, well, it may be useful for you. If you need those words anyway, you can either type them or you can scan them, right? Those are the two ways you can enter them back into a machine. And since most hardware wallets are a pain in the ass to type on, maybe using a camera might be easier. But I think only the Jade hardware wallet
Sjors Provoostand the Specter DIY wallet have cameras. So there's only limited use for QR codes.
Aaron van WirdumOkay, so the general idea is we're using a QR code as a backup. What are the challenges here?
Sjors ProvoostYeah, and not just as a backup. It could even be, let's say you have a phone wallet. And when you're walking around with your phone, maybe it's a phone wallet that you don't use for shopping, but you do use it for your, I don't know, everyday stuff. It's not like cold storage. It's not a huge amount of money. But when somebody robs you in the street, you don't want to be able to give them Bitcoin. So you don't want to have the private keys on the phone itself. You want to have them somewhere safe at home. And so then a QR code could be useful because when you do want to use it, you just scan the QR code. And now, boom, you can spend
Sjors Provoostyour Bitcoin. But when you're on the street, nobody can rob you. If they go to your home, they can. You know, that's a trade-off.
Aaron van WirdumRight. So the idea there would be that your phone doesn't actually store any of the keys. It just scans them for one-time use. It scans the QR code for one-time use and then forgets it. And it can be a phone. It can also be another device, of course. It could be a hardware wallet that operates like this. So then the keys aren't even on the device.
Sjors ProvoostYeah, well, they are when you're using it. But after that, they're not. Well, unless it was compromised.
Aaron van WirdumRight, so rather than thinking of it as a backup, in that case, it is essentially your actual cold storage wallet.
Sjors ProvoostYeah, or at least your actual offline, semi-offline wallet or something like that.
Aaron van WirdumRight, right, right. Okay, so what are the challenges to accomplishing this, if there are any?
Sjors ProvoostWell, for one thing is, again, it depends on the use case. For the easy use case where you are printing a QR code with a physical printer, then I guess it doesn't matter, right? You can make a very big QR code or a very small one. It doesn't matter. But when you, as we described in the beginning, you want to write down your QR code on a piece of paper, which you can draw. It's nice if the QR code is not too many little points because it's very tedious to do it. And if you want to put them on metal, then you really don't want to have 5,000 little points that you need to put on
Sjors Provoostthe QR code.
Aaron van WirdumRight. And I guess the reason this matters is that you ideally don't want to have your private keys touch. A computer at all, possibly, or a printer at all.
Sjors ProvoostExactly.
Aaron van WirdumThese things can be hacked, and I think some printers even have memory of stuff they printed. Ideally, it just flashed on your hardware wallet or something, and then you write it down with a pen and paper.
Sjors ProvoostExactly, and that's what the SeedSigner does. So the SeedSigner is a sort of open-source device where you can buy off-the-shelf components and make it yourself. What this device does is you enter your words, and it shows you the QR code, or you scan the QR code, and it shows you the words. And then I think that device can also sign things, but maybe you don't want to use that part. Maybe you want to use your regular hardware wallet for the signing. So you then take your mnemonic and put it in your regular hardware wallet, something like that. That could be the operation flow. And that means you're not using your main computer,
Sjors Provoostwhich will probably have millions of viruses on it. You're not using your printer, which will probably have millions of viruses on it. And then it's really important because you're doing this step by hand, you're drawing a QR code. The drawing part should be as little work as possible.
Aaron van WirdumRight.
Sjors ProvoostSo then they've done some research about how small these QR codes can get.
Aaron van WirdumHow small can these QR codes get?
Sjors ProvoostFor 12 words, you can use 21 by 21 points. And a large part of that, if you look at a QR code, there's these giant rectangles, right? So it's 21 by 21, including those giant rectangles.
Aaron van WirdumHow small can QR codes get in general?
Sjors Provoost21 by 21.
Aaron van WirdumIs that the smallest type of QR codes?
Sjors ProvoostI believe that is the smallest type of a regular QR code. There is also a micro QR standard that is even smaller, but that is useless for this purpose. So if you look at my book, maybe I'll just shamelessly shill that I have a book.
Aaron van WirdumWe're shilling all the way in this episode.
Sjors ProvoostBitcoin, a Work in Progress. Or just Google Bitcoin Sjors. You'll need to know how to spell that anyway.
Aaron van WirdumNo one knows Sjors.
Sjors ProvoostThat's all right. What was I saying? Yeah, so the book actually contains QR codes that will take you to various resources, right? So you don't have to type the whole URL. You scan the QR code. It takes you to a short URL. Those short URLs fit exactly into the smallest possible QR thing of the 21 by 21. So that's HTTP colon slash slash yadda yadda yadda.
Aaron van WirdumOkay.
Sjors ProvoostBut you can also put a seed in it.
Aaron van WirdumSo the smallest, at least the smallest sort of regular QR code is 21. Do you know what QR stands for?
Sjors ProvoostQuick response.
Aaron van WirdumVery well. Very good. So the smallest QR code is 21 by 21. And then there are bigger ones.
Sjors ProvoostYeah. And so the reason you want to use bigger ones is, for example, because you have more words that you want to put into it.
Aaron van WirdumRight.
Sjors ProvoostSo I think you need a 25 by 25 to have 24 words. And the other thing you can do is increase the error correction. And so what a QR code does is it shows you, a QR code starts with the actual thing that it's describing. So say a URL, a piece of text, and then it has a bunch of extra bits and a bunch of extra pixels. And their purpose is to basically help the device that's scanning it to correct for errors because the camera might not be accurate.
Aaron van WirdumYeah, or, you know, your ink may be blurry.
Sjors ProvoostYeah, so basically, you know, some people abuse this feature. They'll put the company logo in the middle of a QR code. And what that does is basically it obscures part of the QR code, but because it has so much error correction, you can actually obscure 5% or 10% of the QR code and still read it. That's the idea. We talked about error correction in an earlier episode, I believe, about this mempool sync project.
Aaron van WirdumOkay.
Sjors ProvoostMinisketch.
Aaron van WirdumI don't remember. Well, I kind of remember vaguely, but let's get back to the point. So we're using 21 by 21 QR codes.
Sjors ProvoostOr bigger. Yeah. The SeedQR standard uses several different sizes of QR codes.
Aaron van WirdumRight. And is there any sort of... I recall they're doing some tricks to actually make it fit. Is that not the case?
Sjors ProvoostYeah, exactly. There are two ways to put the data into the QR code. One is a way that is as compact as possible. That's where you get to 21 by 21. The other is a way that other apps can actually read it. So the problem is when you use the most compact way to store it, there are not a lot of off-the-shelf applications that can actually read this QR code. So if you point your phone at it... If you use this very compact form, your phone will be confused. It won't understand what to do with the QR code. That's kind of a feature, actually, because you don't want it to.
Aaron van WirdumThey've used optimizations that other apps don't understand. Is that the right way to put it?
Sjors ProvoostBasically, when you scan a QR code, your phone is generally expecting a URL or at least regular text. But these things will use full basically 256-bit ASCII. So if you ever go... I don't know if you've ever seen some binary file and you open it up and it has all these symbols and your computer starts beeping at you.
Aaron van WirdumYeah.
Sjors ProvoostYeah. So that's basically what's in the QR code too. It's using all the bits it can. And so your phone thinking it's text will render complete gibberish. In fact, it will just not work.
Aaron van WirdumRight. Okay.
Sjors ProvoostBut I think that's all solvable.
Aaron van WirdumAnd what you were saying is that in a way it's kind of nice that it does that because if some random person finds this QR code that has all your money on it, then it's kind of nice if they don't understand what it is.
Sjors ProvoostWell, that's one nice thing about QR codes. So now you can start thinking about where could these fit into your security model. Well, if you're traveling with 12 words written on a piece of paper, if the customs search your bag, they'll see the 12 words. They know what to do with it. Maybe if you have, say, a vaccination passport that has a bunch of QR codes on it anyway, you kind of shove in your little Bitcoin backup in that passport and maybe they won't see it. But that's, you know, that's always a little scary.
Aaron van WirdumOkay, so, so far, so far this all sounds... Great. Also kind of straightforward. Is this just a straightforward episode or is there some magic still waiting in the corner? Where are we taking this?
Sjors ProvoostMy magical suggestion would be that, yeah, this is pretty straightforward, but I would say that the downside of QR is that it is designed for computers. So it's very easy for computers and cameras to scan it. You can read it by hand, as in there's a couple of YouTube videos and documents that you can read. That will explain to you, if you see a QR code, how to read it, but it's very difficult. So what I would like to see is another standard, a new standard, that kind of looks like a QR, but that is much easier for a human to read. So that means you
Sjors Provoostwouldn't even need the SeedSigner device. You would just be able to take a pen and paper and just look at where the squares are and do some math, and then you would actually know what the seed is.
Aaron van WirdumI'm just thinking of the...
Sjors ProvoostYeah, I know which XKCD you're thinking about.
Aaron van WirdumWhich one is it?
Sjors ProvoostBut this standard might actually already exist.
Aaron van WirdumThere are 14 competing standards. 14, ridiculous. Anyways, I think everyone knows it. I'm not going to finish the joke.
Sjors ProvoostYeah, so I don't necessarily think there has to be a new standard and maybe that there's already are standards out there that are designed for humans to parse rather than for cameras to parse. Yeah.
Aaron van WirdumOkay, well, let's see if someone develops that then, Sjors. Why don't you? Why don't you develop a new standard? We need the 15th standard.
Sjors ProvoostI'm not a encoding master.
Aaron van WirdumOkay, well, I'm not going to do it either. So hopefully one of our listeners will feel inspired by your encouragement.
Sjors ProvoostI hope sipa picks it up because it'd be nice to have some error correction. Let's say you have a QR code, right? And QR code is every, if you read it from left to right, basically it's either black or it's white. So it's like a bit. So you could imagine having a device where you're clicking a button, either the left button or the right button. If you see a white pixel, you click the left button. If you see a black pixel, you click the right button. And then based on that click, click, click, click, click, click pattern, it reconstructs your seed. And it's nice if there's error correction while you're doing that. So rather than
Sjors Provoosttyping all the 24 words as you would now, and then it says, nope, sorry, it's wrong. Every six or seven characters, they would tell you, no, no, no, you did something wrong. And then you know that you have to go back and check the last seven characters. Because, you know, it's not easy to manually type something like a QR code without making mistakes. So I think there's promise there.
Aaron van WirdumOkay.
Sjors ProvoostBut that's all I got.
Aaron van WirdumOkay. So when are you going to make yours?
Sjors ProvoostOh, I don't know. Whenever.
Aaron van WirdumYour steel plate?
Sjors ProvoostWhenever it arrives. I'll go play with it.
Aaron van WirdumYou're waiting for the actual plates to arrive? That's what you're waiting for?
Sjors ProvoostYeah, exactly.
Aaron van WirdumAll right. Well, you got the rest of the tools ready. Sjors, I think that's it then. I think that's our episode.
Sjors ProvoostSounds good. Thank you for listening to Bitcoin.
Aaron and Sjors discuss Bitcoin Core 32.1 and its updated security disclosure policy in this live conference recording, followed by audience questions. Links Bitcoin Core 32.1 release announcement and release notes...
Aaron and Sjors discuss the COLDCARD hack: the bug itself, how it could have happened, and some reflections on having had Coinkite as a sponsor. Note: If you’re using a COLDCARD and still haven’t moved your funds to a...
The COLDCARD hardware wallet has a critical vulnerability. If you are using the COLDCARD to store bitcoin, move them to a secure location as soon as you can. More information:...
Aaron and Sjors discuss what’s new in Bitcoin Core 31. Chapters 00:00:00 Episode 100 and Core 31 00:02:41 Cluster Mempool 00:10:45 Package Relay and Fee Selection 00:18:59 Private Broadcast over Tor 00:24:03 ASMAP and...