WEBVTT - Automatic transcript; recognition may contain errors. Reviewed for technical wording and speaker labels. Times match the published episode.

00:00:20.430 --> 00:00:22.710
<v Aaron van Wirdum>Live from Utrecht, this is Bitcoin

00:00:22.710 --> 00:00:24.310
<v Sjors Provoost>Explained.

00:00:24.670 --> 00:00:25.210
<v Aaron van Wirdum>Hey Sjors.

00:00:25.650 --> 00:00:26.070
<v Sjors Provoost>Hello.

00:00:26.370 --> 00:00:30.050
<v Aaron van Wirdum>Actually, is that still our name, Sjors? Are we still called Bitcoin Explained?

00:00:30.290 --> 00:00:33.630
<v Sjors Provoost>Yeah, that's up for debate. But we have some exciting news, right?

00:00:33.850 --> 00:00:35.330
<v Aaron van Wirdum>We'll get to that in a minute then.

00:00:35.670 --> 00:00:35.810
<v Sjors Provoost>Okay.

00:00:36.450 --> 00:00:41.330
<v Aaron van Wirdum>Yeah, so we've been away for a while. You haven't heard from us for a couple of

00:00:41.330 --> 00:00:45.550
<v Aaron van Wirdum>weeks, dear listener. So we're going to offer you an update about what's going

00:00:45.550 --> 00:00:50.210
<v Aaron van Wirdum>on. Because something's going on. First of all, though, Sjors, one of the reasons

00:00:50.210 --> 00:00:53.790
<v Aaron van Wirdum>we've been away for a while is because you were literally away for a while.

00:00:54.030 --> 00:00:54.590
<v Sjors Provoost>That's right.

00:00:54.670 --> 00:00:57.870
<v Aaron van Wirdum>You went to a couple of conferences. I think you went to, where did you go?

00:00:58.030 --> 00:01:03.820
<v Sjors Provoost>I went to TABConf in Atlanta and I visited the Bitcoin Park. And then

00:01:03.820 --> 00:01:08.530
<v Sjors Provoost>I went to BTC Azores in the middle of the Atlantic.

00:01:08.870 --> 00:01:11.970
<v Aaron van Wirdum>Right. So you were away for what? A month or something?

00:01:12.250 --> 00:01:12.370
<v Sjors Provoost>Yep.

00:01:12.590 --> 00:01:18.270
<v Aaron van Wirdum>You were away for a while. Now you're back. Okay. So, the

00:01:18.880 --> 00:01:23.090
<v Aaron van Wirdum>big news, Sjors, is... What's the big news?

00:01:23.250 --> 00:01:24.290
<v Sjors Provoost>We've been acquired.

00:01:24.570 --> 00:01:26.790
<v Aaron van Wirdum>We've been acquired. Who acquired us?

00:01:26.970 --> 00:01:29.850
<v Sjors Provoost>We. We acquired ourselves.

00:01:30.110 --> 00:01:35.320
<v Aaron van Wirdum>That's a very positive spin. Okay, we're not a Bitcoin Magazine podcast anymore.

00:01:35.420 --> 00:01:37.360
<v Aaron van Wirdum>That's basically the story here, right?

00:01:37.780 --> 00:01:38.500
<v Sjors Provoost>That's right.

00:01:38.760 --> 00:01:44.400
<v Aaron van Wirdum>Yeah, so, dear listeners, so, yeah, Bitcoin Magazine has been going through a

00:01:44.400 --> 00:01:50.000
<v Aaron van Wirdum>reshuffle, essentially. And one of the things that was decided is that Bitcoin

00:01:50.000 --> 00:01:55.350
<v Aaron van Wirdum>Magazine is not supporting podcasts anymore. Bitcoin Explained is a podcast. So

00:01:55.350 --> 00:01:57.810
<v Aaron van Wirdum>we're not supported by Bitcoin Magazine anymore.

00:01:57.990 --> 00:01:58.970
<v Sjors Provoost>Oh, I thought it was just us.

00:01:59.810 --> 00:02:04.570
<v Aaron van Wirdum>There's another one. Well, yeah, that's sort of the thing. Like we used to have a

00:02:04.570 --> 00:02:09.490
<v Aaron van Wirdum>bunch of podcasts at Bitcoin Magazine. And I don't remember which ones, but then

00:02:09.490 --> 00:02:15.130
<v Aaron van Wirdum>one by one, they sort of stopped. And there were only two left at this point. And

00:02:15.130 --> 00:02:19.390
<v Aaron van Wirdum>it was just kind of this part of Bitcoin Magazine that was sort of ignored and

00:02:19.390 --> 00:02:24.370
<v Aaron van Wirdum>sort of on the wayside. But it still required some resources to kind of keep it

00:02:24.370 --> 00:02:29.730
<v Aaron van Wirdum>running. And at some point, the decision was made that Bitcoin Magazine right now

00:02:29.730 --> 00:02:31.110
<v Aaron van Wirdum>just doesn't do any podcasts.

00:02:31.610 --> 00:02:35.830
<v Sjors Provoost>Well, I do really appreciate Bitcoin Magazine helping us through those first

00:02:35.830 --> 00:02:36.930
<v Sjors Provoost>three years almost.

00:02:37.390 --> 00:02:41.670
<v Aaron van Wirdum>Yeah, absolutely, and Bitcoin Magazine was gracious enough to just let us

00:02:41.670 --> 00:02:46.850
<v Aaron van Wirdum>continue the podcast so you know we don't have any fights about name rights or we

00:02:46.850 --> 00:02:51.910
<v Aaron van Wirdum>can just keep going. So that's nice enough. So in a way not much is going to

00:02:51.910 --> 00:02:57.490
<v Aaron van Wirdum>change. We're still going to make the podcast we even found a new editor, Stijn,

00:02:57.490 --> 00:03:02.370
<v Aaron van Wirdum>the world famous Stijn in the Netherlands, the best editor in the country. He's

00:03:02.370 --> 00:03:04.290
<v Aaron van Wirdum>gonna edit our podcasts going forward.

00:03:04.290 --> 00:03:08.230
<v Sjors Provoost>Even if we said he was not the best editor, he's the editor, so he can just make

00:03:08.230 --> 00:03:09.330
<v Sjors Provoost>us say he's the best editor.

00:03:09.330 --> 00:03:14.450
<v Aaron van Wirdum>You can edit out whatever bad things we say about Stijn. Uh what else so yeah so

00:03:14.450 --> 00:03:18.950
<v Aaron van Wirdum>basically not much will change in that sense. There will still be a podcast. I I

00:03:18.950 --> 00:03:23.350
<v Aaron van Wirdum>guess that's the question right? Like we don't have any evil corporate overlords

00:03:23.350 --> 00:03:27.030
<v Aaron van Wirdum>anymore, Sjors. That's why I want to move back to Van Wirdum Sjorsnado.

00:03:27.370 --> 00:03:31.510
<v Sjors Provoost>Well, we'll have to chat about that. The upside of Van Wirdum Sjorsnado is that

00:03:31.510 --> 00:03:36.390
<v Sjors Provoost>it's the best name for a podcast ever. The downside is that if you tell people to

00:03:36.390 --> 00:03:40.810
<v Sjors Provoost>please subscribe to Van Wirdum Sjorsnado, they will stare at you.

00:03:41.180 --> 00:03:44.060
<v Aaron van Wirdum>No one knows how to spell any word in that name.

00:03:44.260 --> 00:03:46.820
<v Sjors Provoost>So maybe we'll just use both names. We'll figure it out.

00:03:46.880 --> 00:03:51.500
<v Aaron van Wirdum>I mean, maybe we'll just cater a niche audience from now on. Our fan base knows

00:03:51.500 --> 00:03:52.480
<v Aaron van Wirdum>how to spell our name.

00:03:52.960 --> 00:03:57.140
<v Sjors Provoost>Anyway, we've been chatting now for three minutes and 40 seconds. Shall we talk about Bitcoin?

00:03:57.440 --> 00:04:02.340
<v Aaron van Wirdum>No, no, I'm not done yet. One other thing I wanted to mention is, so we were

00:04:02.340 --> 00:04:07.990
<v Aaron van Wirdum>already kind of discussing that before we even... went independent,

00:04:08.250 --> 00:04:14.250
<v Aaron van Wirdum>split off from Bitcoin Magazine, is that from now on, our

00:04:14.250 --> 00:04:19.430
<v Aaron van Wirdum>podcast will be sort of content-driven rather than time-driven, if that's the

00:04:19.430 --> 00:04:24.540
<v Aaron van Wirdum>right way to put it. We used to basically make an episode every other week. Now,

00:04:24.700 --> 00:04:28.160
<v Aaron van Wirdum>we already slipped that sometimes, either because one of us were traveling.

00:04:28.860 --> 00:04:34.580
<v Aaron van Wirdum>Sometimes we didn't have a topic in mind. That was a reason we sometimes skipped

00:04:34.580 --> 00:04:39.240
<v Aaron van Wirdum>an episode. And moving forward, that will sort of just be the order of things. I

00:04:39.240 --> 00:04:43.520
<v Aaron van Wirdum>think we both agree. If you have an interesting topic to discuss or I have an

00:04:43.520 --> 00:04:46.720
<v Aaron van Wirdum>interesting idea, that will be a reason to make a podcast.

00:04:47.990 --> 00:04:50.150
<v Aaron van Wirdum>And if we don't have that, there won't be a podcast.

00:04:51.710 --> 00:04:55.950
<v Aaron van Wirdum>We won't necessarily make a podcast every other week, at least for the time being.

00:04:56.390 --> 00:04:59.530
<v Sjors Provoost>Yeah, that's right. And I think it's interesting to give some context there. In

00:04:59.530 --> 00:05:03.890
<v Sjors Provoost>the beginning, coming up with ideas for podcasts was quite easy because there

00:05:03.890 --> 00:05:09.110
<v Sjors Provoost>were lots of topics left to explain. Nowadays, we usually spend like half an hour

00:05:10.590 --> 00:05:13.870
<v Sjors Provoost>discussing possible topics. And I'm like, meh, I don't feel like this one. Too

00:05:13.870 --> 00:05:18.870
<v Sjors Provoost>much work, etc. So it'll be a bit more difficult, but we'll get there. And

00:05:18.870 --> 00:05:22.170
<v Sjors Provoost>sometimes it's happened that I thought the topic would be super uninteresting and

00:05:22.170 --> 00:05:24.710
<v Sjors Provoost>then we ended up spending 50 minutes and it was a good episode. So,

00:05:25.190 --> 00:05:30.750
<v Aaron van Wirdum>Yeah. Anyway, so I don't think moving forward going forward you—or this dear

00:05:30.750 --> 00:05:34.810
<v Aaron van Wirdum>listener— will necessarily get a podcast every other week but there will still be

00:05:34.810 --> 00:05:39.710
<v Aaron van Wirdum>podcasts. We'll see how often or how many I guess, right we'll figure it out as

00:05:39.710 --> 00:05:45.320
<v Aaron van Wirdum>we go along. What we can say is, so we're kind of making this podcast we're still

00:05:45.320 --> 00:05:50.820
<v Aaron van Wirdum>in the introduction stage right? We're kind of making this podcast as uh kind of

00:05:50.820 --> 00:05:55.260
<v Aaron van Wirdum>a placeholder almost, because even at this point the previous podcast was a while

00:05:55.260 --> 00:05:59.240
<v Aaron van Wirdum>ago in part because we were traveling in part because all the stuff I was just

00:05:59.360 --> 00:06:04.360
<v Aaron van Wirdum>telling you about or this dear listener and then in the next couple of weeks

00:06:04.360 --> 00:06:07.020
<v Aaron van Wirdum>there will also be there will be Bitcoin Amsterdam there will be other

00:06:07.020 --> 00:06:11.900
<v Aaron van Wirdum>conferences I'll be going to. So the next podcast might also take a little while

00:06:11.900 --> 00:06:16.440
<v Aaron van Wirdum>before we, but we, so we wanted to give you something because otherwise there

00:06:16.440 --> 00:06:19.540
<v Aaron van Wirdum>would have been no podcast for like three months or something. So we're making

00:06:19.540 --> 00:06:22.220
<v Aaron van Wirdum>this one. By the way, Sjors, are you going to Bitcoin Amsterdam?

00:06:23.380 --> 00:06:26.660
<v Sjors Provoost>Probably, but I still haven't gotten any formal invite.

00:06:26.820 --> 00:06:27.940
<v Aaron van Wirdum>Okay. Are you not a speaker?

00:06:28.830 --> 00:06:29.190
<v Sjors Provoost>No.

00:06:29.430 --> 00:06:31.890
<v Aaron van Wirdum>You're not invited? That's surprising to me. All right.

00:06:32.010 --> 00:06:36.610
<v Sjors Provoost>I think I was invited to be a speaker, but then it was never followed up, and we

00:06:36.610 --> 00:06:39.490
<v Sjors Provoost>might be doing some recording, but I don't know how that's going.

00:06:39.810 --> 00:06:41.490
<v Aaron van Wirdum>Yeah, I don't think we're going to do that Sjors.

00:06:41.870 --> 00:06:42.550
<v Sjors Provoost>Okay, well.

00:06:42.670 --> 00:06:47.010
<v Aaron van Wirdum>I mean, that was part of the original sort of before Bitcoin Magazine split us up

00:06:47.010 --> 00:06:48.230
<v Aaron van Wirdum>kind of deal. I don't know.

00:06:49.510 --> 00:06:52.950
<v Aaron van Wirdum>Don't count on it. I'm not counting on it. I don't think I'm going to do that.

00:06:54.830 --> 00:07:00.450
<v Aaron van Wirdum>All right, so that's it. Honestly, that was kind of the main reason,

00:07:00.750 --> 00:07:04.630
<v Aaron van Wirdum>as far as I'm concerned, that we're making this podcast, just to tell you all

00:07:04.630 --> 00:07:07.770
<v Aaron van Wirdum>this stuff that I told you in the last, how long are we recording now?

00:07:07.990 --> 00:07:09.750
<v Sjors Provoost>Six minutes and 50 seconds.

00:07:09.910 --> 00:07:15.750
<v Aaron van Wirdum>All right, almost seven minutes. However, dear listener, we didn't want to send

00:07:15.750 --> 00:07:20.850
<v Aaron van Wirdum>you home empty-handed. So Sjors and I did find a topic for you that you'll find

00:07:20.850 --> 00:07:26.820
<v Aaron van Wirdum>fascinating, I'm sure. Sjors, we're going to discuss an invalid block that

00:07:26.820 --> 00:07:28.580
<v Aaron van Wirdum>was mined last week.

00:07:28.760 --> 00:07:29.340
<v Sjors Provoost>That's right.

00:07:29.600 --> 00:07:32.920
<v Aaron van Wirdum>At the time of recording, I think, do you know when it happened exactly?

00:07:33.240 --> 00:07:34.060
<v Sjors Provoost>No, about a week ago.

00:07:34.920 --> 00:07:38.860
<v Aaron van Wirdum>Yeah, well, give a date. What's the date today? We're like early October?

00:07:39.200 --> 00:07:41.820
<v Sjors Provoost>It was block 809478.

00:07:41.960 --> 00:07:47.240
<v Aaron van Wirdum>So it was like late September. Okay, 2023, in case you're listening to this in

00:07:47.240 --> 00:07:52.660
<v Aaron van Wirdum>the future. So an invalid block was mined. It was mined by MarathonPool.

00:07:53.740 --> 00:07:58.240
<v Aaron van Wirdum>And this is where I sort of turn it over to. So what happened? Why was it invalid?

00:07:58.940 --> 00:08:02.920
<v Sjors Provoost>Well, yeah, basically when you mine a...

00:08:02.920 --> 00:08:08.560
<v Aaron van Wirdum>Wait, there's something else, I think. Yes, there's something else.

00:08:08.660 --> 00:08:10.640
<v Aaron van Wirdum>We're getting to the invalid block in a minute.

00:08:11.200 --> 00:08:14.480
<v Sjors Provoost>Well, we can get to the invalid block now and just get to the other things later.

00:08:15.740 --> 00:08:17.600
<v Aaron van Wirdum>Is that a logical order, you think?

00:08:17.780 --> 00:08:19.380
<v Sjors Provoost>Yeah, because we've already started this topic.

00:08:19.380 --> 00:08:20.580
<v Aaron van Wirdum>Okay, we're already started. Let's go.

00:08:21.850 --> 00:08:23.210
<v Aaron van Wirdum>Why was this block invalid?

00:08:23.570 --> 00:08:28.650
<v Sjors Provoost>So basically a block has to follow a bunch of rules as defined by the Bitcoin

00:08:28.650 --> 00:08:32.190
<v Sjors Provoost>consensus rules. You know, don't create too many coins.

00:08:33.710 --> 00:08:37.250
<v Sjors Provoost>Don't do any double spending. I guess that's really the same as don't create any

00:08:37.250 --> 00:08:42.350
<v Sjors Provoost>new coins. Signatures have to be valid. There's lots of little, big rules, little

00:08:42.350 --> 00:08:45.250
<v Sjors Provoost>rules, subtle rules, et cetera. One of the rules is that—

00:08:45.250 --> 00:08:46.630
<v Aaron van Wirdum>The block can't be too big.

00:08:46.930 --> 00:08:52.320
<v Sjors Provoost>Yep. One of the rules is that if you have a transaction A, which is spending from

00:08:52.320 --> 00:08:53.200
<v Sjors Provoost>transaction B,

00:08:54.490 --> 00:08:59.470
<v Sjors Provoost>then transaction B must happen first inside the block.

00:08:59.650 --> 00:09:01.930
<v Aaron van Wirdum>Oh, this confusing A comes before B.

00:09:02.070 --> 00:09:03.150
<v Sjors Provoost>Okay, we'll do it the other way around.

00:09:03.310 --> 00:09:03.490
<v Aaron van Wirdum>Yes.

00:09:03.490 --> 00:09:08.570
<v Sjors Provoost>If you have a transaction B, which is spending from transaction A, then

00:09:08.570 --> 00:09:13.250
<v Sjors Provoost>transaction B must be after transaction A. So you cannot, yeah, you cannot look

00:09:13.250 --> 00:09:17.250
<v Sjors Provoost>at a block as a whole and say, well, it nets out and it's all fine. No, they have

00:09:17.250 --> 00:09:20.990
<v Sjors Provoost>to be in the right order inside the block. That's actually quite annoying because

00:09:20.990 --> 00:09:24.630
<v Sjors Provoost>there's some optimizations that you could do from a block verification

00:09:24.630 --> 00:09:28.330
<v Sjors Provoost>perspective if the order of the transaction didn't matter because then you could

00:09:28.330 --> 00:09:32.940
<v Sjors Provoost>just check them all and then not worry about ordering. But you can't. You have to

00:09:32.940 --> 00:09:34.340
<v Sjors Provoost>check them one by one in sequence.

00:09:34.880 --> 00:09:40.220
<v Aaron van Wirdum>Wait, so why is that? Why is this a rule? Why not just remove this rule? What's

00:09:40.220 --> 00:09:41.040
<v Aaron van Wirdum>the logic?

00:09:41.880 --> 00:09:45.360
<v Sjors Provoost>The rule is there because Satoshi put it in there, either deliberately or

00:09:45.360 --> 00:09:50.410
<v Sjors Provoost>probably not really thinking about it. And it's there. If we remove it, it's a hard fork.

00:09:51.210 --> 00:09:55.390
<v Aaron van Wirdum>I see. Okay, so this has been a rule since the very beginning. So the order that

00:09:55.390 --> 00:09:58.410
<v Aaron van Wirdum>the transactions are included in a block need to be...

00:09:58.800 --> 00:10:02.180
<v Sjors Provoost>the right order yeah, and of course it would have been nice if you could say well

00:10:02.180 --> 00:10:06.050
<v Sjors Provoost>as long as you know if the if the transaction… As long as it's somewhere in the

00:10:06.050 --> 00:10:09.390
<v Sjors Provoost>block, it's fine. But no, it has to be in the right order inside the block. And

00:10:09.390 --> 00:10:12.990
<v Sjors Provoost>if you ask Bitcoin Core to create a block for you as a miner, which you can do,

00:10:13.530 --> 00:10:16.450
<v Sjors Provoost>then Bitcoin Core will make sure that happens, among other checks.

00:10:16.750 --> 00:10:21.330
<v Aaron van Wirdum>Okay, so why were the transactions in this block in the wrong order?

00:10:21.510 --> 00:10:25.070
<v Sjors Provoost>Well, I guess now you're spoiling what actually went wrong. But yes, the thing

00:10:25.070 --> 00:10:27.530
<v Sjors Provoost>that went wrong is that the transactions were not in the correct order.

00:10:28.010 --> 00:10:30.770
<v Aaron van Wirdum>I thought you already said. I mean, that's pretty obvious at this point that that

00:10:30.770 --> 00:10:31.310
<v Aaron van Wirdum>was the problem.

00:10:31.410 --> 00:10:36.120
<v Sjors Provoost>I guess it was a bit of a... of a hint there. Yeah, so basically they were in the

00:10:36.120 --> 00:10:40.960
<v Sjors Provoost>wrong order, and then the first question is, why? And also the second question

00:10:40.960 --> 00:10:43.320
<v Sjors Provoost>for me would be, oh shit, is there a bug in Bitcoin Core?

00:10:44.620 --> 00:10:46.460
<v Sjors Provoost>Now, turns out that...

00:10:46.460 --> 00:10:47.360
<v Aaron van Wirdum>Let's start with the why.

00:10:48.560 --> 00:10:49.780
<v Sjors Provoost>We don't know why.

00:10:51.040 --> 00:10:56.100
<v Sjors Provoost>Like, I don't understand what the thinking was for this particular mistake.

00:10:58.490 --> 00:11:03.850
<v Sjors Provoost>We do know that I think the transactions were ordered by feerate for some reason,

00:11:04.110 --> 00:11:07.290
<v Sjors Provoost>but there's really no sane reason to do that, as far as I know.

00:11:07.450 --> 00:11:11.490
<v Aaron van Wirdum>Not all transactions in the block, right? So only these transactions were ordered?

00:11:11.650 --> 00:11:16.270
<v Sjors Provoost>No, I think they took a normal block as proposed by Bitcoin Core, which has the

00:11:16.270 --> 00:11:20.150
<v Sjors Provoost>transactions in some order, and then they said, ah, it looks nicer if we sort it

00:11:20.150 --> 00:11:20.850
<v Sjors Provoost>by fee rate.

00:11:21.010 --> 00:11:23.770
<v Aaron van Wirdum>Okay, so all the transactions in the block were sorted by fee rate.

00:11:23.870 --> 00:11:28.470
<v Sjors Provoost>I believe so, yeah. Okay, and that's not the correct order. Well, that's what I

00:11:28.470 --> 00:11:29.230
<v Sjors Provoost>read, I haven't checked it.

00:11:30.590 --> 00:11:32.450
<v Aaron van Wirdum>Did you read it from a credible source at least?

00:11:32.730 --> 00:11:37.970
<v Sjors Provoost>Yes. There's a blog post we'll link in the show notes from 0xB10C.

00:11:38.490 --> 00:11:43.460
<v Aaron van Wirdum>Okay. Well, so what I read... Probably in the same blog post, actually.

00:11:44.240 --> 00:11:48.680
<v Aaron van Wirdum>No, well, no, also Marathon said it on Twitter, is that they were experimenting

00:11:48.680 --> 00:11:53.080
<v Aaron van Wirdum>in some way or another. So they were trying to find optimizations. They were

00:11:53.080 --> 00:11:57.640
<v Aaron van Wirdum>using a small amount of their hash power to, I guess, in some way figure out if

00:11:57.640 --> 00:12:00.420
<v Aaron van Wirdum>they could mine even faster or more efficient.

00:12:00.680 --> 00:12:04.460
<v Sjors Provoost>Yeah, but I do not see how you can fit more transactions in a block by changing

00:12:04.460 --> 00:12:08.820
<v Sjors Provoost>the order. Does it make the block any smaller? It's not like compressing.

00:12:09.120 --> 00:12:12.560
<v Aaron van Wirdum>Right. Well, that's the only thing they said. So it sounds like you...

00:12:12.560 --> 00:12:17.760
<v Sjors Provoost>So in general, they were doing experiments. That's okay. That's one thing. But I

00:12:17.760 --> 00:12:20.760
<v Sjors Provoost>don't understand what the point was of this particular experiment.

00:12:21.910 --> 00:12:22.350
<v Aaron van Wirdum>Okay.

00:12:22.590 --> 00:12:26.550
<v Sjors Provoost>Because sorting transactions differently might look prettier. I guess if you want

00:12:26.550 --> 00:12:32.270
<v Sjors Provoost>to make a nice chart of the block and you want to color the block by fee,

00:12:32.570 --> 00:12:35.730
<v Sjors Provoost>with high fees having a darker color and light fees having a lighter color, then

00:12:35.730 --> 00:12:40.310
<v Sjors Provoost>maybe if you order them by fee, then it looks pretty. But mechanically or in

00:12:40.310 --> 00:12:44.350
<v Sjors Provoost>terms of efficiency, I don't see the point. In fact, it takes longer because you

00:12:44.350 --> 00:12:49.360
<v Sjors Provoost>have to sort the block, which takes another split second. And every split second

00:12:49.360 --> 00:12:51.460
<v Sjors Provoost>you need more time to do stuff.

00:12:51.840 --> 00:12:54.780
<v Aaron van Wirdum>You're not much of a block connoisseur, it sounds like.

00:12:55.680 --> 00:12:58.200
<v Sjors Provoost>I don't know. I think Bitcoin Core does a good job at it.

00:12:58.320 --> 00:13:01.620
<v Aaron van Wirdum>You don't care too much about the visual aspects of a block.

00:13:01.640 --> 00:13:07.320
<v Sjors Provoost>So in any case, they said it was not Bitcoin Core's fault, so that's good news,

00:13:07.380 --> 00:13:09.940
<v Sjors Provoost>because otherwise there might be some bug out there. That's not good.

00:13:11.160 --> 00:13:14.820
<v Aaron van Wirdum>Right, that was question two. So yeah, it wasn't a Bitcoin Core thing.

00:13:15.080 --> 00:13:15.280
<v Sjors Provoost>No.

00:13:15.720 --> 00:13:20.240
<v Aaron van Wirdum>Okay. I had another question. Oh yeah, so they were experimenting with it on

00:13:20.240 --> 00:13:21.240
<v Aaron van Wirdum>testnet, apparently.

00:13:21.600 --> 00:13:27.480
<v Sjors Provoost>Yeah, so this is the other observation that our friend 0xB10C, how

00:13:27.480 --> 00:13:31.200
<v Sjors Provoost>can we give him a quicker name? B10C? I don't know.

00:13:33.400 --> 00:13:37.520
<v Sjors Provoost>He observed that it looked like they were trying this on testnet the day before.

00:13:37.860 --> 00:13:40.920
<v Sjors Provoost>So if you looked on testnet, you saw a similar pattern, and in fact, you were

00:13:40.920 --> 00:13:44.460
<v Sjors Provoost>seeing the same error messages. Basically, the testnet nodes were rejecting this

00:13:44.460 --> 00:13:48.710
<v Sjors Provoost>block as invalid. Which then raises the question of, if you're testing on

00:13:48.710 --> 00:13:52.990
<v Sjors Provoost>testnet, why are you not looking at the result of that experiment before

00:13:52.990 --> 00:13:56.830
<v Sjors Provoost>deploying it on mainnet and potentially burning an enormous amount of money?

00:13:57.560 --> 00:14:03.260
<v Aaron van Wirdum>Right. So if you were running an SPV node, and

00:14:03.260 --> 00:14:06.640
<v Aaron van Wirdum>there was a transaction to you in that block, you would have probably just

00:14:06.640 --> 00:14:07.880
<v Aaron van Wirdum>accepted it, right?

00:14:08.140 --> 00:14:12.930
<v Sjors Provoost>Yes. And then, of course, within a few minutes, it would have been... reorged.

00:14:12.930 --> 00:14:13.770
<v Aaron van Wirdum>It would have been reorged.

00:14:13.890 --> 00:14:17.350
<v Sjors Provoost>And probably also included because I don't think there were any double spends here.

00:14:18.210 --> 00:14:24.190
<v Aaron van Wirdum>Right, yeah. Still, I mean, it's kind of an interesting or telling example of why

00:14:24.190 --> 00:14:26.030
<v Aaron van Wirdum>SPV nodes are a potential risk.

00:14:26.330 --> 00:14:28.050
<v Sjors Provoost>Yeah, SPV nodes do not check this.

00:14:28.310 --> 00:14:33.270
<v Aaron van Wirdum>In this case, it's kind of innocent, but yeah, like you mentioned earlier in the

00:14:33.270 --> 00:14:37.470
<v Aaron van Wirdum>episode, maybe someone's trying to steal coins or create inflation, and SPV nodes

00:14:37.470 --> 00:14:41.990
<v Aaron van Wirdum>just doesn't notice that. Well, in this case, all full nodes, all Bitcoin Core

00:14:41.990 --> 00:14:46.970
<v Aaron van Wirdum>nodes, they just rejected the block as invalid and the only real loser here was

00:14:46.970 --> 00:14:51.610
<v Aaron van Wirdum>Marathon Pool because they wasted a bunch of energy and resources creating an

00:14:51.610 --> 00:14:52.210
<v Aaron van Wirdum>invalid block.

00:14:52.350 --> 00:14:52.770
<v Sjors Provoost>Yes.

00:14:53.030 --> 00:14:53.190
<v Aaron van Wirdum>Right?

00:14:54.510 --> 00:15:00.510
<v Aaron van Wirdum>Okay, well, that's all pretty fine and clear so far. Is there

00:15:00.510 --> 00:15:02.090
<v Aaron van Wirdum>anything to say about this, Sjors?

00:15:02.350 --> 00:15:07.940
<v Sjors Provoost>Well, so I'm all for experimenting. But I still don't understand why they tested

00:15:07.940 --> 00:15:10.160
<v Sjors Provoost>this on Mainnet instead of checked on Testnet.

00:15:10.380 --> 00:15:13.620
<v Aaron van Wirdum>Well, they did, and they ignored what happened on Testnet, apparently.

00:15:13.880 --> 00:15:18.560
<v Sjors Provoost>I would also say that if you are willing to spend $170,000 on an experiment,

00:15:18.900 --> 00:15:24.540
<v Sjors Provoost>consider giving me, say, $10,000 and asking me to look at your experiment for one

00:15:24.540 --> 00:15:26.860
<v Sjors Provoost>hour, and I probably would have found this.

00:15:27.240 --> 00:15:31.980
<v Aaron van Wirdum>You can also give me $170,000 as an experiment to see what I'll do with it.

00:15:33.060 --> 00:15:34.720
<v Sjors Provoost>Up to you. It's free world.

00:15:35.510 --> 00:15:39.460
<v Aaron van Wirdum>All right, I think that sort of covers the invalid block.

00:15:39.480 --> 00:15:45.380
<v Sjors Provoost>Oh, I had one more point. So the general... We had an episode before about

00:15:45.380 --> 00:15:49.950
<v Sjors Provoost>an invalid block, episode 76,

00:15:51.750 --> 00:15:53.970
<v Sjors Provoost>which covered the topic of stamps.

00:15:54.190 --> 00:15:54.610
<v Aaron van Wirdum>Oh, right.

00:15:55.910 --> 00:16:01.020
<v Sjors Provoost>But there were two invalid blocks in that episode that we discussed. And the

00:16:01.020 --> 00:16:03.440
<v Sjors Provoost>reason for the invalid block was completely different. They broke a different

00:16:03.440 --> 00:16:07.700
<v Sjors Provoost>rule, and the episode explains that. But the thing that they have in common is

00:16:07.700 --> 00:16:12.240
<v Sjors Provoost>that they were both using some custom software. I believe in the case of the

00:16:12.240 --> 00:16:17.280
<v Sjors Provoost>invalid stamps blocks, they were using Bitcoin Core, but they tweaked Bitcoin

00:16:17.280 --> 00:16:22.320
<v Sjors Provoost>Core, they made changes to it that caused this mistake. Whereas in this case,

00:16:22.500 --> 00:16:26.220
<v Sjors Provoost>they might have been using some completely different piece of software. But the

00:16:26.220 --> 00:16:30.440
<v Sjors Provoost>rule seems to be, the pattern seems to be that if you write your own software to

00:16:30.440 --> 00:16:34.190
<v Sjors Provoost>create blocks, or even to change what Bitcoin Core is doing, you're likely to

00:16:34.190 --> 00:16:38.430
<v Sjors Provoost>make mistakes. There's some really finicky rules out there that you might forget about.

00:16:41.140 --> 00:16:44.500
<v Aaron van Wirdum>The Bitcoin Core developer advises to use Bitcoin Core.

00:16:44.700 --> 00:16:50.200
<v Sjors Provoost>Yes. We have a saying in Dutch. Wij van WC-Eend adviseren WC-Eend.

00:16:50.920 --> 00:16:51.360
<v Aaron van Wirdum>Right.

00:16:52.990 --> 00:16:57.790
<v Aaron van Wirdum>I mean, are you going to even explain that? No, never mind. If you're not Dutch,

00:16:59.310 --> 00:16:59.530
<v Aaron van Wirdum>bad luck.

00:16:59.530 --> 00:17:00.530
<v Sjors Provoost>You would miss this wisdom.

00:17:01.770 --> 00:17:05.550
<v Aaron van Wirdum>All right, I think that covers the invalid block, basically, right?

00:17:05.830 --> 00:17:05.930
<v Sjors Provoost>Yeah.

00:17:06.070 --> 00:17:11.130
<v Aaron van Wirdum>That was a short topic. There was something else. Speaking of older episodes, so

00:17:11.130 --> 00:17:15.740
<v Aaron van Wirdum>this is the other thing I wanted to bring up. Speaking of older episodes, there

00:17:15.740 --> 00:17:20.660
<v Aaron van Wirdum>have been some updates from the Bitcoin Core development front. Namely,

00:17:22.080 --> 00:17:23.700
<v Aaron van Wirdum>peer-to-peer encryption was merged.

00:17:24.020 --> 00:17:26.960
<v Sjors Provoost>Yeah, that's right. It was a productive morning. Two things were merged, and the

00:17:26.960 --> 00:17:32.220
<v Sjors Provoost>first one is peer-to-peer encryption, which is a proposal we talked about in

00:17:32.220 --> 00:17:34.580
<v Sjors Provoost>episode 77, so not even that long ago.

00:17:34.800 --> 00:17:35.080
<v Aaron van Wirdum>Yeah.

00:17:35.300 --> 00:17:40.900
<v Sjors Provoost>The idea has been around for six, seven years, I think, initially

00:17:40.900 --> 00:17:42.320
<v Sjors Provoost>introduced by Jonas Schnelli.

00:17:42.420 --> 00:17:47.010
<v Aaron van Wirdum>Yeah, something like that. Can you give a two-sentence summary for whoever wants

00:17:47.010 --> 00:17:48.090
<v Aaron van Wirdum>to jog their memory?

00:17:48.330 --> 00:17:52.190
<v Sjors Provoost>Yeah, right now nodes talk to each other in plain text, which means your internet

00:17:52.190 --> 00:17:58.040
<v Sjors Provoost>provider or anyone else can listen to exactly what you're doing. In part that

00:17:58.040 --> 00:18:01.990
<v Sjors Provoost>doesn't matter because you know blocks are public information, but in part it

00:18:01.990 --> 00:18:06.450
<v Sjors Provoost>could matter because you might be the one you know you might make a transaction

00:18:06.450 --> 00:18:10.510
<v Sjors Provoost>and then by looking at this how that transaction moves over the network some spy

00:18:10.510 --> 00:18:13.730
<v Sjors Provoost>can tell that the transaction is coming from you and that is not public

00:18:13.730 --> 00:18:17.650
<v Sjors Provoost>information. And it makes censorship easier if you can see what Bitcoin nodes

00:18:17.650 --> 00:18:22.150
<v Sjors Provoost>are. So this proposal encrypts all the traffic between peers. That's basically

00:18:22.150 --> 00:18:24.690
<v Sjors Provoost>it. So anybody observing it can just see noise.

00:18:25.210 --> 00:18:29.430
<v Aaron van Wirdum>Right. So that's merged in Bitcoin Core, which means it will be available in the

00:18:29.430 --> 00:18:32.050
<v Aaron van Wirdum>next Bitcoin Core release. Any idea when that will be?

00:18:32.270 --> 00:18:38.010
<v Sjors Provoost>Probably November. So that'll be release 26. I'm thinking in a few

00:18:38.010 --> 00:18:40.750
<v Sjors Provoost>weeks, maybe in a month, that'll be the first release candidates for people who

00:18:40.750 --> 00:18:43.830
<v Sjors Provoost>are really feeling experimental. I mean, if you're really feeling experimental,

00:18:43.830 --> 00:18:47.430
<v Sjors Provoost>you can compile the master branch. If you're feeling slightly less experimental,

00:18:47.430 --> 00:18:48.910
<v Sjors Provoost>you can wait for the first release candidate.

00:18:50.830 --> 00:18:55.550
<v Sjors Provoost>It's an opt-in feature, so you have to configure V2 Transport, but it will be in

00:18:55.550 --> 00:18:59.830
<v Sjors Provoost>the README. And then one fun thing you can do if you're testing it out is to

00:18:59.830 --> 00:19:04.170
<v Sjors Provoost>check your session ID. So if you connect to somebody you know, normally your node

00:19:04.170 --> 00:19:07.190
<v Sjors Provoost>just connects to random other nodes, but if you do connect to somebody you do

00:19:07.190 --> 00:19:11.810
<v Sjors Provoost>know, you can actually look up the session ID, probably in the GUI, so that's

00:19:11.810 --> 00:19:15.650
<v Sjors Provoost>nice. And then you can call your friend and say, hey, you know, do you see a

00:19:15.650 --> 00:19:19.190
<v Sjors Provoost>connection from my IP address? And do you see what the session ID is? And then

00:19:19.190 --> 00:19:23.190
<v Sjors Provoost>they should be the same. Very much like in Signal and WhatsApp, where you can

00:19:23.190 --> 00:19:24.370
<v Sjors Provoost>compare this identifier.

00:19:24.730 --> 00:19:25.010
<v Aaron van Wirdum>Right.

00:19:25.310 --> 00:19:27.230
<v Sjors Provoost>And that tells you that there's nobody in the middle.

00:19:27.790 --> 00:19:32.900
<v Aaron van Wirdum>Right. Anyways, this is all explained in detail in episode 77. Yep. And there was

00:19:32.900 --> 00:19:35.920
<v Aaron van Wirdum>something else. What else was merged? There was another big merge you mentioned.

00:19:36.080 --> 00:19:37.560
<v Sjors Provoost>That's right. AssumeUTXO.

00:19:38.540 --> 00:19:39.320
<v Aaron van Wirdum>Right. Okay.

00:19:39.440 --> 00:19:40.920
<v Sjors Provoost>For Testnet and for Signet.

00:19:41.390 --> 00:19:46.650
<v Aaron van Wirdum>Okay, so that's not on mainnet yet, but, but the core—sorry, the code is in

00:19:46.650 --> 00:19:47.590
<v Aaron van Wirdum>Bitcoin Core now.

00:19:47.830 --> 00:19:51.610
<v Sjors Provoost>Yes, and if you do want to test it in mainnet, you can. There's a pull request,

00:19:51.710 --> 00:19:52.830
<v Sjors Provoost>but you have to compile it yourself.

00:19:53.920 --> 00:19:58.020
<v Aaron van Wirdum>So why is it not available for mainnet yet? What's the reasoning there?

00:19:58.120 --> 00:20:03.880
<v Sjors Provoost>Because it's not ready enough, I guess. I think it still needs some testing. The

00:20:03.880 --> 00:20:08.520
<v Sjors Provoost>other thing is that these parameters that are in the source code now for testnet

00:20:08.520 --> 00:20:12.850
<v Sjors Provoost>and for signet... they really should be verified by users. So very much like

00:20:12.850 --> 00:20:13.750
<v Sjors Provoost>assumevalid.

00:20:14.970 --> 00:20:18.610
<v Sjors Provoost>We talked about that in some other episode. I think in the AssumeUTXO episode,

00:20:18.950 --> 00:20:21.170
<v Sjors Provoost>which is episode number 14.

00:20:22.150 --> 00:20:25.130
<v Aaron van Wirdum>Right, yeah. So the thing we're talking about now, episode 14,

00:20:25.080 --> 00:20:27.010
<v Aaron van Wirdum>if you know—yeah, if you want to know more about that.

00:20:26.300 --> 00:20:28.970
<v Sjors Provoost>It's one of the first ones we did. Exactly, in 2020.

00:20:30.550 --> 00:20:33.670
<v Sjors Provoost>Basically, there's a hash that goes into the source code, which represents the

00:20:33.670 --> 00:20:38.690
<v Sjors Provoost>UTXO set for AssumeUTXO. And so somebody, or lots of people really, should check

00:20:38.690 --> 00:20:42.570
<v Sjors Provoost>that hash. And for Testnet and signet, it doesn't really matter. Nobody really

00:20:42.570 --> 00:20:45.670
<v Sjors Provoost>checked the hash, but it's just Testnet and signet. But for Mainnet, you probably

00:20:45.670 --> 00:20:48.870
<v Sjors Provoost>want to have a whole bunch of people check that. So that's one of the reasons why

00:20:48.870 --> 00:20:53.230
<v Sjors Provoost>that was delayed a bit. And then also because it still needs a bit more testing,

00:20:53.350 --> 00:20:57.630
<v Sjors Provoost>I think, that feature. So the baby steps here are you just put all the code

00:20:57.630 --> 00:21:00.990
<v Sjors Provoost>inside Bitcoin Core and you turn it on for Testnet for people who want to try it.

00:21:01.720 --> 00:21:04.880
<v Sjors Provoost>And then if people don't find problems, I guess eventually we'll turn it on for

00:21:04.880 --> 00:21:08.700
<v Sjors Provoost>Mainnet. It's still an opt-in feature regardless.

00:21:09.730 --> 00:21:10.250
<v Aaron van Wirdum>Right.

00:21:11.450 --> 00:21:15.550
<v Aaron van Wirdum>Okay. So that's also merged in Bitcoin Core. So we'll, well, I guess for testnet

00:21:15.550 --> 00:21:19.530
<v Aaron van Wirdum>will be available also in Bitcoin Core 26 in November.

00:21:19.830 --> 00:21:19.970
<v Sjors Provoost>Yep.

00:21:20.590 --> 00:21:25.310
<v Aaron van Wirdum>I think that pretty much covers the episode. One thing I thought of sort of

00:21:25.310 --> 00:21:29.470
<v Aaron van Wirdum>during halfway and I didn't want to bring it up immediately. Just to be clear, I

00:21:29.470 --> 00:21:33.230
<v Aaron van Wirdum>actually do still work with Bitcoin Magazine. There's no bad blood or anything

00:21:33.230 --> 00:21:38.010
<v Aaron van Wirdum>like that in case anyone got that impression. It's just a podcast. It's now an

00:21:38.010 --> 00:21:38.630
<v Aaron van Wirdum>independent thing.

00:21:38.930 --> 00:21:41.530
<v Sjors Provoost>Yeah. Oh, I also had another thing. News items.

00:21:41.530 --> 00:21:42.210
<v Aaron van Wirdum>Even more news.

00:21:42.390 --> 00:21:46.190
<v Sjors Provoost>Yeah, yeah. So I recently got a grant from the OpenSats Foundation to keep

00:21:46.190 --> 00:21:48.650
<v Sjors Provoost>working on Bitcoin Core. So that's really nice.

00:21:48.810 --> 00:21:49.270
<v Aaron van Wirdum>Congratulations on that.

00:21:49.450 --> 00:21:49.750
<v Sjors Provoost>Thank you.

00:21:51.150 --> 00:21:55.990
<v Aaron van Wirdum>Does that cover it, Sjors? Is that that we update all our listeners on everything

00:21:55.990 --> 00:21:57.030
<v Aaron van Wirdum>they need to know for now?

00:21:57.210 --> 00:21:58.730
<v Sjors Provoost>I think so. Thank you for listening.

00:21:58.730 --> 00:22:01.530
<v Aaron van Wirdum>And then the next episode will be in a few weeks.

00:22:01.790 --> 00:22:03.190
<v Sjors Provoost>Will be when the next episode lands.

00:22:03.350 --> 00:22:03.510
<v Aaron van Wirdum>Right.

00:22:03.970 --> 00:22:05.290
<v Sjors Provoost>Thank you for listening to Bitcoin

00:22:05.290 --> 00:22:06.150
<v Aaron van Wirdum>Explained.

