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

00:00:20.750 --> 00:00:23.010
<v Aaron van Wirdum>Live from Utrecht, this is Bitcoin.

00:00:23.890 --> 00:00:24.330
<v Sjors Provoost>Explained.

00:00:25.050 --> 00:00:28.430
<v Aaron van Wirdum>Sjors, why is Bitcoin Core 24 not released yet?

00:00:28.970 --> 00:00:30.010
<v Sjors Provoost>It's almost released.

00:00:30.250 --> 00:00:31.150
<v Aaron van Wirdum>What are we waiting for?

00:00:31.330 --> 00:00:35.690
<v Sjors Provoost>But there was a bit of a snafu. There was a bit of discussion about SBX, I mean

00:00:35.690 --> 00:00:36.250
<v Sjors Provoost>RBF.

00:00:36.450 --> 00:00:36.770
<v Aaron van Wirdum>Aha!

00:00:40.910 --> 00:00:42.870
<v Aaron van Wirdum>The discussion about Replace by fee.

00:00:43.230 --> 00:00:43.870
<v Sjors Provoost>That's right.

00:00:44.070 --> 00:00:47.350
<v Aaron van Wirdum>Oh, it's such a coincidence you bring that up, because that's what we're going to

00:00:47.350 --> 00:00:48.650
<v Aaron van Wirdum>discuss in this episode, Sjors.

00:00:48.950 --> 00:00:50.510
<v Sjors Provoost>Exactly, I thought so.

00:00:51.030 --> 00:00:56.600
<v Aaron van Wirdum>So yeah, there's been a long discussion about RBF. It's not the first time, but

00:00:56.600 --> 00:01:02.240
<v Aaron van Wirdum>it definitely resurfaced now that Bitcoin Core 24 is coming up because there

00:01:02.240 --> 00:01:07.820
<v Aaron van Wirdum>is a new feature included in Bitcoin Core 24, as we explained in our episode

00:01:07.820 --> 00:01:11.480
<v Aaron van Wirdum>about Bitcoin Core 24, which was two episodes ago.

00:01:12.000 --> 00:01:12.520
<v Sjors Provoost>Yep.

00:01:12.840 --> 00:01:15.520
<v Aaron van Wirdum>Episode 60, no, three ago, I think.

00:01:15.680 --> 00:01:16.880
<v Sjors Provoost>Could be several episodes ago.

00:01:17.240 --> 00:01:18.200
<v Aaron van Wirdum>A couple episodes ago.

00:01:18.400 --> 00:01:23.360
<v Sjors Provoost>So we talked about how fast release candidates usually go through. And this time

00:01:23.360 --> 00:01:26.880
<v Sjors Provoost>it took longer. And the reason it took longer is because this feature was in there.

00:01:27.260 --> 00:01:32.180
<v Aaron van Wirdum>Right. Well, this is the first time I think that a Bitcoin Core release candidate

00:01:32.180 --> 00:01:36.880
<v Aaron van Wirdum>has been delayed because of a feature, I think, right? Because usually it's to

00:01:36.880 --> 00:01:41.580
<v Aaron van Wirdum>find bugs. But this time this was like explicitly meant to be in there. But then

00:01:41.580 --> 00:01:44.060
<v Aaron van Wirdum>discussion happened whether that was actually desirable.

00:01:44.400 --> 00:01:47.620
<v Sjors Provoost>I don't know if it's the first time. It's definitely the first time I remember

00:01:47.620 --> 00:01:50.520
<v Sjors Provoost>that there was a lot of discussion about whether something should or should not

00:01:50.520 --> 00:01:51.560
<v Sjors Provoost>be in the next release.

00:01:52.030 --> 00:01:54.330
<v Aaron van Wirdum>After it was included in a release candidate.

00:01:54.650 --> 00:01:59.550
<v Sjors Provoost>Yeah, typically you want the release process to be pretty boring. So there is a

00:01:59.550 --> 00:02:03.290
<v Sjors Provoost>release candidate, people look for bugs, and then there's another release

00:02:03.290 --> 00:02:07.530
<v Sjors Provoost>candidate and people look for more bugs. But this can happen if there's a feature

00:02:07.530 --> 00:02:10.770
<v Sjors Provoost>in there that's controversial. Then you can have discussion over it just means

00:02:10.770 --> 00:02:12.370
<v Sjors Provoost>that it's not going to be a release for a while.

00:02:12.370 --> 00:02:17.030
<v Aaron van Wirdum>And by the way, I'll claim my… I was right this time. I'm not sure did I mention

00:02:17.030 --> 00:02:20.650
<v Aaron van Wirdum>it in the episode? I definitely mentioned it before the episode. I told you this

00:02:20.650 --> 00:02:25.670
<v Aaron van Wirdum>is going to be an issue, and then you said no it's fine and I said no this is

00:02:25.670 --> 00:02:29.730
<v Aaron van Wirdum>going to be an issue and now it became a huge issue. Sure. I was right about this one.

00:02:29.730 --> 00:02:31.730
<v Sjors Provoost>You may have been, I don't remember.

00:02:31.730 --> 00:02:37.160
<v Aaron van Wirdum>I definitely I remember very well. Anyway, so it's Sjors, what's the feature?

00:02:37.160 --> 00:02:43.160
<v Sjors Provoost>The feature it's called mempoolfullrbf it's a setting. And this

00:02:43.160 --> 00:02:49.000
<v Sjors Provoost>setting what it does is instead of when you have transactions that signal

00:02:49.000 --> 00:02:54.800
<v Sjors Provoost>replaced by fee you will accept those transactions, if they pay a higher fee and

00:02:54.800 --> 00:03:00.020
<v Sjors Provoost>if they obey some other rules that were specified in BIP 125, and if you turn on

00:03:00.020 --> 00:03:05.780
<v Sjors Provoost>this particular setting then any transaction that does not signal this

00:03:05.780 --> 00:03:11.120
<v Sjors Provoost>flag, but does comply with all the other rules from BIP 125 will get replaced. So

00:03:11.120 --> 00:03:16.120
<v Sjors Provoost>the word full is a bit misleading. It's definitely more RBF, but it's, there's

00:03:16.120 --> 00:03:19.200
<v Sjors Provoost>still rules. You can't just replace any transaction with any other transaction.

00:03:19.890 --> 00:03:21.670
<v Sjors Provoost>There's still some rules to apply there.

00:03:21.910 --> 00:03:26.490
<v Aaron van Wirdum>Yeah, we made a whole episode on replace by fee, RBF. So we're not going to

00:03:26.490 --> 00:03:32.310
<v Aaron van Wirdum>repeat what it is exactly. But very briefly, you can replace a transaction if you

00:03:32.310 --> 00:03:35.010
<v Aaron van Wirdum>include a higher fee, right? That's essentially what it means.

00:03:35.110 --> 00:03:39.450
<v Sjors Provoost>It has to pay a higher absolute fee. It has to pay a higher fee rate and a few

00:03:39.450 --> 00:03:41.890
<v Sjors Provoost>other conditions. Yeah, we've explained it in episode 26.

00:03:43.680 --> 00:03:48.080
<v Aaron van Wirdum>Right. So usually it's already possible. Now you include a flag in a transaction

00:03:48.080 --> 00:03:52.040
<v Aaron van Wirdum>where you basically tell the network, look, I might want to replace this later.

00:03:52.880 --> 00:03:58.640
<v Aaron van Wirdum>And to be clear, technically a miner can always replace a

00:03:58.640 --> 00:04:02.420
<v Aaron van Wirdum>transaction, right? But it's just with this flag, you make it very explicit and

00:04:02.420 --> 00:04:04.560
<v Aaron van Wirdum>then nodes will also forward it to other nodes.

00:04:04.960 --> 00:04:08.020
<v Sjors Provoost>But that's the main thing this setting does. It's about what it forwards and what

00:04:08.020 --> 00:04:12.110
<v Sjors Provoost>it doesn't forward. So if you have a direct connection to a miner, then... That

00:04:12.110 --> 00:04:15.890
<v Sjors Provoost>miner can do whatever it wants because this is not a consensus rule. Right and in

00:04:15.890 --> 00:04:19.850
<v Sjors Provoost>fact there's already a bunch of nodes out there on the network that run maybe a

00:04:19.850 --> 00:04:23.910
<v Sjors Provoost>version of Bitcoin Knots or some other patch that already have this setting in

00:04:23.910 --> 00:04:28.830
<v Sjors Provoost>there so it's not really a new feature but it is new that that it's available in

00:04:28.830 --> 00:04:31.530
<v Sjors Provoost>Bitcoin Core. It's off by default right?

00:04:31.530 --> 00:04:36.270
<v Aaron van Wirdum>Yeah. So now it's a new option in Bitcoin Core and it's off by default how do you

00:04:36.270 --> 00:04:36.810
<v Aaron van Wirdum>switch it on?

00:04:38.190 --> 00:04:42.150
<v Sjors Provoost>You put a setting in your config file called mempoolfullrbf

00:04:42.690 --> 00:04:48.650
<v Aaron van Wirdum>Okay that's it so what are we gonna do in this episode, Sjors I think I know

00:04:48.650 --> 00:04:52.850
<v Aaron van Wirdum>we're gonna discuss what the more recent discussion has been about more or less.

00:04:52.850 --> 00:04:57.570
<v Sjors Provoost>Yeah I think we're gonna try and not rehash the entire RBF discussion that's been

00:04:57.570 --> 00:05:01.470
<v Sjors Provoost>had historically but maybe try to focus on the things that were new in that

00:05:01.470 --> 00:05:03.710
<v Sjors Provoost>discussion but we'll probably get to some old stuff too.

00:05:04.260 --> 00:05:10.080
<v Aaron van Wirdum>Yeah. And also, so this is one of these debates where there are

00:05:10.080 --> 00:05:15.800
<v Aaron van Wirdum>kind of several arguments on both sides. And then all

00:05:16.190 --> 00:05:20.800
<v Aaron van Wirdum>of these arguments have... Counter arguments and then these counter arguments

00:05:20.800 --> 00:05:25.080
<v Aaron van Wirdum>have counter counter arguments and then these counter counter arguments have like

00:05:25.080 --> 00:05:26.100
<v Aaron van Wirdum>sub arguments.

00:05:26.100 --> 00:05:31.600
<v Sjors Provoost>And also there's just six six or seven whatever, lines of argument that go in

00:05:31.600 --> 00:05:35.820
<v Sjors Provoost>parallel right? So, you can talk about very different aspects of this feature and

00:05:35.820 --> 00:05:38.000
<v Sjors Provoost>also of this discussion which we'll get to.

00:05:38.000 --> 00:05:42.720
<v Aaron van Wirdum>Yeah there's like all of the sub arguments and counter counter arguments like

00:05:42.720 --> 00:05:46.950
<v Aaron van Wirdum>there's also… they… can all be summarized by like a meta argument. And there's

00:05:46.950 --> 00:05:51.090
<v Aaron van Wirdum>there's a lot of sides to this discussion, and I don't we're definitely gonna

00:05:51.090 --> 00:05:56.810
<v Aaron van Wirdum>forget or miss some of them but hopefully we'll get the most important ones at

00:05:56.810 --> 00:06:02.690
<v Aaron van Wirdum>least during this episode. Either case we'll do our best. Sure, where do we

00:06:02.690 --> 00:06:06.350
<v Aaron van Wirdum>start? Why was it included? Let's start there. Why was this feature included in

00:06:06.350 --> 00:06:07.350
<v Aaron van Wirdum>this version of Bitcoin Core?

00:06:08.590 --> 00:06:10.430
<v Aaron van Wirdum>What was the original argument?

00:06:10.650 --> 00:06:15.130
<v Sjors Provoost>Because there was a pull request. But yeah, basically there was a pull request

00:06:15.130 --> 00:06:20.870
<v Sjors Provoost>that argued that there are certain annoying pinning attacks, which I guess we'll

00:06:20.870 --> 00:06:26.130
<v Sjors Provoost>try to explain, in Lightning and other protocols that are multi-party. So these

00:06:26.130 --> 00:06:28.750
<v Sjors Provoost>could be vaults or even CoinJoins perhaps.

00:06:29.370 --> 00:06:31.230
<v Aaron van Wirdum>Yeah, sort of smart contract-y kind of stuff.

00:06:31.490 --> 00:06:35.730
<v Sjors Provoost>And basically these protocols are being, the argument was these protocols are

00:06:35.730 --> 00:06:41.450
<v Sjors Provoost>being burdened by some of the details of the RBF rules. And

00:06:41.450 --> 00:06:47.170
<v Sjors Provoost>one way to reduce those burdens at least is to have this new full

00:06:47.170 --> 00:06:49.910
<v Sjors Provoost>RBF option. That was the argument.

00:06:50.210 --> 00:06:52.010
<v Aaron van Wirdum>Okay, hang on. What's a pinning attack?

00:06:52.720 --> 00:06:57.080
<v Sjors Provoost>Well, this is where things get really complicated. And this complexity is

00:06:57.080 --> 00:07:00.600
<v Sjors Provoost>something we'll get back to because we are not the only ones who don't fully

00:07:00.600 --> 00:07:06.470
<v Sjors Provoost>understand these things. But basically... What happens is if you want to replace

00:07:06.470 --> 00:07:11.110
<v Sjors Provoost>a transaction, you have to obey certain rules. And just the simplest rule of that

00:07:11.110 --> 00:07:16.470
<v Sjors Provoost>is I think the new replacements can only be 25 transactions.

00:07:16.870 --> 00:07:21.750
<v Sjors Provoost>Maybe it's 100. I don't know the number. But that could be the rule. So now if

00:07:21.750 --> 00:07:22.590
<v Sjors Provoost>you have a situation...

00:07:22.590 --> 00:07:23.570
<v Aaron van Wirdum>I think it's 100, by the way.

00:07:23.710 --> 00:07:28.330
<v Sjors Provoost>Could be 100. So now let's say there's a situation where I, the attacker, have

00:07:28.330 --> 00:07:33.850
<v Sjors Provoost>created 101 transactions, that are designed to annoy my victim somehow and the

00:07:33.850 --> 00:07:38.870
<v Sjors Provoost>victim wants to replace those by paying a higher fee but unfortunately the victim

00:07:38.870 --> 00:07:44.380
<v Sjors Provoost>cannot replace 101 transactions because you can't replace more than so the victim

00:07:44.380 --> 00:07:49.300
<v Sjors Provoost>cannot replace 101 transactions because they can only replace 100 transactions so

00:07:49.300 --> 00:07:52.780
<v Sjors Provoost>that class of attack where the victim cannot replace even though they might have

00:07:52.780 --> 00:07:56.280
<v Sjors Provoost>the fees is called a pinning attack and other things that you can do is

00:07:56.280 --> 00:08:01.420
<v Aaron van Wirdum>Let's say this is a very specific example of one particular pinning attack then I

00:08:01.420 --> 00:08:02.420
<v Aaron van Wirdum>I would assume right?

00:08:02.420 --> 00:08:06.060
<v Sjors Provoost>Yeah the there's all sorts of ways that you're essentially you're pinning a

00:08:06.060 --> 00:08:08.940
<v Sjors Provoost>transaction that you want as the attacker you're pinning that into the mempool

00:08:08.940 --> 00:08:11.820
<v Sjors Provoost>making it hard to unpin it I guess.

00:08:11.820 --> 00:08:17.080
<v Aaron van Wirdum>Right so then in that case, yeah as the attacker you wouldn't add the RBF flag

00:08:17.080 --> 00:08:22.200
<v Aaron van Wirdum>obviously because you're trying to do it to annoy someone, but then if full RBF

00:08:22.200 --> 00:08:22.680
<v Aaron van Wirdum>would be…

00:08:23.170 --> 00:08:27.870
<v Sjors Provoost>Or you do. I mean, for the example I just gave, with 101 transactions, you can

00:08:27.870 --> 00:08:33.110
<v Sjors Provoost>mark them RBF, but when somebody then tries to replace it, they still cannot

00:08:33.110 --> 00:08:36.990
<v Sjors Provoost>replace it because one of the rules is no more than 100 transactions.

00:08:37.290 --> 00:08:41.890
<v Aaron van Wirdum>Right, but in that case, the full RBF rule would not fix this.

00:08:41.990 --> 00:08:46.770
<v Sjors Provoost>No. But there's other attacks where you can turn RBF off as an attacker. So the

00:08:46.770 --> 00:08:52.050
<v Sjors Provoost>official specification of RBF, of opt-in RBF, says that... If your parent

00:08:52.050 --> 00:08:57.050
<v Sjors Provoost>transaction is RBF, then your child transaction should also be RBF. But that's

00:08:57.050 --> 00:09:02.350
<v Sjors Provoost>not being checked, that rule. So now it's possible to create a transaction and

00:09:02.350 --> 00:09:07.570
<v Sjors Provoost>then the attacker would put a non-RBF transaction on top of the RBF transaction

00:09:07.570 --> 00:09:12.050
<v Sjors Provoost>and then you can't replace that anymore because the second transaction does not

00:09:12.050 --> 00:09:12.830
<v Sjors Provoost>signal RBF.

00:09:14.120 --> 00:09:17.880
<v Sjors Provoost>And that one might be fixable with this change, right? Because then it doesn't

00:09:17.880 --> 00:09:21.240
<v Sjors Provoost>matter whether or not the transaction is RBF as long as it obeys the other rules.

00:09:22.440 --> 00:09:28.360
<v Aaron van Wirdum>Right. So in that case, it actually sounds like the problem with full RBF...

00:09:28.360 --> 00:09:30.000
<v Aaron van Wirdum>Wait, let me rephrase that.

00:09:30.120 --> 00:09:30.940
<v Sjors Provoost>Opt-in RBF?

00:09:32.720 --> 00:09:38.680
<v Aaron van Wirdum>I was going to say, yeah, the problem... Whatever problem we're talking

00:09:38.680 --> 00:09:44.670
<v Aaron van Wirdum>about here can be solved with... The problem with full RBF in this case is that

00:09:44.670 --> 00:09:50.280
<v Aaron van Wirdum>it's not RBF enough. Like there's still limitations to what you can replace.

00:09:50.800 --> 00:09:55.320
<v Sjors Provoost>Yeah, so in the second example I gave, you could actually, full RBF would be a

00:09:55.320 --> 00:10:01.220
<v Sjors Provoost>solution for that problem. Because, right, so the attack would be you put

00:10:01.220 --> 00:10:05.960
<v Sjors Provoost>a transaction that doesn't signal RBF on top of a transaction that does signal

00:10:05.960 --> 00:10:11.760
<v Sjors Provoost>RBF. Now this new transaction is unreplaceable. But if you have

00:10:11.760 --> 00:10:15.880
<v Sjors Provoost>full RBF then it doesn't matter that the that the second transaction doesn't

00:10:15.880 --> 00:10:19.780
<v Sjors Provoost>signal RBF it's going to be treated the same anyway so now you can replace that

00:10:19.780 --> 00:10:23.360
<v Sjors Provoost>one so there's some things that you can you can fix with full RBF but the example

00:10:23.360 --> 00:10:27.880
<v Sjors Provoost>of 101 transactions you cannot fix with full RBF because RBF has other rules.

00:10:27.880 --> 00:10:33.740
<v Aaron van Wirdum>Yeah okay well let's not dwell on this enough let's just establish that some

00:10:33.740 --> 00:10:39.080
<v Aaron van Wirdum>types of smart contract-y kind of things on Bitcoin would benefit from

00:10:39.650 --> 00:10:45.610
<v Aaron van Wirdum>full RBF or at least they would benefit from maximum RBF which is the term used

00:10:45.610 --> 00:10:50.550
<v Aaron van Wirdum>for even fuller than full RBF where yeah really any transaction that has

00:10:50.550 --> 00:10:53.130
<v Aaron van Wirdum>higher fees would be replaced without any other rules.

00:10:53.130 --> 00:10:56.790
<v Sjors Provoost>This this term may have been coined by Suhas Daftuar I think his last name is…

00:10:56.790 --> 00:11:02.690
<v Sjors Provoost>Maximal RBF would be like if miners only cared about their financial

00:11:02.690 --> 00:11:06.170
<v Sjors Provoost>incentives that would be you know they would replace things in a certain way but

00:11:06.170 --> 00:11:09.550
<v Sjors Provoost>it's actually not that trivial to to really think that. And there's trade-offs

00:11:09.550 --> 00:11:11.130
<v Sjors Provoost>there when it comes to...

00:11:11.130 --> 00:11:16.650
<v Aaron van Wirdum>Sure. Well, where I was getting at was, so let's sort of move past this

00:11:16.650 --> 00:11:21.570
<v Aaron van Wirdum>complex smart contract stuff and how it can be attacked exactly. And we'll assume

00:11:21.570 --> 00:11:26.070
<v Aaron van Wirdum>that RBF helps because that is at least what Lightning developers think.

00:11:26.150 --> 00:11:30.010
<v Sjors Provoost>Well, this is where part of the confusion started coming from. So basically from

00:11:30.010 --> 00:11:35.210
<v Sjors Provoost>a Bitcoin Core point of view, there is a pull request with somebody saying...

00:11:35.790 --> 00:11:41.390
<v Sjors Provoost>Well, let's enable full RBF because it makes these pinning attacks less bad,

00:11:41.550 --> 00:11:45.090
<v Sjors Provoost>and then it links to a bunch of mailing list posts that contain very long stories

00:11:45.090 --> 00:11:48.610
<v Sjors Provoost>about very complicated pinning attacks in Lightning that nobody outside of

00:11:48.610 --> 00:11:53.390
<v Sjors Provoost>Lightning understands. So now, as a Bitcoin Core reviewer, you're looking at that

00:11:53.390 --> 00:11:58.410
<v Sjors Provoost>pull request, and you're like, hmm, do I really want to read 15,000 pages of

00:11:58.410 --> 00:12:03.130
<v Sjors Provoost>Lightning mailing list posts to decide whether this feature is good or not? You

00:12:03.130 --> 00:12:06.050
<v Sjors Provoost>might decide not to read those mailing list posts and just assume that they know

00:12:06.050 --> 00:12:10.390
<v Sjors Provoost>what they're talking about. And then you focus on other aspects of the

00:12:10.390 --> 00:12:12.210
<v Sjors Provoost>discussion, but not that specific one.

00:12:12.730 --> 00:12:16.190
<v Aaron van Wirdum>Well, it is interesting you mention that because that is something that came up.

00:12:16.770 --> 00:12:22.250
<v Aaron van Wirdum>In our last episode right with some where I mentioned or we mentioned that sort

00:12:22.250 --> 00:12:25.530
<v Aaron van Wirdum>of Bitcoin development and Lightning development is kind of diverging a bit it

00:12:25.530 --> 00:12:30.670
<v Aaron van Wirdum>seems yeah people that are interested in one or the other rather than both that

00:12:30.670 --> 00:12:34.050
<v Aaron van Wirdum>sort of growing apart a little bit it seems sometimes so this would be an example

00:12:34.050 --> 00:12:38.390
<v Aaron van Wirdum>of that where okay the Lightning devs say that this would actually benefit their

00:12:38.390 --> 00:12:42.510
<v Aaron van Wirdum>protocol and then what you're saying is that a Bitcoin Core developer might

00:12:42.510 --> 00:12:44.820
<v Aaron van Wirdum>think: All right, I believe you.

00:12:45.580 --> 00:12:48.960
<v Sjors Provoost>Right. Well, in this case, those Lightning developers probably do understand the

00:12:48.960 --> 00:12:52.260
<v Sjors Provoost>Bitcoin Core side of things on this aspect. But most of the Bitcoin Core

00:12:52.260 --> 00:12:54.460
<v Sjors Provoost>developers will not understand the Lightning side of things.

00:12:54.740 --> 00:12:54.980
<v Aaron van Wirdum>Right.

00:12:55.180 --> 00:12:58.860
<v Sjors Provoost>So it's a bit asymmetrical. So there's a little bit of trust there. So then

00:12:58.860 --> 00:13:03.900
<v Sjors Provoost>there's still other reasons why you may want to or may not want to merge these

00:13:03.900 --> 00:13:09.730
<v Sjors Provoost>things. One of the things that came back in a discussion now recently was… well

00:13:09.730 --> 00:13:14.290
<v Sjors Provoost>these pinning attacks are not really solved. So then should that pull request

00:13:14.290 --> 00:13:16.910
<v Sjors Provoost>have been merged in the first place given that it didn't really solve anything

00:13:16.910 --> 00:13:20.090
<v Sjors Provoost>and it did piss off other people. So

00:13:21.340 --> 00:13:23.120
<v Sjors Provoost>that's I guess we can get to that.

00:13:23.120 --> 00:13:29.120
<v Aaron van Wirdum>Yeah well okay so so I was gonna go one

00:13:29.120 --> 00:13:34.870
<v Aaron van Wirdum>step at a time. So first of all at least it seems that full RBF

00:13:34.870 --> 00:13:39.790
<v Aaron van Wirdum>would solve a problem for Lightning whether or not that is really the case we can

00:13:39.790 --> 00:13:45.090
<v Aaron van Wirdum>sort of park for now but that was at least the initial assumption. Yeah and then

00:13:45.090 --> 00:13:50.910
<v Aaron van Wirdum>I think the second big assumption or that's not even an assumption maybe but

00:13:50.910 --> 00:13:56.480
<v Aaron van Wirdum>is that full RBF is incentive compatible

00:13:56.480 --> 00:14:01.500
<v Aaron van Wirdum>at least if you look at if you assume that miners want to maximize profits

00:14:01.500 --> 00:14:01.980
<v Aaron van Wirdum>they'll

00:14:03.420 --> 00:14:09.440
<v Aaron van Wirdum>in the long term anyways, include whatever fees earn them the most money, right?

00:14:09.760 --> 00:14:14.100
<v Sjors Provoost>That's the argument. Yeah, it's more incentive compatible because it doesn't

00:14:14.100 --> 00:14:18.260
<v Sjors Provoost>require miners to not mine something that would make them more money in the short run.

00:14:18.480 --> 00:14:22.200
<v Aaron van Wirdum>Yeah, so as a Bitcoin Core developer, you're hearing from Lightning developers

00:14:22.200 --> 00:14:25.200
<v Aaron van Wirdum>that this would help them. And then you're looking at the incentives and you

00:14:25.200 --> 00:14:29.420
<v Aaron van Wirdum>figure, well, it's also incentive compatible, at least on the long run. So let's

00:14:29.420 --> 00:14:31.920
<v Aaron van Wirdum>include it. That's kind of...

00:14:32.110 --> 00:14:34.050
<v Sjors Provoost>I think that was most of the discussion. Yeah.

00:14:34.590 --> 00:14:36.670
<v Aaron van Wirdum>Most of the argument for including it anyways.

00:14:37.010 --> 00:14:37.150
<v Sjors Provoost>Yeah.

00:14:37.570 --> 00:14:38.050
<v Aaron van Wirdum>Right. Okay.

00:14:40.090 --> 00:14:43.670
<v Aaron van Wirdum>Does that include, so have we covered the reasons to include it? We didn't miss

00:14:43.670 --> 00:14:44.350
<v Aaron van Wirdum>anything here, right?

00:14:44.510 --> 00:14:47.190
<v Sjors Provoost>We may have missed something, but I think those were the two, the two main

00:14:47.190 --> 00:14:47.730
<v Sjors Provoost>things. Yeah.

00:14:47.930 --> 00:14:52.910
<v Aaron van Wirdum>Yeah. I guess you could maybe argue that a third argument. So the third argument

00:14:52.910 --> 00:14:56.770
<v Aaron van Wirdum>is maybe more about timing. So this became part of the discussion. Like even if

00:14:56.770 --> 00:15:02.690
<v Aaron van Wirdum>everyone agrees that long-term RBF is incentive compatible and therefore probably

00:15:02.690 --> 00:15:07.390
<v Aaron van Wirdum>unavoidable, you can still ask the question, should it be included now? Should it

00:15:07.390 --> 00:15:13.310
<v Aaron van Wirdum>be phased in? Should it be announced that it's going to be the default in

00:15:13.310 --> 00:15:19.090
<v Aaron van Wirdum>a year from now? How do you make the transition from not having it in Bitcoin

00:15:19.090 --> 00:15:22.190
<v Aaron van Wirdum>Core at all to having it in Bitcoin Core?

00:15:23.470 --> 00:15:28.140
<v Sjors Provoost>I think that discussion did not happen in the original pull request. And that's

00:15:28.140 --> 00:15:33.000
<v Sjors Provoost>kind of what flared up afterwards once people found out that this pull request

00:15:33.000 --> 00:15:36.220
<v Sjors Provoost>existed. Because, you know, just because a couple of people in Bitcoin Core

00:15:36.220 --> 00:15:40.860
<v Sjors Provoost>decide to merge something doesn't mean that the entire Bitcoin ecosystem knows

00:15:40.860 --> 00:15:44.160
<v Sjors Provoost>that this happened. It can take a while. It took several months, in fact, for

00:15:44.160 --> 00:15:48.940
<v Sjors Provoost>some people to find out who, basically people who rely heavily on zero

00:15:48.940 --> 00:15:54.000
<v Sjors Provoost>confirmation transactions and who knew this time was coming at some point, but,

00:15:54.100 --> 00:15:56.440
<v Sjors Provoost>you know, they may not expected it to be now.

00:15:59.760 --> 00:16:05.100
<v Aaron van Wirdum>All right so why did why did the discussion originally flare up like what was the

00:16:05.100 --> 00:16:08.000
<v Aaron van Wirdum>original argument against what we just laid out?

00:16:08.000 --> 00:16:13.180
<v Sjors Provoost>So there are companies that rely on zero confirmation transactions. Yeah.

00:16:13.660 --> 00:16:18.980
<v Aaron van Wirdum>Well I was specifically so I think it flared up, it started with Muun the

00:16:18.980 --> 00:16:24.700
<v Aaron van Wirdum>Lightning wallet or apparently not exactly a Lightning wallet… they first

00:16:24.700 --> 00:16:30.690
<v Aaron van Wirdum>made the case that Maybe not right now anyways. And do

00:16:30.690 --> 00:16:31.770
<v Aaron van Wirdum>you know the argument there?

00:16:32.030 --> 00:16:34.870
<v Sjors Provoost>Yeah, so my understanding of the argument, because I was not on the mailing list

00:16:34.870 --> 00:16:35.950
<v Sjors Provoost>when that flared up.

00:16:36.590 --> 00:16:37.190
<v Aaron van Wirdum>How were you?

00:16:37.850 --> 00:16:41.430
<v Sjors Provoost>Well, I was on the mailing list, but the mailing list sits in a mailing list

00:16:41.430 --> 00:16:45.670
<v Sjors Provoost>folder on my computer, which I check once every three months or so. So I may be

00:16:45.670 --> 00:16:48.510
<v Sjors Provoost>behind on some of the drama. But basically, my understanding of the argument is

00:16:48.510 --> 00:16:54.130
<v Sjors Provoost>that Muun Wallet, or Muun Wallet, I guess, the way they handle Lightning is that

00:16:54.130 --> 00:17:00.070
<v Sjors Provoost>the user sends an… sends a on-chain transaction to the Muun server and then

00:17:00.070 --> 00:17:04.810
<v Sjors Provoost>they send a Lightning transaction to the final destination and That itself might

00:17:04.810 --> 00:17:08.830
<v Sjors Provoost>be fine except that they're using an unconfirmed transaction for this in order to

00:17:08.830 --> 00:17:13.570
<v Sjors Provoost>make it fast. So the risk there for the company is that users will make a

00:17:13.570 --> 00:17:18.370
<v Sjors Provoost>unconfirmed transaction to the Muun server the Muun server then sends the actual

00:17:18.370 --> 00:17:21.490
<v Sjors Provoost>Lightning payment that is irreversible to the final destination and then the user

00:17:21.490 --> 00:17:24.770
<v Sjors Provoost>simply undoes the transaction and double spends the server.

00:17:24.770 --> 00:17:28.770
<v Aaron van Wirdum>Well you say simply but that that would be very simple right? You you're using

00:17:28.770 --> 00:17:32.830
<v Aaron van Wirdum>the Muun software so I'm assuming, well the Muun wallet won't include the feature

00:17:32.830 --> 00:17:33.730
<v Aaron van Wirdum>that will allow that.

00:17:33.730 --> 00:17:37.490
<v Sjors Provoost>So so you would either just take the keys out of the Muun wallet put it in some

00:17:37.490 --> 00:17:42.430
<v Sjors Provoost>other wallet and then do it that way right? Or you figure out how the Muun wallet

00:17:42.860 --> 00:17:45.820
<v Sjors Provoost>communicates with the Muun server and you just write your own software that does

00:17:45.820 --> 00:17:49.930
<v Sjors Provoost>that and creates a bunch of fake accounts and does it with a lot of money.

00:17:50.250 --> 00:17:54.850
<v Aaron van Wirdum>Yeah, I'm just saying that's not simply for people like me, maybe for people like

00:17:54.850 --> 00:17:55.950
<v Aaron van Wirdum>you, but it's possible.

00:17:55.950 --> 00:17:59.490
<v Sjors Provoost>I would say it's for people who are sufficiently motivated to do this.

00:17:59.610 --> 00:18:00.390
<v Aaron van Wirdum>Yes, I agree.

00:18:00.610 --> 00:18:06.190
<v Sjors Provoost>Now, the way they prevent that scenario from happening is by not signaling

00:18:06.190 --> 00:18:11.670
<v Sjors Provoost>RBF. So their transactions do not opt into RBF, which means that by default, if

00:18:11.670 --> 00:18:15.190
<v Sjors Provoost>an attacker tries to do this and they're only connected to regular Bitcoin Core

00:18:15.190 --> 00:18:20.290
<v Sjors Provoost>nodes, those transactions won't propagate. But that is still quite risky because,

00:18:20.430 --> 00:18:25.650
<v Sjors Provoost>again, a sufficiently motivated attacker would find one of Peter Todd's nodes and

00:18:25.650 --> 00:18:31.120
<v Sjors Provoost>just connect to those or directly connect to a miner if they can find it and

00:18:31.120 --> 00:18:34.660
<v Sjors Provoost>start stealing it. So essentially it's not very safe, but at the same time it's

00:18:34.660 --> 00:18:38.760
<v Sjors Provoost>been working and I think they know that it's not safe and they want to improve

00:18:38.760 --> 00:18:43.210
<v Sjors Provoost>it. They just were hoping that they'd have another year on the roadmap before

00:18:43.210 --> 00:18:44.110
<v Sjors Provoost>they would have to do this.

00:18:44.450 --> 00:18:48.530
<v Aaron van Wirdum>Yeah. For context, Peter Todd's nodes, by that you mean, he runs a bunch of

00:18:48.530 --> 00:18:51.710
<v Aaron van Wirdum>Bitcoin Core nodes that have a patch for full RBF, right?

00:18:51.990 --> 00:18:53.190
<v Sjors Provoost>Yeah, and there's others that do that.

00:18:53.430 --> 00:18:58.580
<v Aaron van Wirdum>Yeah. Okay, so at that point, the discussion really flared up. And that's when

00:18:58.580 --> 00:19:03.580
<v Aaron van Wirdum>some merchants, basically, or payment providers, payment processing type of

00:19:03.580 --> 00:19:09.160
<v Aaron van Wirdum>people started to weigh in. And I think the argument can be summarized pretty

00:19:09.160 --> 00:19:14.120
<v Aaron van Wirdum>easily there, which is that... I mean, this is an argument we haven't even

00:19:14.120 --> 00:19:19.520
<v Aaron van Wirdum>mentioned in favor of full RBF, which is zero confirmation transactions aren't

00:19:19.520 --> 00:19:25.020
<v Aaron van Wirdum>secure anyways. They're just not secure. People shouldn't rely on them. So full

00:19:25.020 --> 00:19:31.240
<v Aaron van Wirdum>RBF, no RBF, flag RBF, it doesn't matter. You shouldn't trust zero conf.

00:19:31.860 --> 00:19:36.780
<v Sjors Provoost>Right, but there's a difference between saying that and then making the situation

00:19:36.780 --> 00:19:37.580
<v Sjors Provoost>even worse, right?

00:19:37.820 --> 00:19:41.610
<v Aaron van Wirdum>Well, that's where I'm getting at. So then this is one of these things where a

00:19:41.610 --> 00:19:43.830
<v Aaron van Wirdum>counter argument is a counter argument as a counter [unclear].

00:19:44.110 --> 00:19:44.370
<v Sjors Provoost>Yes.

00:19:44.990 --> 00:19:49.030
<v Aaron van Wirdum>So yeah. So then the counter argument there, the first counter argument is, well,

00:19:49.090 --> 00:19:53.730
<v Aaron van Wirdum>that might technically be true, but you know, we run a payment processor and

00:19:53.730 --> 00:19:58.910
<v Aaron van Wirdum>we've processed tens of thousands of payments and the number of double spends

00:19:58.910 --> 00:20:03.570
<v Aaron van Wirdum>that we've actually seen is negligible. Like right now there isn't actually a

00:20:03.570 --> 00:20:09.050
<v Aaron van Wirdum>problem with double spends that's you know worth taking very seriously or at

00:20:09.050 --> 00:20:12.430
<v Aaron van Wirdum>least it's very manageable. And then the counter counter argument as you

00:20:12.430 --> 00:20:14.170
<v Aaron van Wirdum>mentioned is…

00:20:16.410 --> 00:20:19.950
<v Aaron van Wirdum>No, that's not the counter counter. See, now I'm confusing my own arguments.

00:20:20.230 --> 00:20:23.390
<v Sjors Provoost>Well, you can go all sorts of directions with that counter counter argument. You

00:20:23.390 --> 00:20:27.190
<v Sjors Provoost>could say, well, but if you create an ecosystem that is too dependent on things

00:20:27.190 --> 00:20:30.870
<v Sjors Provoost>that are unsafe, you get a strong lobby to keep those unsafe things in. And then

00:20:30.870 --> 00:20:35.390
<v Sjors Provoost>in the long run, it goes really bad, right? Because you're building a really weak

00:20:35.390 --> 00:20:39.450
<v Sjors Provoost>foundation. So you could argue, no, we need to actively push more discipline into

00:20:39.450 --> 00:20:43.500
<v Sjors Provoost>the system. That's almost similar to the argument we had about... The Lightning

00:20:43.500 --> 00:20:47.600
<v Sjors Provoost>channel closures. So the Lightning node crashes right now.

00:20:49.010 --> 00:20:53.850
<v Aaron van Wirdum>Anyways, the point being, you just mentioned something about sabotaging the

00:20:53.850 --> 00:20:57.690
<v Aaron van Wirdum>network, right? Which argument was that? Was that some sub-argument or

00:20:57.690 --> 00:20:58.670
<v Aaron van Wirdum>counter-counter-argument?

00:20:58.850 --> 00:21:03.030
<v Sjors Provoost>Well, the argument is you can tell a company like, hey, your business model

00:21:03.030 --> 00:21:07.490
<v Sjors Provoost>relies on something that is inherently insecure, namely zero-conf. You can tell a

00:21:07.490 --> 00:21:11.180
<v Sjors Provoost>company that and then it's their decision. Or you could say, no, no, no, it's not

00:21:11.180 --> 00:21:14.820
<v Sjors Provoost>their decision. We're going to actively make them stop doing that.

00:21:16.050 --> 00:21:21.110
<v Sjors Provoost>And that could be an argument for simply deploying full RBF, even though you have

00:21:21.110 --> 00:21:25.410
<v Sjors Provoost>no other reason to do it. So if a pull request had been opened, and that comes

00:21:25.410 --> 00:21:28.210
<v Sjors Provoost>back to the Bitcoin Core process, I guess, if a pull request had been opened

00:21:28.210 --> 00:21:32.730
<v Sjors Provoost>saying, let's just enable full RBF for no other reason than to discipline these

00:21:32.730 --> 00:21:38.290
<v Sjors Provoost>zero-conf companies, then that argument probably would not have survived the pull

00:21:38.290 --> 00:21:42.310
<v Sjors Provoost>request process but that's not the only argument right? There's other arguments,

00:21:42.310 --> 00:21:45.520
<v Sjors Provoost>namely it might help with these pinning attacks, yadda yadda, yadda.

00:21:46.990 --> 00:21:51.930
<v Aaron van Wirdum>All right, so Sjors, as I mentioned I don't want to dwell on the discussion about

00:21:51.930 --> 00:21:56.670
<v Aaron van Wirdum>RBF too much but just to sort of work our way through a couple of arguments that

00:21:56.670 --> 00:22:01.310
<v Aaron van Wirdum>I'm not sure I've heard before real quick so one of the arguments is that

00:22:01.310 --> 00:22:06.890
<v Aaron van Wirdum>requiring an RBF flag in order to have your transactions be replaced is bad for

00:22:06.890 --> 00:22:12.050
<v Aaron van Wirdum>privacy. Like it sort of reveals something about the user and it can be used to,

00:22:12.050 --> 00:22:15.410
<v Aaron van Wirdum>you know, analyze the network and maybe cluster transactions, that kind of stuff.

00:22:15.610 --> 00:22:19.190
<v Aaron van Wirdum>So if we can get rid of the flag that would improve privacy, that's one argument.

00:22:19.290 --> 00:22:21.870
<v Sjors Provoost>It's another fingerprint that tells you something about the wallet, et cetera.

00:22:22.110 --> 00:22:27.630
<v Aaron van Wirdum>Yeah, exactly. There are also good reasons to maybe want to revert

00:22:27.630 --> 00:22:32.250
<v Aaron van Wirdum>transactions. You know, an obvious example would be you sent a transaction

00:22:32.250 --> 00:22:36.850
<v Aaron van Wirdum>accidentally. You know, that's... Well, in this case, you might want to.

00:22:37.090 --> 00:22:41.150
<v Sjors Provoost>You sent a transaction accidentally that did not signal RBF.

00:22:41.670 --> 00:22:42.430
<v Aaron van Wirdum>Yes, exactly.

00:22:42.630 --> 00:22:45.630
<v Sjors Provoost>So that would only be a problem with wallets that don't do that by default. But

00:22:45.630 --> 00:22:46.710
<v Sjors Provoost>yes, that's an argument.

00:22:46.870 --> 00:22:52.290
<v Aaron van Wirdum>Or another argument, this is kind of the standard argument, I guess, is we've

00:22:52.290 --> 00:22:56.450
<v Aaron van Wirdum>seen in the past couple of days where suddenly the mempool fills up with tons of

00:22:56.450 --> 00:23:00.770
<v Aaron van Wirdum>transactions. And there's definitely people on the network that don't use the RBF

00:23:00.770 --> 00:23:04.680
<v Aaron van Wirdum>flag just because their wallet doesn't do it by default or they haven't upgraded

00:23:04.680 --> 00:23:09.320
<v Aaron van Wirdum>their wallet for a long time and now these people have stuck transactions so it

00:23:09.320 --> 00:23:11.760
<v Aaron van Wirdum>might make sense for them if they can just replace it.

00:23:11.760 --> 00:23:15.720
<v Sjors Provoost>Yeah maybe though then the counter argument would be it would be strange to have

00:23:15.720 --> 00:23:20.440
<v Sjors Provoost>a wallet that does not support RBF but that can somehow replace transactions that

00:23:20.440 --> 00:23:25.910
<v Sjors Provoost>don't support RBF. But anyway, they might switch to a different wallet just to

00:23:25.910 --> 00:23:27.830
<v Sjors Provoost>replace the transaction, something like that.

00:23:28.050 --> 00:23:33.750
<v Aaron van Wirdum>Yeah, well, that's a good example. Peter Todd's argument is that right now a lot

00:23:33.750 --> 00:23:38.590
<v Aaron van Wirdum>of merchants that want to prevent double spending do this by monitoring the

00:23:38.590 --> 00:23:44.200
<v Aaron van Wirdum>network very extensively, which requires... Resource costs from all the nodes

00:23:44.200 --> 00:23:47.600
<v Aaron van Wirdum>they're connecting to so in that sense it's bad for the health of the network.

00:23:47.600 --> 00:23:51.880
<v Sjors Provoost>Yeah so I guess the idea here is that the the fee bump transactions or the

00:23:51.880 --> 00:23:55.540
<v Sjors Provoost>competing transactions could be in some corner of the network where they're

00:23:55.540 --> 00:23:58.080
<v Sjors Provoost>trying to double spend you and you're in a different corner of the network so you

00:23:58.080 --> 00:24:01.920
<v Sjors Provoost>don't see that you double spend so as a merchant in that case you really want to

00:24:01.920 --> 00:24:04.800
<v Sjors Provoost>be completely up to date on the mempool more so than other nodes.

00:24:04.800 --> 00:24:10.640
<v Aaron van Wirdum>Yeah there's something Sergey from Bitrefill brought up which is called the

00:24:10.640 --> 00:24:15.720
<v Aaron van Wirdum>the issue with the free American call option am I saying that right? I think so.

00:24:15.720 --> 00:24:21.300
<v Aaron van Wirdum>Which means a merchant that receives a transaction

00:24:21.300 --> 00:24:25.220
<v Aaron van Wirdum>if it's easier to replace the transaction then it could have a problem if the

00:24:25.220 --> 00:24:31.080
<v Aaron van Wirdum>price becomes volatile because users might decide to change their minds about the

00:24:31.080 --> 00:24:37.050
<v Aaron van Wirdum>purchase and sort of halfway just opt out so even if you do I guess… Yeah,

00:24:37.770 --> 00:24:42.010
<v Aaron van Wirdum>what's our reasoning here? Even if you do wait for confirmation, then until the

00:24:42.010 --> 00:24:42.830
<v Aaron van Wirdum>confirmation happens.

00:24:43.110 --> 00:24:46.690
<v Sjors Provoost>Well, I guess as a user, what you can do is you can send a very low fee

00:24:46.690 --> 00:24:52.270
<v Sjors Provoost>transaction to the merchant and then the merchant is just going to wait. Well, if

00:24:52.270 --> 00:24:56.350
<v Sjors Provoost>the merchant just waits for confirmation, then there's not really a problem. But

00:24:56.350 --> 00:25:00.470
<v Sjors Provoost>if the merchant wants to give you the product early or something like that, then

00:25:00.470 --> 00:25:05.030
<v Sjors Provoost>you might, well, you can already double spend. But I guess...

00:25:05.030 --> 00:25:06.630
<v Aaron van Wirdum>That's why I mentioned the confirmation.

00:25:07.470 --> 00:25:10.970
<v Sjors Provoost>I guess the other thing that might happen is that the merchant doesn't give you

00:25:10.970 --> 00:25:16.370
<v Sjors Provoost>the product yet, but they might lock in some sort of price. Yes, exactly. So they

00:25:16.370 --> 00:25:19.550
<v Sjors Provoost>might say, well, we're not going to ship anything yet to you, like a gift card,

00:25:19.690 --> 00:25:22.730
<v Sjors Provoost>but we're going to wait until there's a confirmation. But if there's a

00:25:22.730 --> 00:25:26.190
<v Sjors Provoost>confirmation, this is the price you're going to get, which is still sort of a

00:25:26.190 --> 00:25:30.590
<v Sjors Provoost>zero-conf thing to do, but slightly less so. And then in that case, yeah, the

00:25:30.590 --> 00:25:34.230
<v Sjors Provoost>user could see, well, if this deal... You know, because the price is already

00:25:34.230 --> 00:25:38.310
<v Sjors Provoost>locked in, if the price moves in the wrong direction, the user can double spend it.

00:25:40.330 --> 00:25:46.110
<v Sjors Provoost>And that's already possible if the user has opt-in RBF turned on. But then the

00:25:46.110 --> 00:25:51.710
<v Sjors Provoost>way merchants try to prevent that is to tell users don't turn opt-in RBF on. And

00:25:51.710 --> 00:25:54.670
<v Sjors Provoost>that, of course, won't work anymore if the flag has no meaning.

00:25:55.190 --> 00:25:59.350
<v Aaron van Wirdum>Yeah. And the counter-counter submeta argument there is that the merchant can

00:25:59.350 --> 00:26:01.110
<v Aaron van Wirdum>also use child pays for parents.

00:26:02.650 --> 00:26:07.410
<v Aaron van Wirdum>Anyway there was also something with CoinJoin but which also seems like it wasn't

00:26:07.410 --> 00:26:09.970
<v Aaron van Wirdum>a very strong argument because even some of the CoinJoin

00:26:09.970 --> 00:26:13.750
<v Sjors Provoost>I think the CoinJoin thing was just about pinning attacks. So there was a worry

00:26:13.750 --> 00:26:19.370
<v Sjors Provoost>about pinning attacks that could be slightly reduced by having this full RBF.

00:26:19.370 --> 00:26:22.910
<v Aaron van Wirdum>Right. Okay. Well so anyway, so we're rushing through a couple of the arguments

00:26:22.910 --> 00:26:26.830
<v Aaron van Wirdum>and some of them which I hadn't heard before. But I think the real issue is.

00:26:27.390 --> 00:26:31.330
<v Aaron van Wirdum>Should this have been included in Bitcoin Core? And now that it was included in

00:26:31.330 --> 00:26:37.260
<v Aaron van Wirdum>Bitcoin Core, should it be removed before release? That's what

00:26:37.260 --> 00:26:40.200
<v Aaron van Wirdum>a lot of the discussion ultimately sort of wound down to, right?

00:26:40.610 --> 00:26:44.670
<v Sjors Provoost>Yeah, and it was tricky because basically the discussion itself was holding the

00:26:44.670 --> 00:26:49.630
<v Sjors Provoost>release back, but you also get a little bit into these power dynamics of once

00:26:49.630 --> 00:26:53.910
<v Sjors Provoost>something is already merged, it takes more energy to get it out in a certain

00:26:53.910 --> 00:26:57.170
<v Sjors Provoost>sense. Somebody has to open a pull request to get it out, and somebody has to

00:26:57.170 --> 00:27:01.130
<v Sjors Provoost>then spend the energy defending that pull request. And so what ended up happening

00:27:01.130 --> 00:27:05.110
<v Sjors Provoost>is somebody, I think multiple people tried making pull requests to get it out,

00:27:05.270 --> 00:27:09.920
<v Sjors Provoost>and especially the last attempt had a lot of discussion. And we'll get to some

00:27:09.920 --> 00:27:11.440
<v Sjors Provoost>other arguments that we use in that discussion.

00:27:11.660 --> 00:27:12.740
<v Aaron van Wirdum>More arguments still?

00:27:13.180 --> 00:27:14.000
<v Sjors Provoost>Yeah, yeah, yeah, for sure.

00:27:14.320 --> 00:27:14.880
<v Aaron van Wirdum>Oh, my.

00:27:14.940 --> 00:27:20.640
<v Sjors Provoost>But basically what happens is if you open a pull request and a lot of people

00:27:20.640 --> 00:27:24.980
<v Sjors Provoost>don't like it, other people do like it, you get lots of toxic discussion on the

00:27:24.980 --> 00:27:28.900
<v Sjors Provoost>pull request, at some point you might decide, like, I don't want to bother with

00:27:28.900 --> 00:27:34.700
<v Sjors Provoost>this. And then essentially somebody can force a change or prevent the change

00:27:34.700 --> 00:27:39.700
<v Sjors Provoost>by just creating a lot of drama, not even having any arguments. Just the drama

00:27:39.700 --> 00:27:43.660
<v Sjors Provoost>itself can be a factor that decides whether a certain change happens or not. And

00:27:43.660 --> 00:27:48.240
<v Sjors Provoost>that, of course, is not a healthy development because that could be used to, I

00:27:48.240 --> 00:27:52.480
<v Sjors Provoost>don't know, prevent the soft fork from happening or... Make a soft fork happen

00:27:52.480 --> 00:27:55.740
<v Sjors Provoost>that we don't want to happen. Some other controversial change could just be

00:27:55.740 --> 00:28:00.680
<v Sjors Provoost>happening because you're just making you know anybody who so for example maybe

00:28:00.680 --> 00:28:05.280
<v Sjors Provoost>you sneak in some some evil change in the code somewhere when nobody's paying

00:28:05.280 --> 00:28:08.960
<v Sjors Provoost>attention and then anybody who tries to remove that evil change you just

00:28:08.960 --> 00:28:13.520
<v Sjors Provoost>completely make their life miserable by by making really a lot of drama around it

00:28:13.520 --> 00:28:16.720
<v Sjors Provoost>you know that could work maybe not there's just of course other things that could

00:28:16.720 --> 00:28:22.710
<v Sjors Provoost>happen in that case right But here, I think it's fair to say that, or at least

00:28:22.710 --> 00:28:28.510
<v Sjors Provoost>I think it's fair to say that the reason that full RBF is still in there is not

00:28:28.510 --> 00:28:31.910
<v Sjors Provoost>just because the arguments weighed in one way or the other. It had a lot to do

00:28:31.910 --> 00:28:37.270
<v Sjors Provoost>with the social dynamics of just making a lot of noise on any attempt to remove it.

00:28:39.100 --> 00:28:44.210
<v Aaron van Wirdum>Okay, Sjors, you mentioned that was one more argument. Actually, I think I know

00:28:44.210 --> 00:28:49.150
<v Aaron van Wirdum>where you want to go with this. Okay, let me first bring up one point myself. So

00:28:49.150 --> 00:28:54.290
<v Aaron van Wirdum>this is sort of my general philosophy when it comes to Bitcoin Core development

00:28:54.290 --> 00:28:59.470
<v Aaron van Wirdum>or the Bitcoin Core release process or what's included or what's not included. I

00:28:59.470 --> 00:29:04.770
<v Aaron van Wirdum>tend to like options. I think it's fine to give people options. I think it's fine

00:29:04.770 --> 00:29:05.910
<v Aaron van Wirdum>to give users options.

00:29:07.780 --> 00:29:09.660
<v Aaron van Wirdum>I think people should be...

00:29:11.050 --> 00:29:15.850
<v Aaron van Wirdum>Free to run their own nodes however they want basically. Now obviously Bitcoin

00:29:15.850 --> 00:29:20.330
<v Aaron van Wirdum>Core developers don't have some sort of obligation to include features, but in

00:29:20.330 --> 00:29:24.310
<v Aaron van Wirdum>this case it seems pretty obvious that if some Bitcoin Core developers think it's

00:29:24.310 --> 00:29:28.110
<v Aaron van Wirdum>a good idea some think it's maybe not a great idea, then I would say include it

00:29:28.110 --> 00:29:32.110
<v Aaron van Wirdum>as an option that people choose. The people that will actually make that choice,

00:29:32.110 --> 00:29:36.650
<v Aaron van Wirdum>you know they're the people that are running Bitcoin Core. And they know how to

00:29:36.650 --> 00:29:42.250
<v Aaron van Wirdum>change a default. These are pretty technical people. And I think they

00:29:42.250 --> 00:29:47.790
<v Aaron van Wirdum>should be trusted to be able to do that. Now, what the default is, that's maybe a

00:29:47.790 --> 00:29:51.470
<v Aaron van Wirdum>more interesting discussion, especially in a case like this. I don't know where I

00:29:51.470 --> 00:29:52.550
<v Aaron van Wirdum>would land on that discussion.

00:29:53.070 --> 00:29:55.790
<v Sjors Provoost>But that's not the actual discussion here, so that's fine.

00:29:56.050 --> 00:29:59.350
<v Aaron van Wirdum>Including it as a default, in my mind, that should always be fine.

00:29:59.470 --> 00:30:00.310
<v Sjors Provoost>Including it as an option.

00:30:00.410 --> 00:30:02.710
<v Aaron van Wirdum>Sorry, yeah. Including it as an option should always be fine.

00:30:02.770 --> 00:30:07.590
<v Sjors Provoost>So I agree with that in general, but I can give you a very different topic area

00:30:07.590 --> 00:30:12.910
<v Sjors Provoost>where it's very clearly not so obvious. So, for example, there is an option

00:30:12.910 --> 00:30:18.880
<v Sjors Provoost>called, I think, assumevalid which is the block where we, you know, which has

00:30:18.880 --> 00:30:23.260
<v Sjors Provoost>been baked into the source code where we say you cannot, you don't have to verify

00:30:23.260 --> 00:30:27.460
<v Sjors Provoost>signatures before that. Actually, that may be the wrong example, but they're

00:30:27.460 --> 00:30:33.060
<v Sjors Provoost>similar. There's some options where basically if you provide a

00:30:33.060 --> 00:30:36.720
<v Sjors Provoost>malicious, if somebody gives you a malicious suggestion for that option, they can

00:30:36.720 --> 00:30:40.320
<v Sjors Provoost>steal your coins. So I don't think it's true for assumevalid, but it might be for

00:30:40.320 --> 00:30:45.080
<v Sjors Provoost>assumeutxo for some of the proposals we say. So you could give the user like, oh,

00:30:45.220 --> 00:30:48.960
<v Sjors Provoost>just add this to your Bitcoin Core settings and things will be great for you.

00:30:49.120 --> 00:30:51.500
<v Aaron van Wirdum>Well, if you say it in that voice, it's very compelling.

00:30:51.960 --> 00:30:57.200
<v Sjors Provoost>Exactly. So there are some things that you might be able to, that could be abused

00:30:57.200 --> 00:31:00.340
<v Sjors Provoost>by making it a little bit too easy for users to configure things that would shoot

00:31:00.340 --> 00:31:03.700
<v Sjors Provoost>them in the foot. So those settings generally are not in there. And there's

00:31:03.700 --> 00:31:08.020
<v Sjors Provoost>definitely settings that are hidden in a way that you can only use them on test

00:31:08.020 --> 00:31:12.420
<v Sjors Provoost>networks you can't use them on the real network. So as a general rule basically

00:31:12.420 --> 00:31:15.620
<v Sjors Provoost>you should be able to configure whatever you want, but if it's a true footgun,

00:31:15.620 --> 00:31:19.000
<v Sjors Provoost>then maybe not or at least it should be a little bit more difficult so that you

00:31:19.000 --> 00:31:23.080
<v Sjors Provoost>really know what you're doing. The question is does that apply here? Now

00:31:23.080 --> 00:31:26.500
<v Sjors Provoost>initially you might think no. It doesn't really apply here why would it matter

00:31:26.500 --> 00:31:32.620
<v Sjors Provoost>that somebody turns on this full RBF and or not? And so this is where the last I guess…

00:31:33.950 --> 00:31:38.290
<v Sjors Provoost>attempt to undo this pull request came from the realization by at least some

00:31:38.290 --> 00:31:42.390
<v Sjors Provoost>people that maybe this is one of those cases where it's not a good idea to give

00:31:42.390 --> 00:31:45.790
<v Sjors Provoost>everybody an option because it could actually have some cause some problems down

00:31:45.790 --> 00:31:48.910
<v Sjors Provoost>the line that are completely separate from whether or not you think RBF is good

00:31:48.910 --> 00:31:54.170
<v Sjors Provoost>or not. And this is, I believe, posted initially by AJ, Andrew Towns, and by

00:31:54.170 --> 00:31:58.470
<v Sjors Provoost>Suhas as well as a follow up on the Bitcoin developer mailing list. And the

00:31:58.470 --> 00:32:02.630
<v Sjors Provoost>general topic was like, do we want mempool policies to start diverging?

00:32:04.560 --> 00:32:10.410
<v Sjors Provoost>And what this means is that if you run the mempool with one setting and I run it

00:32:10.410 --> 00:32:13.690
<v Sjors Provoost>with another setting, then our mempools are going to be different. That are some

00:32:13.690 --> 00:32:17.650
<v Sjors Provoost>settings where this different isn't a big deal. So for example, if I set my

00:32:17.650 --> 00:32:21.310
<v Sjors Provoost>mempool to one gigabyte and you leave it at 300 megabytes, then my mempool is

00:32:21.310 --> 00:32:27.170
<v Sjors Provoost>going to be bigger than your mempool. But basically the top of the mempool, so

00:32:27.170 --> 00:32:30.450
<v Sjors Provoost>the transactions that are going to be in the next block, that's going to look the

00:32:30.450 --> 00:32:36.240
<v Sjors Provoost>same between us. But if one of us turns on RBF and the other person doesn't, it's

00:32:36.240 --> 00:32:41.070
<v Sjors Provoost>going to be different. Now, what this means is that if you're a miner, you want

00:32:41.070 --> 00:32:44.810
<v Sjors Provoost>to mine the economically most efficient block. Now you're going to have to

00:32:44.810 --> 00:32:49.570
<v Sjors Provoost>connect really to both of us because you want to see what the best block is in

00:32:49.570 --> 00:32:55.550
<v Sjors Provoost>mining pool type 1 and what the best block is going to be for mining pool type B.

00:32:55.790 --> 00:33:00.470
<v Aaron van Wirdum>Don't you only have to connect to the full RBF node?

00:33:00.690 --> 00:33:03.330
<v Sjors Provoost>No, because they might have mutually exclusive transactions in them.

00:33:05.270 --> 00:33:06.550
<v Sjors Provoost>Because I could...

00:33:07.830 --> 00:33:12.300
<v Sjors Provoost>I mean, you'd have to come up with some esoteric... Examples I guess because in

00:33:12.300 --> 00:33:12.700
<v Sjors Provoost>this case

00:33:12.700 --> 00:33:17.620
<v Aaron van Wirdum>Yeah I think the example there would be that a transaction with a low fee has

00:33:17.620 --> 00:33:23.500
<v Aaron van Wirdum>very high fee child transactions so it's it's bumps from the

00:33:23.500 --> 00:33:28.080
<v Aaron van Wirdum>full RBF node and therefore the high fee child transactions are also bumped from

00:33:28.080 --> 00:33:33.060
<v Aaron van Wirdum>the high fee node like something that this would be the scenario something like this right

00:33:33.060 --> 00:33:38.880
<v Sjors Provoost>So I'm I'm not actually entirely sure about this one so in principle at least You

00:33:38.880 --> 00:33:42.500
<v Sjors Provoost>know, there could be things in the full RBF node that are not in the opt-in RBF

00:33:42.500 --> 00:33:45.880
<v Sjors Provoost>node, but it may not be the other way around. That may not be as big a deal. But

00:33:45.880 --> 00:33:49.360
<v Sjors Provoost>still, it creates some sort of split. So the worry there is that there might be

00:33:49.360 --> 00:33:53.940
<v Sjors Provoost>some settings where these kind of splits could happen, and they could be worse.

00:33:54.200 --> 00:33:58.500
<v Sjors Provoost>They might not be just in one direction. There might be things that people can

00:33:58.500 --> 00:33:59.860
<v Sjors Provoost>toggle that work in both directions.

00:34:00.810 --> 00:34:05.330
<v Aaron van Wirdum>Okay, so what is the exact problem here? That a miner has to connect to multiple nodes?

00:34:05.530 --> 00:34:10.530
<v Sjors Provoost>Yes, exactly. And that comes back to similar to the argument of having nodes

00:34:10.530 --> 00:34:14.030
<v Sjors Provoost>connect to lots of nodes. The miners would be connecting to lots of nodes. If

00:34:14.030 --> 00:34:17.270
<v Sjors Provoost>that goes too far, then miners would have to have a lot of connections to a lot

00:34:17.270 --> 00:34:20.210
<v Sjors Provoost>of different nodes, which means it's more expensive to run a miner, basically.

00:34:21.090 --> 00:34:26.090
<v Sjors Provoost>And conversely... As a miner, you probably want to be very reachable to different

00:34:26.090 --> 00:34:31.150
<v Sjors Provoost>kind of nodes. So you might want to almost identify yourself as a miner so that

00:34:31.150 --> 00:34:35.850
<v Sjors Provoost>all these different sub-mempools basically that are out there all connect to you.

00:34:36.350 --> 00:34:39.690
<v Sjors Provoost>And that's not good either because you want to have some privacy as a miner. So

00:34:39.690 --> 00:34:43.130
<v Sjors Provoost>the very long-term consequence is that if you make it too easy for users to start

00:34:43.130 --> 00:34:47.310
<v Sjors Provoost>choosing things somewhat arbitrarily that create different kinds of mempools,

00:34:47.530 --> 00:34:53.120
<v Sjors Provoost>then you might end up in an ecosystem where mining becomes... More difficult,

00:34:53.280 --> 00:34:57.260
<v Sjors Provoost>therefore easier to centralize. That's sort of the long-term risk. Now, whether

00:34:57.260 --> 00:35:01.920
<v Sjors Provoost>this one little setting really matters in the scheme of things, that's, I think,

00:35:02.040 --> 00:35:07.170
<v Sjors Provoost>very debatable. And so that's why maybe, you know, but that was the reason why

00:35:07.170 --> 00:35:10.990
<v Sjors Provoost>this last pull request was opened to say, well, we're worried about this scenario

00:35:10.990 --> 00:35:15.460
<v Sjors Provoost>and we should think about this scenario a bit more. And so maybe we should do

00:35:15.460 --> 00:35:18.520
<v Sjors Provoost>this option in the next release while we have some time to think about whether

00:35:18.520 --> 00:35:19.540
<v Sjors Provoost>this really matters or not.

00:35:19.820 --> 00:35:25.180
<v Aaron van Wirdum>Yeah, I guess the counter-argument there would also be that this is already a

00:35:25.180 --> 00:35:30.440
<v Aaron van Wirdum>potential long-term risk because people can always patch their Bitcoin Core node

00:35:30.440 --> 00:35:31.460
<v Aaron van Wirdum>or run something else.

00:35:31.660 --> 00:35:35.900
<v Sjors Provoost>Yeah, but they're much less likely to do it at a scale that it matters for your

00:35:35.900 --> 00:35:36.620
<v Sjors Provoost>revenue.

00:35:36.900 --> 00:35:38.200
<v Aaron van Wirdum>Maybe, maybe not.

00:35:39.130 --> 00:35:44.800
<v Sjors Provoost>But anyway, the hope was to have... To not have two different versions, to have a

00:35:44.800 --> 00:35:50.600
<v Sjors Provoost>new version of RBF, maximal RBF, or transaction version number three,

00:35:50.760 --> 00:35:55.440
<v Sjors Provoost>or some sort of proposal that everybody would be happy with, at which point you

00:35:55.440 --> 00:35:58.220
<v Sjors Provoost>would not have two different policies. You just have one, and you'd recommend it

00:35:58.220 --> 00:36:01.760
<v Sjors Provoost>to everyone. So the idea would be to wait a little bit and not have the split.

00:36:02.200 --> 00:36:06.480
<v Sjors Provoost>But you could also say these type of split scenarios are not likely to happen in

00:36:06.480 --> 00:36:07.520
<v Sjors Provoost>the very short future anyway.

00:36:09.370 --> 00:36:10.250
<v Sjors Provoost>So it's...

00:36:10.250 --> 00:36:13.810
<v Aaron van Wirdum>Well, you also mentioned you just call it a recommendation, and I would agree

00:36:13.810 --> 00:36:16.830
<v Aaron van Wirdum>with that in the sense that a default is already a recommendation.

00:36:17.330 --> 00:36:20.450
<v Sjors Provoost>Yeah, as long as everybody sticks to the recommendation, then nothing changes.

00:36:21.010 --> 00:36:25.650
<v Sjors Provoost>But that also goes to the, you know, what is the reality now? How many people are

00:36:25.650 --> 00:36:29.330
<v Sjors Provoost>going to turn on this setting? I don't know. But then you have people like Peter

00:36:29.330 --> 00:36:34.850
<v Sjors Provoost>Todd who are now trying to accelerate this new reality anyway by... Running a

00:36:34.850 --> 00:36:36.670
<v Sjors Provoost>bounty program I don't think we talked about that yet.

00:36:36.670 --> 00:36:40.870
<v Aaron van Wirdum>Yeah let's let's mention that as sort of last part of this episode because I've

00:36:40.870 --> 00:36:45.190
<v Aaron van Wirdum>seen something about it but I haven't kept up with that thread. Like that was

00:36:45.190 --> 00:36:50.790
<v Aaron van Wirdum>another side argument somewhere happening somewhere where I wasn't paying

00:36:50.790 --> 00:36:53.690
<v Aaron van Wirdum>attention… but there was a bounty program by Peter Todd is that right?

00:36:53.690 --> 00:36:58.330
<v Sjors Provoost>So one way to get to avoid the problem of having two different settings or you

00:36:58.330 --> 00:37:01.950
<v Sjors Provoost>know two different mempools or or having this debate go on forever is to just

00:37:03.190 --> 00:37:09.050
<v Sjors Provoost>basically make miners use full RBF at such a scale that it just becomes even

00:37:09.050 --> 00:37:15.010
<v Sjors Provoost>more unsafe to keep the opt-in RBF version around. And so that's what he

00:37:15.010 --> 00:37:18.630
<v Sjors Provoost>tried to do. I think he created an address where people can donate, but also just

00:37:18.630 --> 00:37:22.750
<v Sjors Provoost>put some of his own money in. And he's basically making transactions that don't

00:37:22.750 --> 00:37:26.470
<v Sjors Provoost>signal RBF and pay like one Satoshi per byte. And then he puts another

00:37:26.470 --> 00:37:31.510
<v Sjors Provoost>transaction on top of it that pays a hundred dollars in fees and then basically

00:37:31.510 --> 00:37:34.870
<v Sjors Provoost>any miner that doesn't run full RBF would be stupid in this case because they

00:37:34.870 --> 00:37:40.550
<v Sjors Provoost>would miss out on 100 bucks. And then if you do that at the right time, so I

00:37:40.550 --> 00:37:44.710
<v Sjors Provoost>guess when fees are very low but the mempool is full. So I don't know some some

00:37:44.710 --> 00:37:48.490
<v Sjors Provoost>moment when there's a strong incentive to to snap up that extra hundred dollars

00:37:48.490 --> 00:37:54.160
<v Sjors Provoost>you can very cheaply create an incentive to tilt the ecosystem in one direction

00:37:54.160 --> 00:37:55.380
<v Sjors Provoost>yeah and he can do that.

00:37:55.380 --> 00:37:56.500
<v Aaron van Wirdum>So and how is that going?

00:37:56.500 --> 00:37:57.300
<v Sjors Provoost>I don't know.

00:37:59.220 --> 00:38:00.340
<v Aaron van Wirdum>So I think...

00:38:00.340 --> 00:38:04.520
<v Sjors Provoost>I mean, today or a couple of days ago before we were recording it, Binance

00:38:04.520 --> 00:38:08.340
<v Sjors Provoost>decided to consolidate all their transactions, which actually filled the mempool

00:38:08.340 --> 00:38:14.280
<v Sjors Provoost>very quickly. And then it's actually already trivial to do double spends because

00:38:14.280 --> 00:38:17.160
<v Sjors Provoost>all the low fee transactions would have been booted out of the mempool and you

00:38:17.160 --> 00:38:20.280
<v Sjors Provoost>can simply create a brand new transaction with a higher fee and it would just

00:38:20.280 --> 00:38:24.460
<v Sjors Provoost>propagate everywhere. So that kind of interferes with the experiment. I don't

00:38:24.460 --> 00:38:25.160
<v Sjors Provoost>know what the stats are.

00:38:25.300 --> 00:38:30.300
<v Aaron van Wirdum>I thought the takeaway so far was that miners were not using full RBF. That's

00:38:30.300 --> 00:38:34.320
<v Aaron van Wirdum>what I sort of saw from the corner of my eye in one of the side discussions that

00:38:34.320 --> 00:38:38.200
<v Aaron van Wirdum>I didn't really follow. But I think that was the latest update on that end.

00:38:38.320 --> 00:38:43.320
<v Sjors Provoost>My hope is that there'll be some good dashboards that observe exactly which pools

00:38:43.320 --> 00:38:46.740
<v Sjors Provoost>are doing that and which pools are not, which gives you some indication of what

00:38:46.740 --> 00:38:47.280
<v Sjors Provoost>the odds are.

00:38:49.250 --> 00:38:52.460
<v Aaron van Wirdum>Yeah. Are you going to make that? This sounds like a job for Sjors.

00:38:52.720 --> 00:38:58.660
<v Sjors Provoost>No, what I do is I go to projects like miningpoolops or miningpoolobserver. I

00:38:58.660 --> 00:39:02.420
<v Sjors Provoost>think it's miningpool.observer, the domain. And I go to the GitHub repo and I

00:39:02.420 --> 00:39:06.370
<v Sjors Provoost>make an issue saying, hey, it'd be good to monitor this. And then somebody else

00:39:06.370 --> 00:39:08.310
<v Sjors Provoost>gets really excited by that and does it.

00:39:09.300 --> 00:39:11.460
<v Aaron van Wirdum>Smart, smart. That's how smart people work.

00:39:11.860 --> 00:39:12.160
<v Sjors Provoost>Yep.

00:39:13.000 --> 00:39:17.750
<v Aaron van Wirdum>Okay, Sjors, I think that's it for me. Did we forget anything? Do you want to add

00:39:17.750 --> 00:39:21.730
<v Aaron van Wirdum>anything? Do you want to tell our listeners something before we end the episode?

00:39:22.110 --> 00:39:27.510
<v Sjors Provoost>No, I believe Bitcoin Core version 24.0 is coming very soon, TM.

00:39:27.970 --> 00:39:33.390
<v Aaron van Wirdum>Including the option to switch on full RBF. That was not removed in the end, right?

00:39:34.010 --> 00:39:38.310
<v Sjors Provoost>Exactly. And you should download that new release anyway and try it out. And so

00:39:38.310 --> 00:39:40.210
<v Sjors Provoost>thank you for listening to Bitcoin.

00:39:40.650 --> 00:39:41.170
<v Aaron van Wirdum>Explained.

