Skip to content
PodSubs
ShowsPeopleGuestsJobsNewsEvents
More
BlogPodCred
Menu
ShowsPeopleGuestsJobsNewsEventsBlogPodCredNetworksSign in
Join nowSign in
  • Shows
  • People
  • Jobs
  • News
  • More
    • Guests
    • Events
    • Blog
    • PodCred
    • Networks
    Join nowSign in

Bitcoin, Explained — The Technical Side of Bitcoin

Bitcoin, Explained — The Technical Side of Bitcoin artwork

Episode 84: Marathon Pool’s Invalid Block (And Some Updates About the Show)

Oct 5, 202322 minAudio
ShareXLinkedInFacebookWhatsAppEmail

In this episode of Bitcoin, Explained, Aaron and Sjors discuss an invalid block mined by Marathon Pool. They explain why the block was invalid, what caused it (and what didn’t), and why that didn’t affect the Bitcoin network. Aaron and Sjors also provide some updates about the show, and what that means moving forward. Finally, Sjors briefly mentions some notable Bitcoin Core updates that were recently merged. For more information on the invalid block, also see: https://b10c.me/observations/07-invalid-block-809478/ Chapters 00:00:00 Show updates and independence from Bitcoin Magazine 00:03:57 A new topic-driven release schedule 00:07:09 Marathon Pool’s invalid block and transaction ordering 00:10:16 Fee-rate sorting and Marathon’s experiment 00:13:56 Why SPV nodes accepted the invalid block 00:15:39 The risks of custom block-building software 00:17:05 Peer-to-peer encryption merged into Bitcoin Core 00:19:31 AssumeUTXO on testnet and signet

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 WirdumActually, is that still our name, Sjors? Are we still called Bitcoin Explained?

Sjors ProvoostYeah, that's up for debate. But we have some exciting news, right?

Aaron van WirdumWe'll get to that in a minute then.

Sjors ProvoostOkay.

Aaron van WirdumYeah, 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 ProvoostThat's right.

Aaron van WirdumYou went to a couple of conferences. I think you went to, where did you go?

Sjors ProvoostI 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 WirdumRight. So you were away for what? A month or something?

Sjors ProvoostYep.

Aaron van WirdumYou were away for a while. Now you're back. Okay. So, the big news, Sjors, is... What's the big news?

Sjors ProvoostWe've been acquired.

Aaron van WirdumWe've been acquired. Who acquired us?

Sjors ProvoostWe. We acquired ourselves.

Aaron van WirdumThat's a very positive spin. Okay, we're not a Bitcoin Magazine podcast anymore. That's basically the story here, right?

Sjors ProvoostThat's right.

Aaron van WirdumYeah, 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 ProvoostOh, I thought it was just us.

Aaron van WirdumThere'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 ProvoostWell, I do really appreciate Bitcoin Magazine helping us through those first three years almost.

Aaron van WirdumYeah, 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 ProvoostEven 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 WirdumYou 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 ProvoostWell, 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 WirdumNo one knows how to spell any word in that name.

Sjors ProvoostSo maybe we'll just use both names. We'll figure it out.

Aaron van WirdumI mean, maybe we'll just cater a niche audience from now on. Our fan base knows how to spell our name.

Sjors ProvoostAnyway, we've been chatting now for three minutes and 40 seconds. Shall we talk about Bitcoin?

Aaron van WirdumNo, 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.

Aaron van WirdumSometimes 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 ProvoostYeah, 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 WirdumYeah. 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

Aaron van Wirdumago 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 ProvoostProbably, but I still haven't gotten any formal invite.

Aaron van WirdumOkay. Are you not a speaker?

Sjors ProvoostNo.

Aaron van WirdumYou're not invited? That's surprising to me. All right.

Sjors ProvoostI 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 WirdumYeah, I don't think we're going to do that Sjors.

Sjors ProvoostOkay, well.

Aaron van WirdumI 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 ProvoostSix minutes and 50 seconds.

Aaron van WirdumAll 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 ProvoostThat's right.

Aaron van WirdumAt the time of recording, I think, do you know when it happened exactly?

Sjors ProvoostNo, about a week ago.

Aaron van WirdumYeah, well, give a date. What's the date today? We're like early October?

Sjors ProvoostIt was block 809478.

Aaron van WirdumSo 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 ProvoostWell, yeah, basically when you mine a...

Aaron van WirdumWait, there's something else, I think. Yes, there's something else. We're getting to the invalid block in a minute.

Sjors ProvoostWell, we can get to the invalid block now and just get to the other things later.

Aaron van WirdumIs that a logical order, you think?

Sjors ProvoostYeah, because we've already started this topic.

Aaron van WirdumOkay, we're already started. Let's go. Why was this block invalid?

Sjors ProvoostSo 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 WirdumThe block can't be too big.

Sjors ProvoostYep. 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 WirdumOh, this confusing A comes before B.

Sjors ProvoostOkay, we'll do it the other way around.

Aaron van WirdumYes.

Sjors ProvoostIf 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 WirdumWait, so why is that? Why is this a rule? Why not just remove this rule? What's the logic?

Sjors ProvoostThe 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 WirdumI 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 Provoostthe 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 WirdumOkay, so why were the transactions in this block in the wrong order?

Sjors ProvoostWell, 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 WirdumI thought you already said. I mean, that's pretty obvious at this point that that was the problem.

Sjors ProvoostI 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 WirdumLet's start with the why.

Sjors ProvoostWe 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 WirdumNot all transactions in the block, right? So only these transactions were ordered?

Sjors ProvoostNo, 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 WirdumOkay, so all the transactions in the block were sorted by fee rate.

Sjors ProvoostI believe so, yeah. Okay, and that's not the correct order. Well, that's what I read, I haven't checked it.

Aaron van WirdumDid you read it from a credible source at least?

Sjors ProvoostYes. There's a blog post we'll link in the show notes from 0xB10C.

Aaron van WirdumOkay. 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 ProvoostYeah, 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 WirdumRight. Well, that's the only thing they said. So it sounds like you...

Sjors ProvoostSo 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 WirdumOkay.

Sjors ProvoostBecause 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 WirdumYou're not much of a block connoisseur, it sounds like.

Sjors ProvoostI don't know. I think Bitcoin Core does a good job at it.

Aaron van WirdumYou don't care too much about the visual aspects of a block.

Sjors ProvoostSo 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 WirdumRight, that was question two. So yeah, it wasn't a Bitcoin Core thing.

Sjors ProvoostNo.

Aaron van WirdumOkay. I had another question. Oh yeah, so they were experimenting with it on testnet, apparently.

Sjors ProvoostYeah, 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

Sjors Provoostdeploying it on mainnet and potentially burning an enormous amount of money?

Aaron van WirdumRight. 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 ProvoostYes. And then, of course, within a few minutes, it would have been... reorged.

Aaron van WirdumIt would have been reorged.

Sjors ProvoostAnd probably also included because I don't think there were any double spends here.

Aaron van WirdumRight, yeah. Still, I mean, it's kind of an interesting or telling example of why SPV nodes are a potential risk.

Sjors ProvoostYeah, SPV nodes do not check this.

Aaron van WirdumIn 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 ProvoostYes.

Aaron van WirdumRight? Okay, well, that's all pretty fine and clear so far. Is there anything to say about this, Sjors?

Sjors ProvoostWell, 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 WirdumWell, they did, and they ignored what happened on Testnet, apparently.

Sjors ProvoostI 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 WirdumYou can also give me $170,000 as an experiment to see what I'll do with it.

Sjors ProvoostUp to you. It's free world.

Aaron van WirdumAll right, I think that sort of covers the invalid block.

Sjors ProvoostOh, 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 WirdumOh, right.

Sjors ProvoostBut 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

Sjors Provoostrule 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 WirdumThe Bitcoin Core developer advises to use Bitcoin Core.

Sjors ProvoostYes. We have a saying in Dutch. Wij van WC-Eend adviseren WC-Eend.

Aaron van WirdumRight. I mean, are you going to even explain that? No, never mind. If you're not Dutch, bad luck.

Sjors ProvoostYou would miss this wisdom.

Aaron van WirdumAll right, I think that covers the invalid block, basically, right?

Sjors ProvoostYeah.

Aaron van WirdumThat 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 ProvoostYeah, 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 WirdumYeah.

Sjors ProvoostThe idea has been around for six, seven years, I think, initially introduced by Jonas Schnelli.

Aaron van WirdumYeah, something like that. Can you give a two-sentence summary for whoever wants to jog their memory?

Sjors ProvoostYeah, 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

Sjors Provoostit. So anybody observing it can just see noise.

Aaron van WirdumRight. 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 ProvoostProbably 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

Sjors Provoostjust 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 WirdumRight.

Sjors ProvoostAnd that tells you that there's nobody in the middle.

Aaron van WirdumRight. 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 ProvoostThat's right. AssumeUTXO.

Aaron van WirdumRight. Okay.

Sjors ProvoostFor Testnet and for Signet.

Aaron van WirdumOkay, so that's not on mainnet yet, but, but the core—sorry, the code is in Bitcoin Core now.

Sjors ProvoostYes, 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 WirdumSo why is it not available for mainnet yet? What's the reasoning there?

Sjors ProvoostBecause 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 WirdumRight, yeah. So the thing we're talking about now, episode 14, if you know—yeah, if you want to know more about that.

Sjors ProvoostIt'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

Sjors Provoostinside 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 WirdumRight. 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 ProvoostYep.

Aaron van WirdumI 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 ProvoostYeah. Oh, I also had another thing. News items.

Aaron van WirdumEven more news.

Sjors ProvoostYeah, yeah. So I recently got a grant from the OpenSats Foundation to keep working on Bitcoin Core. So that's really nice.

Aaron van WirdumCongratulations on that.

Sjors ProvoostThank you.

Aaron van WirdumDoes that cover it, Sjors? Is that that we update all our listeners on everything they need to know for now?

Sjors ProvoostI think so. Thank you for listening.

Aaron van WirdumAnd then the next episode will be in a few weeks.

Sjors ProvoostWill be when the next episode lands.

Aaron van WirdumRight.

Sjors ProvoostThank you for listening to Bitcoin

Aaron van WirdumExplained.

Open the transcript file

Hosts and Guests

Hosts

  • Aaron van Wirdum Host Feed-stated
  • Sjors Provoost Host Feed-stated

Credit the people on this episode

Be the first to rate this episode

More episodes

All episodes
  1. Episode 102: Bitcoin Core 32.1 — Live

    Nov 6, 202650 minVideo

    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...

    Listen to the audio

    Credit the people on this episode

  2. Episode 101: The COLDCARD Hack

    Aug 26, 20261 hr 6 minAudio

    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...

    Credit the people on this episode

  3. Emergency broadcast: COLDCARD vulnerability

    Jul 31, 20261 minAudio

    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:...

    Credit the people on this episode

  4. Episode 100: Bitcoin Core 31

    Jul 15, 202641 minVideo

    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...

    Listen to the audio

    Credit the people on this episode

  5. Episode 99: Bitcoin Core 30

    Nov 6, 202551 minVideo

    Aaron and Sjors discuss what’s new in Bitcoin Core 30. Chapters 00:00:00 Release Overview and Controversy 00:04:58 OP_RETURN Policy Changes 00:12:32 Lower Minimum Relay Fees 00:23:06 Sigops Limits and Consensus Cleanup...

    Listen to the audio

    Credit the people on this episode