Aaron van Wirdum Live from Utrecht, this is Bitcoin
Transcript
Sjors Provoost Explained.
Aaron van Wirdum Hey Sjors.
Sjors Provoost Hello.
Aaron van Wirdum Actually, is that still our name, Sjors? Are we still called Bitcoin Explained?
Sjors Provoost Yeah, that's up for debate. But we have some exciting news, right?
Aaron van Wirdum We'll get to that in a minute then.
Sjors Provoost Okay.
Aaron van Wirdum Yeah, so we've been away for a while. You haven't heard from us for a couple of weeks, dear listener. So we're going to offer you an update about what's going on. Because something's going on. First of all, though, Sjors, one of the reasons we've been away for a while is because you were literally away for a while.
Sjors Provoost That's right.
Aaron van Wirdum You went to a couple of conferences. I think you went to, where did you go?
Sjors Provoost I went to TABConf in Atlanta and I visited the Bitcoin Park. And then I went to BTC Azores in the middle of the Atlantic.
Aaron van Wirdum Right. So you were away for what? A month or something?
Sjors Provoost Yep.
Aaron van Wirdum You were away for a while. Now you're back. Okay. So, the big news, Sjors, is... What's the big news?
Sjors Provoost We've been acquired.
Aaron van Wirdum We've been acquired. Who acquired us?
Sjors Provoost We. We acquired ourselves.
Aaron van Wirdum That's a very positive spin. Okay, we're not a Bitcoin Magazine podcast anymore. That's basically the story here, right?
Sjors Provoost That's right.
Aaron van Wirdum Yeah, so, dear listeners, so, yeah, Bitcoin Magazine has been going through a reshuffle, essentially. And one of the things that was decided is that Bitcoin Magazine is not supporting podcasts anymore. Bitcoin Explained is a podcast. So we're not supported by Bitcoin Magazine anymore.
Sjors Provoost Oh, I thought it was just us.
Aaron van Wirdum There's another one. Well, yeah, that's sort of the thing. Like we used to have a bunch of podcasts at Bitcoin Magazine. And I don't remember which ones, but then one by one, they sort of stopped. And there were only two left at this point. And it was just kind of this part of Bitcoin Magazine that was sort of ignored and sort of on the wayside. But it still required some resources to kind of keep it running. And at some point, the decision was made that Bitcoin Magazine right now just doesn't do any podcasts.
Sjors Provoost Well, I do really appreciate Bitcoin Magazine helping us through those first three years almost.
Aaron van Wirdum Yeah, absolutely, and Bitcoin Magazine was gracious enough to just let us continue the podcast so you know we don't have any fights about name rights or we can just keep going. So that's nice enough. So in a way not much is going to change. We're still going to make the podcast we even found a new editor, Stijn, the world famous Stijn in the Netherlands, the best editor in the country. He's gonna edit our podcasts going forward.
Sjors Provoost Even if we said he was not the best editor, he's the editor, so he can just make us say he's the best editor.
Aaron van Wirdum You can edit out whatever bad things we say about Stijn. Uh what else so yeah so basically not much will change in that sense. There will still be a podcast. I I guess that's the question right? Like we don't have any evil corporate overlords anymore, Sjors. That's why I want to move back to Van Wirdum Sjorsnado.
Sjors Provoost Well, we'll have to chat about that. The upside of Van Wirdum Sjorsnado is that it's the best name for a podcast ever. The downside is that if you tell people to please subscribe to Van Wirdum Sjorsnado, they will stare at you.
Aaron van Wirdum No one knows how to spell any word in that name.
Sjors Provoost So maybe we'll just use both names. We'll figure it out.
Aaron van Wirdum I mean, maybe we'll just cater a niche audience from now on. Our fan base knows how to spell our name.
Sjors Provoost Anyway, we've been chatting now for three minutes and 40 seconds. Shall we talk about Bitcoin?
Aaron van Wirdum No, no, I'm not done yet. One other thing I wanted to mention is, so we were already kind of discussing that before we even... went independent, split off from Bitcoin Magazine, is that from now on, our podcast will be sort of content-driven rather than time-driven, if that's the right way to put it. We used to basically make an episode every other week. Now, we already slipped that sometimes, either because one of us were traveling. Sometimes we didn't have a topic in mind. That was a reason we sometimes skipped an episode. And moving forward, that will sort of just be the order of things. I think we both agree. If you have an interesting topic to discuss or I have an interesting idea, that will be a reason to make a podcast. And if we don't have that, there won't be a podcast. We won't necessarily make a podcast every other week, at least for the time being.
Sjors Provoost Yeah, that's right. And I think it's interesting to give some context there. In the beginning, coming up with ideas for podcasts was quite easy because there were lots of topics left to explain. Nowadays, we usually spend like half an hour discussing possible topics. And I'm like, meh, I don't feel like this one. Too much work, etc. So it'll be a bit more difficult, but we'll get there. And sometimes it's happened that I thought the topic would be super uninteresting and then we ended up spending 50 minutes and it was a good episode. So,
Aaron van Wirdum Yeah. Anyway, so I don't think moving forward going forward you—or this dear listener— will necessarily get a podcast every other week but there will still be podcasts. We'll see how often or how many I guess, right we'll figure it out as we go along. What we can say is, so we're kind of making this podcast we're still in the introduction stage right? We're kind of making this podcast as uh kind of a placeholder almost, because even at this point the previous podcast was a while ago in part because we were traveling in part because all the stuff I was just telling you about or this dear listener and then in the next couple of weeks there will also be there will be Bitcoin Amsterdam there will be other conferences I'll be going to. So the next podcast might also take a little while before we, but we, so we wanted to give you something because otherwise there would have been no podcast for like three months or something. So we're making this one. By the way, Sjors, are you going to Bitcoin Amsterdam?
Sjors Provoost Probably, but I still haven't gotten any formal invite.
Aaron van Wirdum Okay. Are you not a speaker?
Sjors Provoost No.
Aaron van Wirdum You're not invited? That's surprising to me. All right.
Sjors Provoost I think I was invited to be a speaker, but then it was never followed up, and we might be doing some recording, but I don't know how that's going.
Aaron van Wirdum Yeah, I don't think we're going to do that Sjors.
Sjors Provoost Okay, well.
Aaron van Wirdum I mean, that was part of the original sort of before Bitcoin Magazine split us up kind of deal. I don't know. Don't count on it. I'm not counting on it. I don't think I'm going to do that. All right, so that's it. Honestly, that was kind of the main reason, as far as I'm concerned, that we're making this podcast, just to tell you all this stuff that I told you in the last, how long are we recording now?
Sjors Provoost Six minutes and 50 seconds.
Aaron van Wirdum All right, almost seven minutes. However, dear listener, we didn't want to send you home empty-handed. So Sjors and I did find a topic for you that you'll find fascinating, I'm sure. Sjors, we're going to discuss an invalid block that was mined last week.
Sjors Provoost That's right.
Aaron van Wirdum At the time of recording, I think, do you know when it happened exactly?
Sjors Provoost No, about a week ago.
Aaron van Wirdum Yeah, well, give a date. What's the date today? We're like early October?
Sjors Provoost It was block 809478.
Aaron van Wirdum So it was like late September. Okay, 2023, in case you're listening to this in the future. So an invalid block was mined. It was mined by MarathonPool. And this is where I sort of turn it over to. So what happened? Why was it invalid?
Sjors Provoost Well, yeah, basically when you mine a...
Aaron van Wirdum Wait, there's something else, I think. Yes, there's something else. We're getting to the invalid block in a minute.
Sjors Provoost Well, we can get to the invalid block now and just get to the other things later.
Aaron van Wirdum Is that a logical order, you think?
Sjors Provoost Yeah, because we've already started this topic.
Aaron van Wirdum Okay, we're already started. Let's go. Why was this block invalid?
Sjors Provoost So basically a block has to follow a bunch of rules as defined by the Bitcoin consensus rules. You know, don't create too many coins. Don't do any double spending. I guess that's really the same as don't create any new coins. Signatures have to be valid. There's lots of little, big rules, little rules, subtle rules, et cetera. One of the rules is that—
Aaron van Wirdum The block can't be too big.
Sjors Provoost Yep. One of the rules is that if you have a transaction A, which is spending from transaction B, then transaction B must happen first inside the block.
Aaron van Wirdum Oh, this confusing A comes before B.
Sjors Provoost Okay, we'll do it the other way around.
Aaron van Wirdum Yes.
Sjors Provoost If you have a transaction B, which is spending from transaction A, then transaction B must be after transaction A. So you cannot, yeah, you cannot look at a block as a whole and say, well, it nets out and it's all fine. No, they have to be in the right order inside the block. That's actually quite annoying because there's some optimizations that you could do from a block verification perspective if the order of the transaction didn't matter because then you could just check them all and then not worry about ordering. But you can't. You have to check them one by one in sequence.
Aaron van Wirdum Wait, so why is that? Why is this a rule? Why not just remove this rule? What's the logic?
Sjors Provoost The rule is there because Satoshi put it in there, either deliberately or probably not really thinking about it. And it's there. If we remove it, it's a hard fork.
Aaron van Wirdum I see. Okay, so this has been a rule since the very beginning. So the order that the transactions are included in a block need to be...
Sjors Provoost the right order yeah, and of course it would have been nice if you could say well as long as you know if the if the transaction… As long as it's somewhere in the block, it's fine. But no, it has to be in the right order inside the block. And if you ask Bitcoin Core to create a block for you as a miner, which you can do, then Bitcoin Core will make sure that happens, among other checks.
Aaron van Wirdum Okay, so why were the transactions in this block in the wrong order?
Sjors Provoost Well, I guess now you're spoiling what actually went wrong. But yes, the thing that went wrong is that the transactions were not in the correct order.
Aaron van Wirdum I thought you already said. I mean, that's pretty obvious at this point that that was the problem.
Sjors Provoost I guess it was a bit of a... of a hint there. Yeah, so basically they were in the wrong order, and then the first question is, why? And also the second question for me would be, oh shit, is there a bug in Bitcoin Core? Now, turns out that...
Aaron van Wirdum Let's start with the why.
Sjors Provoost We don't know why. Like, I don't understand what the thinking was for this particular mistake. We do know that I think the transactions were ordered by feerate for some reason, but there's really no sane reason to do that, as far as I know.
Aaron van Wirdum Not all transactions in the block, right? So only these transactions were ordered?
Sjors Provoost No, I think they took a normal block as proposed by Bitcoin Core, which has the transactions in some order, and then they said, ah, it looks nicer if we sort it by fee rate.
Aaron van Wirdum Okay, so all the transactions in the block were sorted by fee rate.
Sjors Provoost I believe so, yeah. Okay, and that's not the correct order. Well, that's what I read, I haven't checked it.
Aaron van Wirdum Did you read it from a credible source at least?
Sjors Provoost Yes. There's a blog post we'll link in the show notes from 0xB10C.
Aaron van Wirdum Okay. Well, so what I read... Probably in the same blog post, actually. No, well, no, also Marathon said it on Twitter, is that they were experimenting in some way or another. So they were trying to find optimizations. They were using a small amount of their hash power to, I guess, in some way figure out if they could mine even faster or more efficient.
Sjors Provoost Yeah, but I do not see how you can fit more transactions in a block by changing the order. Does it make the block any smaller? It's not like compressing.
Aaron van Wirdum Right. Well, that's the only thing they said. So it sounds like you...
Sjors Provoost So in general, they were doing experiments. That's okay. That's one thing. But I don't understand what the point was of this particular experiment.
Aaron van Wirdum Okay.
Sjors Provoost Because sorting transactions differently might look prettier. I guess if you want to make a nice chart of the block and you want to color the block by fee, with high fees having a darker color and light fees having a lighter color, then maybe if you order them by fee, then it looks pretty. But mechanically or in terms of efficiency, I don't see the point. In fact, it takes longer because you have to sort the block, which takes another split second. And every split second you need more time to do stuff.
Aaron van Wirdum You're not much of a block connoisseur, it sounds like.
Sjors Provoost I don't know. I think Bitcoin Core does a good job at it.
Aaron van Wirdum You don't care too much about the visual aspects of a block.
Sjors Provoost So in any case, they said it was not Bitcoin Core's fault, so that's good news, because otherwise there might be some bug out there. That's not good.
Aaron van Wirdum Right, that was question two. So yeah, it wasn't a Bitcoin Core thing.
Sjors Provoost No.
Aaron van Wirdum Okay. I had another question. Oh yeah, so they were experimenting with it on testnet, apparently.
Sjors Provoost Yeah, so this is the other observation that our friend 0xB10C, how can we give him a quicker name? B10C? I don't know. He observed that it looked like they were trying this on testnet the day before. So if you looked on testnet, you saw a similar pattern, and in fact, you were seeing the same error messages. Basically, the testnet nodes were rejecting this block as invalid. Which then raises the question of, if you're testing on testnet, why are you not looking at the result of that experiment before deploying it on mainnet and potentially burning an enormous amount of money?
Aaron van Wirdum Right. So if you were running an SPV node, and there was a transaction to you in that block, you would have probably just accepted it, right?
Sjors Provoost Yes. And then, of course, within a few minutes, it would have been... reorged.
Aaron van Wirdum It would have been reorged.
Sjors Provoost And probably also included because I don't think there were any double spends here.
Aaron van Wirdum Right, yeah. Still, I mean, it's kind of an interesting or telling example of why SPV nodes are a potential risk.
Sjors Provoost Yeah, SPV nodes do not check this.
Aaron van Wirdum In this case, it's kind of innocent, but yeah, like you mentioned earlier in the episode, maybe someone's trying to steal coins or create inflation, and SPV nodes just doesn't notice that. Well, in this case, all full nodes, all Bitcoin Core nodes, they just rejected the block as invalid and the only real loser here was Marathon Pool because they wasted a bunch of energy and resources creating an invalid block.
Sjors Provoost Yes.
Aaron van Wirdum Right? Okay, well, that's all pretty fine and clear so far. Is there anything to say about this, Sjors?
Sjors Provoost Well, so I'm all for experimenting. But I still don't understand why they tested this on Mainnet instead of checked on Testnet.
Aaron van Wirdum Well, they did, and they ignored what happened on Testnet, apparently.
Sjors Provoost I would also say that if you are willing to spend $170,000 on an experiment, consider giving me, say, $10,000 and asking me to look at your experiment for one hour, and I probably would have found this.
Aaron van Wirdum You can also give me $170,000 as an experiment to see what I'll do with it.
Sjors Provoost Up to you. It's free world.
Aaron van Wirdum All right, I think that sort of covers the invalid block.
Sjors Provoost Oh, I had one more point. So the general... We had an episode before about an invalid block, episode 76, which covered the topic of stamps.
Aaron van Wirdum Oh, right.
Sjors Provoost But there were two invalid blocks in that episode that we discussed. And the reason for the invalid block was completely different. They broke a different rule, and the episode explains that. But the thing that they have in common is that they were both using some custom software. I believe in the case of the invalid stamps blocks, they were using Bitcoin Core, but they tweaked Bitcoin Core, they made changes to it that caused this mistake. Whereas in this case, they might have been using some completely different piece of software. But the rule seems to be, the pattern seems to be that if you write your own software to create blocks, or even to change what Bitcoin Core is doing, you're likely to make mistakes. There's some really finicky rules out there that you might forget about.
Aaron van Wirdum The Bitcoin Core developer advises to use Bitcoin Core.
Sjors Provoost Yes. We have a saying in Dutch. Wij van WC-Eend adviseren WC-Eend.
Aaron van Wirdum Right. I mean, are you going to even explain that? No, never mind. If you're not Dutch, bad luck.
Sjors Provoost You would miss this wisdom.
Aaron van Wirdum All right, I think that covers the invalid block, basically, right?
Sjors Provoost Yeah.
Aaron van Wirdum That was a short topic. There was something else. Speaking of older episodes, so this is the other thing I wanted to bring up. Speaking of older episodes, there have been some updates from the Bitcoin Core development front. Namely, peer-to-peer encryption was merged.
Sjors Provoost Yeah, that's right. It was a productive morning. Two things were merged, and the first one is peer-to-peer encryption, which is a proposal we talked about in episode 77, so not even that long ago.
Aaron van Wirdum Yeah.
Sjors Provoost The idea has been around for six, seven years, I think, initially introduced by Jonas Schnelli.
Aaron van Wirdum Yeah, something like that. Can you give a two-sentence summary for whoever wants to jog their memory?
Sjors Provoost Yeah, right now nodes talk to each other in plain text, which means your internet provider or anyone else can listen to exactly what you're doing. In part that doesn't matter because you know blocks are public information, but in part it could matter because you might be the one you know you might make a transaction and then by looking at this how that transaction moves over the network some spy can tell that the transaction is coming from you and that is not public information. And it makes censorship easier if you can see what Bitcoin nodes are. So this proposal encrypts all the traffic between peers. That's basically it. So anybody observing it can just see noise.
Aaron van Wirdum Right. So that's merged in Bitcoin Core, which means it will be available in the next Bitcoin Core release. Any idea when that will be?
Sjors Provoost Probably November. So that'll be release 26. I'm thinking in a few weeks, maybe in a month, that'll be the first release candidates for people who are really feeling experimental. I mean, if you're really feeling experimental, you can compile the master branch. If you're feeling slightly less experimental, you can wait for the first release candidate. It's an opt-in feature, so you have to configure V2 Transport, but it will be in the README. And then one fun thing you can do if you're testing it out is to check your session ID. So if you connect to somebody you know, normally your node just connects to random other nodes, but if you do connect to somebody you do know, you can actually look up the session ID, probably in the GUI, so that's nice. And then you can call your friend and say, hey, you know, do you see a connection from my IP address? And do you see what the session ID is? And then they should be the same. Very much like in Signal and WhatsApp, where you can compare this identifier.
Aaron van Wirdum Right.
Sjors Provoost And that tells you that there's nobody in the middle.
Aaron van Wirdum Right. Anyways, this is all explained in detail in episode 77. Yep. And there was something else. What else was merged? There was another big merge you mentioned.
Sjors Provoost That's right. AssumeUTXO.
Aaron van Wirdum Right. Okay.
Sjors Provoost For Testnet and for Signet.
Aaron van Wirdum Okay, so that's not on mainnet yet, but, but the core—sorry, the code is in Bitcoin Core now.
Sjors Provoost Yes, and if you do want to test it in mainnet, you can. There's a pull request, but you have to compile it yourself.
Aaron van Wirdum So why is it not available for mainnet yet? What's the reasoning there?
Sjors Provoost Because it's not ready enough, I guess. I think it still needs some testing. The other thing is that these parameters that are in the source code now for testnet and for signet... they really should be verified by users. So very much like assumevalid. We talked about that in some other episode. I think in the AssumeUTXO episode, which is episode number 14.
Aaron van Wirdum Right, yeah. So the thing we're talking about now, episode 14, if you know—yeah, if you want to know more about that.
Sjors Provoost It's one of the first ones we did. Exactly, in 2020. Basically, there's a hash that goes into the source code, which represents the UTXO set for AssumeUTXO. And so somebody, or lots of people really, should check that hash. And for Testnet and signet, it doesn't really matter. Nobody really checked the hash, but it's just Testnet and signet. But for Mainnet, you probably want to have a whole bunch of people check that. So that's one of the reasons why that was delayed a bit. And then also because it still needs a bit more testing, I think, that feature. So the baby steps here are you just put all the code inside Bitcoin Core and you turn it on for Testnet for people who want to try it. And then if people don't find problems, I guess eventually we'll turn it on for Mainnet. It's still an opt-in feature regardless.
Aaron van Wirdum Right. Okay. So that's also merged in Bitcoin Core. So we'll, well, I guess for testnet will be available also in Bitcoin Core 26 in November.
Sjors Provoost Yep.
Aaron van Wirdum I think that pretty much covers the episode. One thing I thought of sort of during halfway and I didn't want to bring it up immediately. Just to be clear, I actually do still work with Bitcoin Magazine. There's no bad blood or anything like that in case anyone got that impression. It's just a podcast. It's now an independent thing.
Sjors Provoost Yeah. Oh, I also had another thing. News items.
Aaron van Wirdum Even more news.
Sjors Provoost Yeah, yeah. So I recently got a grant from the OpenSats Foundation to keep working on Bitcoin Core. So that's really nice.
Aaron van Wirdum Congratulations on that.
Sjors Provoost Thank you.
Aaron van Wirdum Does that cover it, Sjors? Is that that we update all our listeners on everything they need to know for now?
Sjors Provoost I think so. Thank you for listening.
Aaron van Wirdum And then the next episode will be in a few weeks.
Sjors Provoost Will be when the next episode lands.
Aaron van Wirdum Right.
Sjors Provoost Thank you for listening to Bitcoin
Aaron van Wirdum Explained.