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:24.950
<v Aaron van Wirdum>Live from Utrecht, this is Bitcoin Explained. Hey Sjors.

00:00:25.610 --> 00:00:25.830
<v Sjors Provoost>Hello.

00:00:26.670 --> 00:00:31.050
<v Aaron van Wirdum>So this was kind of funny. We always have our conversation before we do the

00:00:31.050 --> 00:00:36.170
<v Aaron van Wirdum>actual podcast one day in advance. And then you ask me, do you have any topics?

00:00:36.290 --> 00:00:40.550
<v Aaron van Wirdum>And I ask you, do you have any topics? And this time we both had a topic in mind.

00:00:41.390 --> 00:00:45.170
<v Aaron van Wirdum>But we both had a different topic in mind, except it turned out it was sort of

00:00:45.170 --> 00:00:46.270
<v Aaron van Wirdum>the same topic after all.

00:00:46.610 --> 00:00:46.890
<v Sjors Provoost>Exactly.

00:00:47.030 --> 00:00:52.090
<v Aaron van Wirdum>We just approached it from like opposite directions. And then we realized that we

00:00:52.090 --> 00:00:56.290
<v Aaron van Wirdum>were, you know, talking about the same thing. So we're going to talk about Stamps

00:00:56.290 --> 00:00:59.850
<v Aaron van Wirdum>and an invalid block that was found.

00:01:00.110 --> 00:01:01.170
<v Sjors Provoost>On April Fool's Day.

00:01:03.290 --> 00:01:05.510
<v Aaron van Wirdum>The block was mined on April Fool's Day?

00:01:05.690 --> 00:01:06.030
<v Sjors Provoost>Yes.

00:01:06.270 --> 00:01:11.050
<v Aaron van Wirdum>Right. But first, Sjors, you want to read some boostagrams, I think. Is that what it's called?

00:01:11.210 --> 00:01:11.770
<v Sjors Provoost>That's right.

00:01:12.670 --> 00:01:17.770
<v Aaron van Wirdum>Sjors stacks sats. Sjors stacks sats. Sjors stacks sats.

00:01:17.990 --> 00:01:22.590
<v Sjors Provoost>Hooray. Okay, I've got one from Eric99 for

00:01:22.590 --> 00:01:27.190
<v Sjors Provoost>50,000 sats. And he says, stay humble, stack sats.

00:01:27.710 --> 00:01:28.550
<v Aaron van Wirdum>There you go.

00:01:30.640 --> 00:01:35.700
<v Aaron van Wirdum>Okay where do we start with this so we we did an episode on

00:01:35.700 --> 00:01:41.580
<v Aaron van Wirdum>inscriptions two three episodes ago something like that and in a way

00:01:41.580 --> 00:01:47.200
<v Aaron van Wirdum>I guess Stamps are a new way of doing inscriptions but they're really an old way

00:01:47.200 --> 00:01:50.660
<v Sjors Provoost>or yeah they're they're really an old and very inefficient way to do

00:01:50.660 --> 00:01:53.420
<v Aaron van Wirdum>they're kind of a rediscovered older

00:01:53.500 --> 00:01:59.270
<v Aaron van Wirdum>Well, they—we kind of—when we discussed inscriptions,

00:01:59.310 --> 00:02:04.450
<v Aaron van Wirdum>the point was that people were always putting stuff on the blockchain and then

00:02:04.670 --> 00:02:10.270
<v Aaron van Wirdum>Bitcoin developers figured out better ways of doing it. And now Stamps is kind of

00:02:10.270 --> 00:02:12.950
<v Aaron van Wirdum>going back to the bad ways of doing it.

00:02:12.950 --> 00:02:17.630
<v Sjors Provoost>Yeah, because they realized that putting things on the blockchain is a van Wirdum

00:02:17.630 --> 00:02:19.210
<v Sjors Provoost>good, as you would call it.

00:02:19.350 --> 00:02:23.630
<v Aaron van Wirdum>That's a reference. That's a deep reference to the Bitcoin show or Dutch podcast.

00:02:24.480 --> 00:02:27.480
<v Sjors Provoost>Yes, and I forgot what the actual word was.

00:02:27.660 --> 00:02:28.220
<v Aaron van Wirdum>Veblen good?

00:02:28.720 --> 00:02:32.780
<v Sjors Provoost>Yeah, Veblen good or something. Anyway, it means something that because it's

00:02:32.780 --> 00:02:36.740
<v Sjors Provoost>expensive, it's actually more popular. So you think you don't want to put too

00:02:36.740 --> 00:02:40.960
<v Sjors Provoost>much stuff on the blockchain because that is inefficient, but it turns out that

00:02:40.960 --> 00:02:44.340
<v Sjors Provoost>because it's so expensive to put stuff on the blockchain, it actually suddenly

00:02:44.340 --> 00:02:49.140
<v Sjors Provoost>became popular with inscriptions. And so the folks from Counterparty said they

00:02:49.140 --> 00:02:52.940
<v Sjors Provoost>had an old method to put data on the blockchain even more inefficiently

00:02:54.260 --> 00:02:58.740
<v Sjors Provoost>than with ordinals. So that's sort of what you were seeing. And then what I was

00:02:58.740 --> 00:03:02.040
<v Sjors Provoost>seeing was that there was an invalid block and I started looking at why that

00:03:02.040 --> 00:03:06.120
<v Sjors Provoost>block was invalid. And that actually ties into what we discussed last episode.

00:03:06.480 --> 00:03:10.600
<v Sjors Provoost>Because in our last episode, we talked about multisig. And one of the things we

00:03:10.600 --> 00:03:14.900
<v Sjors Provoost>discussed as part of multisig was this weird thing called the sigops counter.

00:03:16.870 --> 00:03:22.220
<v Sjors Provoost>And... So a block can have four mega—four [unclear], or whatever,

00:03:22.560 --> 00:03:28.240
<v Sjors Provoost>four megabyte worth of stuff in it. And there's this

00:03:28.240 --> 00:03:33.280
<v Sjors Provoost>counter for how much. So SegWit data counts as less than regular data.

00:03:33.980 --> 00:03:38.820
<v Sjors Provoost>And that's how you get a fee market, which is a fairly straightforward way to

00:03:38.820 --> 00:03:44.430
<v Sjors Provoost>calculate. But then the problem is... There's another counter for things that

00:03:44.430 --> 00:03:49.950
<v Sjors Provoost>involve signature checking called the sigops counter. And it turns out that the

00:03:49.950 --> 00:03:52.870
<v Sjors Provoost>reason this block failed, or at least the message I saw when the block failed,

00:03:53.030 --> 00:03:55.270
<v Sjors Provoost>was max sigops exceeded.

00:03:56.220 --> 00:03:59.980
<v Aaron van Wirdum>Yeah, we'll get to that, I think, later. But yeah, you're right. So we discussed

00:03:59.980 --> 00:04:03.440
<v Aaron van Wirdum>that in the previous episode. And then I think maybe the episode before that was

00:04:03.440 --> 00:04:08.220
<v Aaron van Wirdum>inscriptions. So this episode is sort of combining insights from the previous two

00:04:08.220 --> 00:04:08.640
<v Aaron van Wirdum>episodes.

00:04:09.450 --> 00:04:09.850
<v Sjors Provoost>Yes.

00:04:10.090 --> 00:04:10.390
<v Aaron van Wirdum>Is there? Okay.

00:04:10.730 --> 00:04:14.650
<v Sjors Provoost>And the other observation I guess we did was a very happy Mike in Space on

00:04:14.650 --> 00:04:19.260
<v Sjors Provoost>Twitter. Though not because of the failed block, but very much around the same time.

00:04:19.360 --> 00:04:23.260
<v Aaron van Wirdum>I was just going to ask, so who's Mike in Space? Because Mike in Space introduced

00:04:23.260 --> 00:04:25.000
<v Aaron van Wirdum>this Stamps protocol, right?

00:04:25.300 --> 00:04:28.820
<v Sjors Provoost>Yeah. Well, Mike in Space is a famous movie maker. He made this, this series

00:04:28.820 --> 00:04:29.720
<v Sjors Provoost>Bitcoin Car Talk.

00:04:31.340 --> 00:04:34.020
<v Sjors Provoost>And he's also involved with the Counterparty protocol.

00:04:34.260 --> 00:04:38.560
<v Aaron van Wirdum>I think there's probably a lot of newer Bitcoiners that may not know

00:04:38.560 --> 00:04:44.560
<v Aaron van Wirdum>Mike in Space. He was sort of... A comic relief type of figure on Bitcoin Twitter

00:04:44.560 --> 00:04:49.000
<v Aaron van Wirdum>Yeah, sort of during the block size war kind of era I would say.

00:04:49.000 --> 00:04:53.920
<v Sjors Provoost>Yeah, so the Bitcoin Car Talk series very short videos he made were quite funny I

00:04:53.920 --> 00:04:57.160
<v Sjors Provoost>think I don't know if they're still on YouTube but they would involve him sitting

00:04:57.160 --> 00:05:00.200
<v Sjors Provoost>in a car and calling somebody else who might be sitting in another car and

00:05:00.200 --> 00:05:04.320
<v Sjors Provoost>talking about something technical but in a funny way and then either the car

00:05:04.320 --> 00:05:06.620
<v Sjors Provoost>would explode or or somebody would be in the trunk.

00:05:06.620 --> 00:05:10.020
<v Aaron van Wirdum>Yeah, there were like spoof interviews with Bitcoin developers and that kind of

00:05:10.020 --> 00:05:15.700
<v Aaron van Wirdum>stuff. Yeah, so now he somehow introduced a new particle is I

00:05:15.960 --> 00:05:19.400
<v Aaron van Wirdum>guess my question to you or is this serious

00:05:20.320 --> 00:05:20.980
<v Sjors Provoost>I don't know.

00:05:21.100 --> 00:05:26.020
<v Aaron van Wirdum>Because we know him as a comedian, basically, right? Is it supposed to be

00:05:26.020 --> 00:05:29.280
<v Aaron van Wirdum>serious? How are we supposed to look at this or think about this?

00:05:29.280 --> 00:05:33.180
<v Sjors Provoost>This is always difficult to know, right? Because Counterparty was partly a joke,

00:05:33.340 --> 00:05:36.900
<v Sjors Provoost>especially with the Rare Pepe that was being traded. But Rare Pepe was

00:05:36.900 --> 00:05:41.400
<v Sjors Provoost>essentially there before even CryptoKitties, one of the first NFTs. And that

00:05:41.400 --> 00:05:45.930
<v Sjors Provoost>trading was kind of a joke, but also involved money. And it had its own token.

00:05:46.390 --> 00:05:50.490
<v Sjors Provoost>So, you know, that was partly a joke, but it was also not a joke. And some people

00:05:50.490 --> 00:05:52.810
<v Sjors Provoost>make money, some people lost money. So you never know these things.

00:05:53.030 --> 00:05:54.970
<v Aaron van Wirdum>I mean, that's, did I discuss this before?

00:05:54.970 --> 00:05:56.770
<v Sjors Provoost>The blockchain doesn't care whether it's a joke or not.

00:05:57.090 --> 00:06:00.990
<v Aaron van Wirdum>Yeah, I don't remember if I discussed this on the podcast before, but what's the

00:06:00.990 --> 00:06:05.690
<v Aaron van Wirdum>guy's name who was behind the whole Rare Pepe thing and who was promoting it? I

00:06:05.690 --> 00:06:06.930
<v Aaron van Wirdum>should know his name. I know his name.

00:06:07.130 --> 00:06:10.030
<v Sjors Provoost>Well, John Seth is one of them, but he was not behind it, but he was promoting

00:06:10.030 --> 00:06:13.250
<v Sjors Provoost>it. But he was jokingly promoting it as part of Bitcoin Uncensored.

00:06:13.290 --> 00:06:18.130
<v Aaron van Wirdum>Well, that's the point. Man, his name is slipping my mind right now. Anyways.

00:06:18.530 --> 00:06:19.310
<v Sjors Provoost>John Carvalho?

00:06:19.570 --> 00:06:19.930
<v Aaron van Wirdum>No.

00:06:22.000 --> 00:06:27.880
<v Aaron van Wirdum>Yeah I I his name is escaping me but yeah no I I always took it as a joke and I

00:06:27.880 --> 00:06:31.680
<v Aaron van Wirdum>thought it was like a hilarious joke I thought it was he did this interview this

00:06:31.680 --> 00:06:35.800
<v Aaron van Wirdum>famous and there was this famous interview Sjors, maybe we're going off the rails

00:06:35.800 --> 00:06:40.580
<v Aaron van Wirdum>now with these sort of half-baked memories he did this famous interview at the

00:06:40.580 --> 00:06:45.140
<v Aaron van Wirdum>time about Rare Pepes and sort of defending it and it was really hilarious and

00:06:45.140 --> 00:06:50.850
<v Aaron van Wirdum>then I ran into him pretty recently like a year ago and I commented on how funny

00:06:50.850 --> 00:06:54.690
<v Aaron van Wirdum>that interview was and the reason it was so funny because he kept a straight face

00:06:54.690 --> 00:06:59.190
<v Aaron van Wirdum>the whole time and now I ran into him and I told him that and turns out that no

00:06:59.190 --> 00:07:03.370
<v Aaron van Wirdum>he wasn't actually like his straight face was a genuine straight face he was

00:07:03.370 --> 00:07:07.070
<v Aaron van Wirdum>actually being serious about the whole NFT thing and he actually believed in it

00:07:07.070 --> 00:07:11.610
<v Aaron van Wirdum>well for me it was anyways a lot of people including myself thought it was like

00:07:11.610 --> 00:07:15.630
<v Aaron van Wirdum>taking the piss out of the concept but no he actually believed in it and I guess

00:07:15.630 --> 00:07:17.630
<v Aaron van Wirdum>a lot of people believe in the whole NFT thing.

00:07:17.810 --> 00:07:22.790
<v Sjors Provoost>Well, but it ran into problems because all these transactions were on-chain. And

00:07:22.790 --> 00:07:26.130
<v Sjors Provoost>especially early on, fees started going up in the Bitcoin network. Fee estimation

00:07:26.130 --> 00:07:30.730
<v Sjors Provoost>was very bad. So I think the wallet software that Counterparty was using was just

00:07:30.730 --> 00:07:35.810
<v Sjors Provoost>a modified Bitcoin Core client, which did not have very good fee estimation. And

00:07:35.810 --> 00:07:40.690
<v Sjors Provoost>so each of these transactions became extremely expensive. And I think they even

00:07:40.690 --> 00:07:43.870
<v Sjors Provoost>thought about moving the whole protocol off to one of the forks or some other

00:07:43.870 --> 00:07:49.490
<v Sjors Provoost>blockchain. So we hadn't really heard from it in a while but once the ordinals

00:07:49.490 --> 00:07:55.070
<v Sjors Provoost>inscription stuff started coming about I think they kind of made a comeback and

00:07:55.070 --> 00:07:59.770
<v Sjors Provoost>so the Stamps protocol is just one example of how you can use Counterparty and I

00:07:59.770 --> 00:08:04.910
<v Sjors Provoost>think the idea there is you put very small images on the blockchain so 64 by 64

00:08:04.910 --> 00:08:08.670
<v Sjors Provoost>pixels and then you you know you trade them

00:08:09.150 --> 00:08:14.870
<v Aaron van Wirdum>okay so let's let's talk about it more in detail more specifically so

00:08:17.720 --> 00:08:22.760
<v Aaron van Wirdum>Last time in our inscriptions episode, we discussed inscriptions,

00:08:23.040 --> 00:08:28.940
<v Aaron van Wirdum>and that's a way of putting data in the blockchain. And then there were sort of

00:08:28.940 --> 00:08:33.300
<v Aaron van Wirdum>the ordinals, and that lets you supposedly trade

00:08:34.840 --> 00:08:40.840
<v Aaron van Wirdum>ownership or whatever you want to call it. It allows people to pretend that

00:08:40.840 --> 00:08:42.660
<v Aaron van Wirdum>they own whatever data is on the blockchain.

00:08:42.900 --> 00:08:43.100
<v Sjors Provoost>Yes.

00:08:45.330 --> 00:08:50.750
<v Aaron van Wirdum>So Stamps are kind of the equivalent of inscriptions. And there is probably also

00:08:50.750 --> 00:08:55.470
<v Aaron van Wirdum>an equivalent of ordinals, which is traded on Counterparty. But like our

00:08:55.470 --> 00:08:58.330
<v Aaron van Wirdum>inscriptions episode, we're not really going to talk about that. We're just going

00:08:58.330 --> 00:09:01.310
<v Aaron van Wirdum>to talk about how you upload data into the blockchain, right?

00:09:01.610 --> 00:09:05.090
<v Sjors Provoost>Yeah, I would say that Counterparty has a different way of telling the

00:09:05.090 --> 00:09:09.270
<v Sjors Provoost>blockchain, well, not telling the blockchain, telling people who owns which asset

00:09:09.270 --> 00:09:13.130
<v Sjors Provoost>by making transactions on the blockchain that would say, okay, this asset has

00:09:13.130 --> 00:09:18.450
<v Sjors Provoost>moved from A to B. And the way Counterparty does it I don't know exactly it's but

00:09:18.450 --> 00:09:21.710
<v Sjors Provoost>I do know it's different from the way ordinals do it right and it doesn't really

00:09:21.710 --> 00:09:24.530
<v Sjors Provoost>matter I mean the blockchain doesn't care what's happening but from the outside

00:09:24.530 --> 00:09:28.130
<v Sjors Provoost>you see I think in the case of Counterparty you usually see a bunch of OP_RETURN

00:09:28.130 --> 00:09:31.950
<v Sjors Provoost>transactions and if you run the right software that software will know what those

00:09:31.950 --> 00:09:35.970
<v Sjors Provoost>OP_RETURN transactions mean and it will know which who owns which Counterparty

00:09:35.970 --> 00:09:37.510
<v Sjors Provoost>asset and they can show you pictures

00:09:41.190 --> 00:09:46.080
<v Aaron van Wirdum>Stamps are like inscriptions right and that's okay so

00:09:47.170 --> 00:09:52.130
<v Aaron van Wirdum>is a stamp because you've mentioned Counterparty a couple of times is Stamps just

00:09:52.130 --> 00:09:56.750
<v Aaron van Wirdum>using Counterparty in the same way that Rare Pepes was using Counterparty?

00:09:56.750 --> 00:09:59.890
<v Sjors Provoost>That is my understanding. I think the only difference is that you put the word

00:09:59.890 --> 00:10:05.030
<v Sjors Provoost>stamp in front of it like when you're making the asset and you I think you also

00:10:05.030 --> 00:10:09.830
<v Sjors Provoost>should use 64 by 64 pixels so it's kind of a convention on top of Counterparty

00:10:09.830 --> 00:10:12.390
<v Sjors Provoost>that's my understanding, but it uses all the same rails.

00:10:12.390 --> 00:10:15.110
<v Aaron van Wirdum>Okay, so it's not actually that new.

00:10:15.710 --> 00:10:19.690
<v Sjors Provoost>No, I think the new thing is this convention around it that makes it a little bit

00:10:19.690 --> 00:10:21.150
<v Sjors Provoost>more similar to how inscriptions work.

00:10:22.430 --> 00:10:24.610
<v Sjors Provoost>But I don't think the technology itself is new.

00:10:26.310 --> 00:10:29.750
<v Aaron van Wirdum>Okay, I think there's one new thing about it and we'll get to that.

00:10:30.190 --> 00:10:30.390
<v Sjors Provoost>Okay.

00:10:30.550 --> 00:10:35.530
<v Aaron van Wirdum>But let's just first explain how it works.

00:10:35.770 --> 00:10:40.170
<v Sjors Provoost>Yeah, so basically when you create the asset or whatever it is, you have to put

00:10:40.170 --> 00:10:42.490
<v Sjors Provoost>the data on the blockchain. That's hip nowadays.

00:10:42.930 --> 00:10:44.710
<v Aaron van Wirdum>Yeah, so how do you put the data on the blockchain?

00:10:45.460 --> 00:10:51.340
<v Sjors Provoost>So they do that using, well, they do it using Counterparty. And Counterparty has

00:10:51.340 --> 00:10:54.460
<v Sjors Provoost>different ways of doing it depending how big the thing is that you want to put on

00:10:54.460 --> 00:10:59.440
<v Sjors Provoost>the blockchain. So basically, if it's less than 80 bytes, it'll put OP_RETURN on

00:10:59.440 --> 00:11:03.140
<v Sjors Provoost>the blockchain. But if it's more than 80 byte, it's going to fall back to an

00:11:03.140 --> 00:11:08.340
<v Sjors Provoost>older mechanism, which uses fake multi-signature addresses. Fake, raw, or bare

00:11:08.340 --> 00:11:13.070
<v Sjors Provoost>multi-sig. And we described what bare multi-sig is last week. But basically,

00:11:13.530 --> 00:11:18.730
<v Sjors Provoost>it looks to the blockchain looks like it's one out of three multisig.

00:11:19.190 --> 00:11:23.230
<v Sjors Provoost>And the idea is that two of the... And so when you create a multisig address, you

00:11:23.230 --> 00:11:27.170
<v Sjors Provoost>have to specify which public keys can spend it. And it turns out that one of

00:11:27.170 --> 00:11:30.110
<v Sjors Provoost>those public keys is real. So actually the owner.

00:11:30.290 --> 00:11:32.510
<v Aaron van Wirdum>Well, that's new in Stamps, right? Or not?

00:11:32.810 --> 00:11:34.170
<v Sjors Provoost>Yes, but it's not new in Counterparty.

00:11:34.590 --> 00:11:37.250
<v Aaron van Wirdum>Oh, okay. So then there's literally nothing new about Stamps.

00:11:37.930 --> 00:11:38.650
<v Sjors Provoost>Pretty much.

00:11:38.650 --> 00:11:42.610
<v Aaron van Wirdum>Oh, it's just a troll then. I didn't realize it was literally just a troll. Now

00:11:42.610 --> 00:11:43.850
<v Aaron van Wirdum>it sounds like it's just a troll.

00:11:43.850 --> 00:11:47.090
<v Sjors Provoost>Well, it sounds like there's a little bit of extra convention around it but it's

00:11:47.090 --> 00:11:49.030
<v Sjors Provoost>basically repurposing what already existed.

00:11:49.030 --> 00:11:50.710
<v Aaron van Wirdum>Okay, all right well I didn't know that.

00:11:50.710 --> 00:11:54.810
<v Sjors Provoost>So two of the three signatures so one of the three six sorry one of the three

00:11:54.810 --> 00:12:00.150
<v Sjors Provoost>public keys is real so you can actually spend it and and then two of the three

00:12:00.150 --> 00:12:05.880
<v Sjors Provoost>are fake and that means that you get 32 bytes per signature so you get 64

00:12:05.880 --> 00:12:10.460
<v Sjors Provoost>bytes for each of these multisig outputs that you can put real data in. Now, if

00:12:10.460 --> 00:12:15.780
<v Sjors Provoost>you have an image that's, say, 200 bytes, you're going to need four

00:12:15.780 --> 00:12:21.290
<v Sjors Provoost>of these outputs. So you make a transaction that has coins going in, and it has,

00:12:21.330 --> 00:12:27.000
<v Sjors Provoost>on the output side, it will have four, basically, UTXOs, each of

00:12:27.000 --> 00:12:31.940
<v Sjors Provoost>which have two real public keys, sorry, one real public key and two fake public

00:12:31.940 --> 00:12:34.920
<v Sjors Provoost>keys, and that's how you're stuffing the data in. So you can put as much data as

00:12:34.920 --> 00:12:36.180
<v Sjors Provoost>you want on the blockchain this way.

00:12:36.180 --> 00:12:41.180
<v Aaron van Wirdum>Okay, but we've we've discussed some of these things these things before but let

00:12:41.180 --> 00:12:44.120
<v Aaron van Wirdum>me break it down because you've mentioned a couple different things now so

00:12:44.120 --> 00:12:49.880
<v Aaron van Wirdum>Counterparty as a protocol as a layer two protocol for Bitcoin has several

00:12:49.880 --> 00:12:53.700
<v Aaron van Wirdum>different ways of including data on the blockchain

00:12:55.410 --> 00:12:59.810
<v Aaron van Wirdum>Now the first way that people, even before Counterparty I guess, the first way

00:12:59.810 --> 00:13:03.850
<v Aaron van Wirdum>that people were putting data on the blockchain, I don't know if it was the first

00:13:03.850 --> 00:13:08.310
<v Aaron van Wirdum>actually, but the first that I know of was this bare multisig…

00:13:08.850 --> 00:13:09.290
<v Sjors Provoost>Yeah.

00:13:09.290 --> 00:13:13.450
<v Aaron van Wirdum>Trick, essentially that that you're mentioning although probably at first there

00:13:13.450 --> 00:13:15.390
<v Aaron van Wirdum>was not even a single key that was valid.

00:13:15.390 --> 00:13:19.450
<v Sjors Provoost>Right, I think either way I don't remember we did an episode called the OP_RETURN

00:13:19.450 --> 00:13:23.390
<v Sjors Provoost>wars a long time ago where I think we explained all the mechanisms it's possible

00:13:23.390 --> 00:13:26.690
<v Sjors Provoost>that they used OP_RETURN first then there was a limit in OP_RETURN then they

00:13:26.690 --> 00:13:30.530
<v Sjors Provoost>thought okay then we'll just use multisig but it's also possible that they

00:13:30.530 --> 00:13:32.770
<v Sjors Provoost>started with the multisig from the beginning

00:13:33.660 --> 00:13:37.380
<v Aaron van Wirdum>Right, well it's kind of that episode I was sort of rehashing here so…

00:13:37.380 --> 00:13:40.940
<v Sjors Provoost>Yeah, and those would all three be fake so you would have a three of three

00:13:40.940 --> 00:13:44.020
<v Sjors Provoost>multi-sig and all three public keys would be fake.

00:13:44.020 --> 00:13:49.580
<v Aaron van Wirdum>Right, so there was the bare multi-sig way of doing it and then at some point

00:13:49.580 --> 00:13:55.140
<v Aaron van Wirdum>Bitcoin developers said all right use OP_RETURN because that way you can prune

00:13:55.140 --> 00:14:00.060
<v Aaron van Wirdum>the data more easily. So Counterparty actually does use the OP_RETURN, but then

00:14:00.060 --> 00:14:05.420
<v Aaron van Wirdum>if the data doesn't fit within the OP_RETURN, they fall back to the bare

00:14:05.420 --> 00:14:08.300
<v Aaron van Wirdum>multisig, which is sort of older than using OP_RETURN.

00:14:08.540 --> 00:14:08.740
<v Sjors Provoost>Yes.

00:14:08.860 --> 00:14:12.020
<v Aaron van Wirdum>And that way you can still include as much data as you want.

00:14:12.220 --> 00:14:12.680
<v Sjors Provoost>Yes.

00:14:12.940 --> 00:14:18.850
<v Aaron van Wirdum>Okay. So Stamps is data, for example, pictures,

00:14:18.990 --> 00:14:23.230
<v Aaron van Wirdum>pictures most obviously, and Stamps, because they're too big for OP_RETURN,

00:14:23.860 --> 00:14:27.400
<v Aaron van Wirdum>Stamps use Counterparty. They use the Counterparty protocol. But because they're

00:14:27.400 --> 00:14:31.040
<v Aaron van Wirdum>too big for the OP_RETURN option, they use the bare multisig option.

00:14:31.280 --> 00:14:31.520
<v Sjors Provoost>Yes.

00:14:32.820 --> 00:14:37.990
<v Aaron van Wirdum>Okay. And the way they're doing it specifically is they're using, I think you

00:14:37.990 --> 00:14:39.310
<v Aaron van Wirdum>said one out of three multisig.

00:14:39.490 --> 00:14:40.030
<v Sjors Provoost>That's right.

00:14:40.270 --> 00:14:46.210
<v Aaron van Wirdum>Where two of the addresses public keys are actually just fake data. Well,

00:14:46.330 --> 00:14:49.310
<v Aaron van Wirdum>they are the data you're uploading. There are no actual private keys. So you

00:14:49.310 --> 00:14:54.090
<v Aaron van Wirdum>can't spend from these two public keys. But then the remaining public key is

00:14:54.090 --> 00:14:57.650
<v Aaron van Wirdum>actually real and there's a private key. So that would allow you to spend.

00:14:58.430 --> 00:15:02.510
<v Sjors Provoost>Yeah, so that's the biggest difference, I guess. It's actually possible to remove

00:15:02.510 --> 00:15:06.750
<v Sjors Provoost>these things from the UTXO set. So as we've discussed before, the UTXO set is a

00:15:06.750 --> 00:15:11.570
<v Sjors Provoost>set of who owns which coin. And these nodes like to keep this in RAM. They can't

00:15:11.570 --> 00:15:14.710
<v Sjors Provoost>because it's too big, but they prefer to keep as much as possible in RAM because

00:15:14.710 --> 00:15:18.650
<v Sjors Provoost>that makes it quicker to figure out when a new block comes in, whether a coin

00:15:18.650 --> 00:15:22.290
<v Sjors Provoost>that's being mentioned in the block actually exists or not. So to very quickly

00:15:22.290 --> 00:15:26.330
<v Sjors Provoost>look it up and to look up what the script... Now, the blockchain has no idea

00:15:26.330 --> 00:15:30.890
<v Sjors Provoost>whether a public key is fake or not. So when it has a UTXO that mentions three

00:15:30.890 --> 00:15:34.510
<v Sjors Provoost>public keys, it'll simply assume that those three public keys are real. And so

00:15:34.510 --> 00:15:37.570
<v Sjors Provoost>it's going to keep it in memory just like it would keep anything else in memory.

00:15:38.050 --> 00:15:41.610
<v Sjors Provoost>So by using a mechanism like this, you're using up other people's RAM,

00:15:42.330 --> 00:15:42.690
<v Aaron van Wirdum>essentially.

00:15:43.050 --> 00:15:47.590
<v Sjors Provoost>But you can, because you can spend it, you can still remove it from people's RAM

00:15:47.590 --> 00:15:48.130
<v Sjors Provoost>if you want to.

00:15:51.340 --> 00:15:56.400
<v Aaron van Wirdum>I was first going to ask, so this is why Bitcoin developers essentially don't

00:15:56.400 --> 00:15:57.840
<v Aaron van Wirdum>like this method, right?

00:15:58.100 --> 00:15:58.320
<v Sjors Provoost>Yes.

00:15:58.480 --> 00:15:59.120
<v Aaron van Wirdum>Like you.

00:15:59.560 --> 00:16:03.420
<v Sjors Provoost>Yes, and the difference with OP_RETURN is that OP_RETURN, because it is provably

00:16:03.420 --> 00:16:07.750
<v Sjors Provoost>unspendable, because the way the script works is when it sees OP_RETURN, it says

00:16:07.750 --> 00:16:13.060
<v Sjors Provoost>this script is invalid. That's what it means. And therefore, because the node

00:16:13.060 --> 00:16:16.560
<v Sjors Provoost>knows can prove that the script is invalid, it can forget about it because it

00:16:16.560 --> 00:16:19.060
<v Sjors Provoost>knows it can never be spent. So it does not have to hold on to it.

00:16:20.370 --> 00:16:23.530
<v Sjors Provoost>And so anything that comes after the OP_RETURN then is just data you can put in

00:16:23.530 --> 00:16:26.510
<v Sjors Provoost>the blockchain. And it will use disk space if you're storing the whole

00:16:26.510 --> 00:16:29.830
<v Sjors Provoost>blockchain. You have to download it. But you don't have to keep it in memory to

00:16:29.830 --> 00:16:31.730
<v Sjors Provoost>see who owns this particular output.

00:16:33.040 --> 00:16:39.000
<v Aaron van Wirdum>Right. So whatever is stored in the UTXO set, I guess one, [unclear]

00:16:39.000 --> 00:16:44.820
<v Aaron van Wirdum>be pruned. And two, practically speaking, most Bitcoin nodes would keep

00:16:44.820 --> 00:16:45.260
<v Aaron van Wirdum>that in…

00:16:45.690 --> 00:16:48.910
<v Sjors Provoost>RAM, if they have the space to keep it in RAM. Yeah, and if you want your nodes

00:16:48.910 --> 00:16:49.390
<v Sjors Provoost>to be fast.

00:16:49.390 --> 00:16:54.650
<v Aaron van Wirdum>So what happens if everyone would start using Stamps? What's the problem that

00:16:54.650 --> 00:16:57.390
<v Aaron van Wirdum>I will encounter on my node for example?

00:16:57.390 --> 00:17:03.390
<v Sjors Provoost>Well, then you will see the size of the UTXO set grow and it's been remarkably

00:17:03.390 --> 00:17:07.510
<v Sjors Provoost>stable so it's it seems to have reached when you're keeping it in memory on your

00:17:07.510 --> 00:17:13.440
<v Sjors Provoost>node it might peak at about 12 or 13 gigabytes and then I think that was a few

00:17:13.440 --> 00:17:18.540
<v Sjors Provoost>years ago and then it goes down a bit but Yeah, it's been around that space for a

00:17:18.540 --> 00:17:22.840
<v Sjors Provoost>few years. Now, if everybody starts using Stamps and that's the only thing going

00:17:22.840 --> 00:17:25.960
<v Sjors Provoost>on in the blockchain, this thing can grow quite fast.

00:17:26.500 --> 00:17:27.360
<v Aaron van Wirdum>And then what?

00:17:27.580 --> 00:17:30.100
<v Sjors Provoost>I think it's like tens of gigabytes a year or something.

00:17:30.240 --> 00:17:35.200
<v Aaron van Wirdum>It basically means it will require more of my computer's resources to run a node.

00:17:35.320 --> 00:17:39.540
<v Aaron van Wirdum>My computer will get slower if I want to do other stuff. That's basically the

00:17:39.540 --> 00:17:40.080
<v Aaron van Wirdum>problem here.

00:17:40.300 --> 00:17:41.040
<v Sjors Provoost>Yeah, pretty much.

00:17:42.200 --> 00:17:48.020
<v Aaron van Wirdum>Is there a benefit? Because it... So Mike in Space and again I don't know

00:17:48.020 --> 00:17:53.810
<v Aaron van Wirdum>to what extent he's trolling but this sort of perverted benefit is

00:17:53.810 --> 00:17:58.930
<v Aaron van Wirdum>also that it's kept in UTXO. Is this an argument that you think [unclear]

00:17:58.930 --> 00:18:00.230
<v Aaron van Wirdum>steelman—is, is there any…

00:18:00.230 --> 00:18:05.350
<v Sjors Provoost>Yeah, I think the argument then is that it's harder to prune so if your goal is

00:18:05.350 --> 00:18:10.870
<v Sjors Provoost>to put something in the blockchain and keep it there well Even with ordinals,

00:18:11.010 --> 00:18:15.290
<v Sjors Provoost>it's going to be in the blockchain. So in that sense, it's there. And the entire

00:18:15.290 --> 00:18:19.870
<v Sjors Provoost>blockchain should always be available. Now, there have been talks about syncing a

00:18:19.870 --> 00:18:23.490
<v Sjors Provoost>Bitcoin node and then not downloading all the witness, at least from the older

00:18:23.490 --> 00:18:28.130
<v Sjors Provoost>blocks. So in that sense, there might be nodes in the future that will never have

00:18:28.130 --> 00:18:32.430
<v Sjors Provoost>these ordinals on them. And that, from the ordinal point of view, is considered a

00:18:32.430 --> 00:18:35.190
<v Sjors Provoost>good thing. It's like a way to not waste resources.

00:18:35.190 --> 00:18:37.090
<v Aaron van Wirdum>Wait, from whose point of view?

00:18:37.090 --> 00:18:40.690
<v Sjors Provoost>From the ordinals folks point of view they're trying not to waste resources

00:18:40.690 --> 00:18:42.270
<v Sjors Provoost>beyond what they need.

00:18:42.270 --> 00:18:46.130
<v Aaron van Wirdum>Well, but they do want the data to exist on the blockchain right?

00:18:46.130 --> 00:18:50.010
<v Sjors Provoost>Yeah, it exists on the blockchain but nodes don't have to download that part of

00:18:50.010 --> 00:18:53.650
<v Sjors Provoost>the blockchain at least if they're if they're pruning so there's like a special

00:18:53.650 --> 00:18:56.750
<v Sjors Provoost>case if you're running a node that's going to prune things and you use the assume

00:18:56.750 --> 00:19:01.860
<v Sjors Provoost>valid block then you can skip downloading all the witness data. Now, this is a

00:19:01.860 --> 00:19:04.280
<v Sjors Provoost>couple of things we talked about many, many episodes ago.

00:19:04.460 --> 00:19:09.450
<v Aaron van Wirdum>Yeah, but I still want to dig a little bit into this because this does seem to be

00:19:09.450 --> 00:19:14.590
<v Aaron van Wirdum>the main difference between Stamps and inscriptions. I mean, the way people are

00:19:14.590 --> 00:19:18.890
<v Aaron van Wirdum>talking about inscriptions is this idea that 10,000 years in the future and there

00:19:18.890 --> 00:19:20.430
<v Aaron van Wirdum>will be, you know, Mars colonies.

00:19:21.710 --> 00:19:27.310
<v Aaron van Wirdum>When people download the blockchain, they'll still find these original Dickbutt pics.

00:19:28.370 --> 00:19:32.030
<v Sjors Provoost>Yeah, but this is a tricky question, right? And it depends on where these things

00:19:32.030 --> 00:19:35.970
<v Sjors Provoost>are. So you could say, well, the UTXO set is sort of the most durable thing

00:19:35.970 --> 00:19:40.670
<v Sjors Provoost>because it's the database of who owns what coin. So to be in there sounds

00:19:40.670 --> 00:19:44.470
<v Sjors Provoost>possibly as the most durable thing you can do to make sure that everybody running

00:19:44.470 --> 00:19:48.730
<v Sjors Provoost>Bitcoin in the future will have your Dickbutt pic on their computer in RAM, like ready.

00:19:51.090 --> 00:19:54.550
<v Sjors Provoost>And then if you're going back from that, when you look at something like

00:19:54.550 --> 00:19:58.530
<v Sjors Provoost>ordinals, because the data is pruned, every node that is, or sorry, because the

00:19:58.530 --> 00:20:00.890
<v Sjors Provoost>data is only in the blocks, but not in the UTXO set.

00:20:00.890 --> 00:20:01.990
<v Aaron van Wirdum>Also, we're talking about inscriptions.

00:20:02.330 --> 00:20:02.710
<v Sjors Provoost>Yeah.

00:20:02.850 --> 00:20:03.510
<v Aaron van Wirdum>To be specific.

00:20:03.690 --> 00:20:08.150
<v Sjors Provoost>Yeah. So when you're talking about inscriptions, the data is inside the blocks,

00:20:08.190 --> 00:20:13.310
<v Sjors Provoost>but it is never inside the UTXO set. And so if you're pruning the blocks as a

00:20:13.310 --> 00:20:17.090
<v Sjors Provoost>node, so if you're keeping only the most recent 1000 blocks, eventually you throw

00:20:17.090 --> 00:20:19.350
<v Sjors Provoost>these ordinals away. So they're not going to be on your disk anymore.

00:20:20.770 --> 00:20:26.030
<v Aaron van Wirdum>Let me ask you a more specific question, which is more to the point. Is there a

00:20:26.030 --> 00:20:32.020
<v Aaron van Wirdum>potential future where inscriptions that

00:20:32.020 --> 00:20:37.760
<v Aaron van Wirdum>are included in the blockchain today are not available in the

00:20:37.760 --> 00:20:41.780
<v Aaron van Wirdum>future while Bitcoin is still working and running just fine?

00:20:42.460 --> 00:20:46.260
<v Sjors Provoost>That depends very much on your definition of just fine and what you're willing to

00:20:46.260 --> 00:20:51.540
<v Sjors Provoost>tolerate. So there is a possible future where you could say, hey, you know what?

00:20:51.660 --> 00:20:55.460
<v Sjors Provoost>We're not going to sync from the Genesis block. Or at least you could if you

00:20:55.460 --> 00:20:58.860
<v Sjors Provoost>wanted to. You could sync all the way from the Genesis block 50,000 years in the

00:20:58.860 --> 00:21:03.570
<v Sjors Provoost>past and all the way through. But maybe most people have decided, you know what?

00:21:03.570 --> 00:21:08.030
<v Sjors Provoost>We're only going to sync the last 100 years. And that could lead to a situation

00:21:08.030 --> 00:21:12.790
<v Sjors Provoost>where one day, all you have is the last 100 years and nobody has the actual

00:21:12.790 --> 00:21:15.550
<v Sjors Provoost>blockchain all the way back to the 21st century.

00:21:15.830 --> 00:21:19.250
<v Aaron van Wirdum>Right, exactly. But even in that world...

00:21:19.250 --> 00:21:23.660
<v Sjors Provoost>In that world, you'd still have this thing in your UTXO set. Because that's not

00:21:23.660 --> 00:21:24.140
<v Sjors Provoost>going to go away.

00:21:24.240 --> 00:21:24.860
<v Aaron van Wirdum>Now you're going to Stamps.

00:21:25.060 --> 00:21:25.200
<v Sjors Provoost>Okay.

00:21:25.440 --> 00:21:29.840
<v Aaron van Wirdum>Even in that world, we would know that there's only 21 million coins, right?

00:21:30.060 --> 00:21:31.600
<v Sjors Provoost>Yes, you can see the total supply.

00:21:31.780 --> 00:21:35.440
<v Aaron van Wirdum>Yeah, the only thing we wouldn't know for sure is if any coins have been stolen

00:21:35.900 --> 00:21:37.040
<v Aaron van Wirdum>Over 100 years ago.

00:21:37.040 --> 00:21:37.420
<v Sjors Provoost>Exactly.

00:21:37.420 --> 00:21:41.320
<v Aaron van Wirdum>Okay, so that actually sounds to me like that's a feasible past— that's a

00:21:41.320 --> 00:21:42.060
<v Aaron van Wirdum>feasible future.

00:21:42.060 --> 00:21:45.620
<v Sjors Provoost>Yeah, although it could still create lots of conspiracies right because you might

00:21:45.620 --> 00:21:49.560
<v Sjors Provoost>have this really rich family and you would say well we know that five generations

00:21:49.560 --> 00:21:53.560
<v Sjors Provoost>ago you guys stole Bitcoin but nobody can prove it anymore because you killed

00:21:53.560 --> 00:21:57.120
<v Sjors Provoost>everybody who still had the blockchain and so it could still lead to controversy,

00:21:57.120 --> 00:21:59.760
<v Sjors Provoost>but it's a it's you know it's a plausible future right?

00:21:59.760 --> 00:22:04.720
<v Aaron van Wirdum>Yes. Okay, so that's a plausible future okay now let's go to Stamps so is…

00:22:04.640 --> 00:22:10.620
<v Aaron van Wirdum>how does this come, like… So is the claim that it's better to store in

00:22:10.620 --> 00:22:16.340
<v Aaron van Wirdum>UTXO for this reason? For example, now you're steelmanning it. So is this

00:22:16.340 --> 00:22:17.880
<v Aaron van Wirdum>actually a good steelman?

00:22:18.140 --> 00:22:21.780
<v Sjors Provoost>Yeah, this would be the argument. And we'll get later to why this doesn't work

00:22:21.780 --> 00:22:25.860
<v Sjors Provoost>either. But at least it's plausible that in this case, people still have to keep

00:22:25.860 --> 00:22:31.560
<v Sjors Provoost>the list of who owns which coin. Who owns which coin has to be kept by

00:22:31.560 --> 00:22:35.780
<v Sjors Provoost>nodes in some way either in memory or on disk because you never know if it ever

00:22:35.780 --> 00:22:40.440
<v Sjors Provoost>gets spent. Yeah, especially with the way they're doing it now because it is

00:22:40.440 --> 00:22:41.920
<v Sjors Provoost>actually one of the keys is valid.

00:22:42.940 --> 00:22:48.920
<v Aaron van Wirdum>Right, okay so in this plausible future where people are only keeping

00:22:48.920 --> 00:22:54.200
<v Aaron van Wirdum>track of the last hundred years and other than that Bitcoin doesn't change I

00:22:54.200 --> 00:22:59.520
<v Aaron van Wirdum>guess we should sort of add that then it sort of makes sense to use Stamps if you

00:22:59.520 --> 00:23:03.150
<v Aaron van Wirdum>want to make sure that people will still find your Dickbutt picture.

00:23:03.150 --> 00:23:05.010
<v Sjors Provoost>Yeah, but but even in the shorter term…

00:23:05.010 --> 00:23:05.750
<v Aaron van Wirdum>years from now.

00:23:05.750 --> 00:23:10.090
<v Sjors Provoost>Even in the shorter term there are proposals where if you want to prune your node

00:23:10.090 --> 00:23:14.510
<v Sjors Provoost>anyway so if you don't want to keep all the old blocks you will right now when

00:23:14.510 --> 00:23:17.930
<v Sjors Provoost>you when you turn on this pruning feature you will download the whole blockchain

00:23:17.930 --> 00:23:22.230
<v Sjors Provoost>you will verify the whole blockchain but you will toss away the old blocks once

00:23:22.230 --> 00:23:25.650
<v Sjors Provoost>you're done with them and there's a second feature that we discussed many many

00:23:25.650 --> 00:23:31.500
<v Sjors Provoost>episodes ago called assume UTXO sorry assume valid not assume UTXO assume valid

00:23:31.500 --> 00:23:35.680
<v Sjors Provoost>is a feature that says when you're starting up this new node, and all nodes do

00:23:35.680 --> 00:23:39.300
<v Sjors Provoost>that now by default, we're not going to check any signatures before, I don't

00:23:39.300 --> 00:23:45.030
<v Sjors Provoost>know, six months ago or a few months ago. With some security assumptions around

00:23:45.030 --> 00:23:48.610
<v Sjors Provoost>that, you can turn that off. But if you do turn that on, which is the case by

00:23:48.610 --> 00:23:54.590
<v Sjors Provoost>default, you're not validating the witness data for all the blocks. And so then

00:23:54.940 --> 00:23:59.020
<v Sjors Provoost>the idea would be that if you're pruning anyway, It is completely pointless to

00:23:59.020 --> 00:24:02.680
<v Sjors Provoost>download witness data, not verify it, and then delete it. You're literally

00:24:02.680 --> 00:24:07.290
<v Sjors Provoost>downloading something, not looking at it, and then throwing it away. Well, you're

00:24:07.290 --> 00:24:11.590
<v Sjors Provoost>looking at some aspects of it, but you're not looking at most of it. And so one

00:24:11.590 --> 00:24:16.360
<v Sjors Provoost>concrete proposal that's already people are trying to implement is to just not

00:24:16.360 --> 00:24:20.520
<v Sjors Provoost>download the witness data for all blocks. And so then you can say, well, but then

00:24:20.520 --> 00:24:25.200
<v Sjors Provoost>your ordinals won't be downloaded by all new nodes. Only some lucky nodes will

00:24:25.200 --> 00:24:26.580
<v Sjors Provoost>have the ordinals in it.

00:24:27.890 --> 00:24:31.290
<v Sjors Provoost>Which is a good thing if you're trying not to waste people's resources but it's a

00:24:31.290 --> 00:24:34.110
<v Sjors Provoost>bad thing if you somehow want to be stored

00:24:34.750 --> 00:24:40.370
<v Aaron van Wirdum>your point being that it might not only like the Stamps

00:24:40.370 --> 00:24:44.250
<v Aaron van Wirdum>argument if we're steelmanning it doesn't only make sense 10 000 years into the

00:24:44.250 --> 00:24:48.200
<v Aaron van Wirdum>future when people are only downloading the last hundred years it might actually

00:24:48.200 --> 00:24:52.280
<v Aaron van Wirdum>make sense in a couple years in the future when people are not downloading

00:24:52.280 --> 00:24:54.660
<v Aaron van Wirdum>witnesses that are older than six months.

00:24:54.660 --> 00:24:55.180
<v Sjors Provoost>Yes.

00:24:55.180 --> 00:24:56.640
<v Aaron van Wirdum>Right, that's the steel man.

00:24:56.640 --> 00:24:59.740
<v Sjors Provoost>Exactly. They will still be around because nobody's going to delete the

00:24:59.740 --> 00:25:02.200
<v Sjors Provoost>blockchain and there's very good reasons why you want to make sure that the

00:25:02.200 --> 00:25:08.080
<v Sjors Provoost>blockchain stays in existence and is widely available but… that that might be

00:25:08.080 --> 00:25:08.480
<v Sjors Provoost>their worry.

00:25:08.510 --> 00:25:13.970
<v Aaron van Wirdum>All right so that's the steel man for Stamps now

00:25:13.970 --> 00:25:19.720
<v Aaron van Wirdum>let's… Well, it's not a straw man, I think. It's a legitimate...

00:25:19.960 --> 00:25:20.720
<v Sjors Provoost>We're gonna…

00:25:20.680 --> 00:25:26.470
<v Aaron van Wirdum>No, it's also not a concern. But does this... I just want to

00:25:26.470 --> 00:25:29.490
<v Aaron van Wirdum>question, does this steel man really hold up?

00:25:29.790 --> 00:25:35.710
<v Sjors Provoost>Well, I would describe this phenomena as Utreexo accelerationism,

00:25:35.730 --> 00:25:37.110
<v Sjors Provoost>if we want to give it a name.

00:25:37.310 --> 00:25:38.370
<v Aaron van Wirdum>Right, I was thinking.

00:25:38.710 --> 00:25:44.590
<v Sjors Provoost>Really, this problem that we want to keep track of who owns which coins... This

00:25:44.590 --> 00:25:49.890
<v Sjors Provoost>has been known to be a problem that does not have a limit. Because there could be

00:25:49.890 --> 00:25:55.170
<v Sjors Provoost>an infinite number of coins. And every year, tens of gigabytes of new coins could

00:25:55.170 --> 00:25:58.530
<v Sjors Provoost>be created that people have to keep track of. Even if it's on a disk at some

00:25:58.530 --> 00:26:04.510
<v Sjors Provoost>point, if you have 200 gigabytes of things, you can't prune it. And it can

00:26:04.510 --> 00:26:08.530
<v Sjors Provoost>grow forever. So something that cannot be pruned and can grow forever is bad,

00:26:08.750 --> 00:26:13.900
<v Sjors Provoost>generally. And so there is a solution to that problem, which is called

00:26:13.900 --> 00:26:17.140
<v Sjors Provoost>Utreexo, which we did a whole episode on two years ago.

00:26:17.460 --> 00:26:17.640
<v Aaron van Wirdum>Yeah.

00:26:18.900 --> 00:26:20.760
<v Aaron van Wirdum>What's the episode number?

00:26:20.980 --> 00:26:23.040
<v Sjors Provoost>I don't know, but just look for Utreexo.

00:26:23.060 --> 00:26:24.880
<v Aaron van Wirdum>I'm pretty sure it's just called Utreexo.

00:26:25.100 --> 00:26:29.780
<v Sjors Provoost>Yeah. So it's a U and then a tree, like in the thing with leaves, and then XO.

00:26:30.000 --> 00:26:35.740
<v Aaron van Wirdum>Right. So Utreexo would be a way to essentially prune the UTXO set, right?

00:26:35.960 --> 00:26:41.820
<v Sjors Provoost>That's right. And the short version of it is that instead of every

00:26:41.820 --> 00:26:47.780
<v Sjors Provoost>node keeping track of which coin is where, the burden of evidence is sort

00:26:47.780 --> 00:26:51.680
<v Sjors Provoost>of turned around. So you're telling if you want to spend a coin, you need to

00:26:51.680 --> 00:26:55.840
<v Sjors Provoost>prove that this coin exists. I'm not going to remember that this coin exists. And

00:26:55.840 --> 00:27:00.200
<v Sjors Provoost>there's some mathematical magic there. That means that I as a node operator only

00:27:00.200 --> 00:27:05.270
<v Sjors Provoost>have to remember like a kilobyte worth of data, a bunch of Merkle trees or some

00:27:05.270 --> 00:27:10.390
<v Sjors Provoost>other mechanism. And then if you send me a transaction, including a piece of

00:27:10.390 --> 00:27:14.230
<v Sjors Provoost>proof, then I can check that this transaction is valid and spending a coin that

00:27:14.230 --> 00:27:17.550
<v Sjors Provoost>exists. So you're basically hiding the whole UTXO set inside a Merkle tree.

00:27:18.690 --> 00:27:24.620
<v Aaron van Wirdum>Yeah. So even if... The argument that it's better to put it in

00:27:24.620 --> 00:27:30.320
<v Aaron van Wirdum>the UTXO set is superior because it can't be pruned, Even that is not really true

00:27:30.320 --> 00:27:35.660
<v Aaron van Wirdum>because there are solutions to prune the UTXO set, except they're not in Bitcoin

00:27:35.660 --> 00:27:36.260
<v Aaron van Wirdum>yet.

00:27:36.560 --> 00:27:40.860
<v Sjors Provoost>No, and I think within the next couple of weeks, there's going to be a demo of

00:27:40.860 --> 00:27:45.680
<v Sjors Provoost>this software. So people are working on it, but this would just be a demo. And of

00:27:45.680 --> 00:27:49.500
<v Sjors Provoost>course, ultimately, something like this, in order to really get rid of the UTXO

00:27:49.500 --> 00:27:53.620
<v Sjors Provoost>set, it would have to be a soft fork that is pretty dramatic. So this is not

00:27:53.620 --> 00:27:56.600
<v Sjors Provoost>something that would happen in the next year or so, probably not even in the next

00:27:56.600 --> 00:28:00.600
<v Sjors Provoost>decade or so. Because there is a pretty serious downside to it.

00:28:00.600 --> 00:28:06.080
<v Aaron van Wirdum>It might also depend on how many people are going to use Stamps. As you said,

00:28:06.840 --> 00:28:08.680
<v Aaron van Wirdum>Stamps might be sort of an acceleration.

00:28:10.590 --> 00:28:12.290
<v Aaron van Wirdum>Motivation behind Utreexo.

00:28:12.450 --> 00:28:16.110
<v Sjors Provoost>There's always a balance when you want to do a new piece of functionality between

00:28:16.110 --> 00:28:21.490
<v Sjors Provoost>how desperately do you need it and how scary is it. And this is scarier than

00:28:21.490 --> 00:28:25.510
<v Sjors Provoost>something like Taproot, I would say. And we don't really need it at the moment.

00:28:26.170 --> 00:28:31.810
<v Sjors Provoost>But, you know, if the dynamics change, then... So the downside of this

00:28:31.810 --> 00:28:36.510
<v Sjors Provoost>proposal, Utreexo, is that it's going to make blocks bigger. So that creates a

00:28:36.510 --> 00:28:42.310
<v Sjors Provoost>trade-off where you need more bandwidth. And that's a pretty big deal in some countries.

00:28:42.510 --> 00:28:42.870
<v Aaron van Wirdum>Right.

00:28:43.130 --> 00:28:43.890
<v Sjors Provoost>But so is storage.

00:28:44.370 --> 00:28:48.670
<v Aaron van Wirdum>Okay. Well, we've done a whole episode on Utreexo, so if people want to know more

00:28:48.670 --> 00:28:52.050
<v Aaron van Wirdum>about that, you should probably just go back to that episode and hear all the details.

00:28:52.050 --> 00:28:55.910
<v Sjors Provoost>But if we go to a world where you only download the last 100,000 or the last 100

00:28:55.910 --> 00:29:00.540
<v Sjors Provoost>years of blocks or even less, and you're not holding on to the UTXO set… That

00:29:00.540 --> 00:29:03.640
<v Sjors Provoost>means that your Bitcoin node is always going to be the same size. The blockchain

00:29:03.640 --> 00:29:08.140
<v Sjors Provoost>is always going to be the same size because it's only just the last 100 years,

00:29:08.340 --> 00:29:13.580
<v Sjors Provoost>for example. So I don't know how many terabytes that is, but that's it. And the

00:29:13.580 --> 00:29:19.180
<v Sjors Provoost>UTXO set is always going to be one, like a kilobyte. And then the system can be

00:29:19.180 --> 00:29:21.900
<v Sjors Provoost>like that forever. So that's kind of a nice potential future.

00:29:23.080 --> 00:29:25.360
<v Aaron van Wirdum>Okay, letting go of the future for one second.

00:29:25.560 --> 00:29:29.850
<v Sjors Provoost>But that would mean that any of these things, ordinals would be gone. Or at least

00:29:29.850 --> 00:29:34.610
<v Sjors Provoost>they wouldn't be gone. They would just not be on your hard disk unless you want

00:29:34.610 --> 00:29:39.050
<v Sjors Provoost>them to be. So if you want to reveal them, somebody can give you proof and they

00:29:39.050 --> 00:29:43.470
<v Sjors Provoost>can show that indeed this picture exists on the blockchain in some way that you

00:29:43.470 --> 00:29:46.470
<v Sjors Provoost>define existing, but it wouldn't actually be on your disk anymore.

00:29:48.480 --> 00:29:53.600
<v Sjors Provoost>Although you could say like, if something is in a Merkle tree, is it really there?

00:29:55.060 --> 00:29:56.740
<v Sjors Provoost>That's a nice philosophical question.

00:29:57.290 --> 00:29:59.870
<v Aaron van Wirdum>If a Merkle tree falls in the forest,

00:30:01.140 --> 00:30:05.700
<v Aaron van Wirdum>Okay, letting go of the future for one second. One thing we haven't mentioned, I

00:30:05.700 --> 00:30:11.100
<v Aaron van Wirdum>think, is just the difference in cost between Stamps and inscriptions.

00:30:12.020 --> 00:30:14.680
<v Aaron van Wirdum>And essentially, inscriptions are a lot cheaper, right?

00:30:14.900 --> 00:30:15.160
<v Sjors Provoost>Oh, yeah.

00:30:15.300 --> 00:30:18.700
<v Aaron van Wirdum>Because inscriptions use the SegWit discount, which we discussed in our

00:30:18.700 --> 00:30:19.160
<v Aaron van Wirdum>inscriptions…

00:30:19.340 --> 00:30:22.580
<v Sjors Provoost>Yeah, they are cheaper in two ways, exactly. They use the SegWit discount, so

00:30:22.580 --> 00:30:25.840
<v Sjors Provoost>that makes them a factor four cheaper. Well, in three ways, I guess. I think

00:30:25.840 --> 00:30:29.800
<v Sjors Provoost>they're also cheaper because they used like... Transaction itself more

00:30:29.800 --> 00:30:34.920
<v Sjors Provoost>efficiently like it's not because you're not adding this this third multi-sig key

00:30:34.920 --> 00:30:39.940
<v Sjors Provoost>for every output so like a third of the data is being used to repeat the

00:30:39.940 --> 00:30:45.180
<v Sjors Provoost>the public key that's real when you make this Counterparty thing so if you have

00:30:45.180 --> 00:30:49.020
<v Sjors Provoost>for example six outputs then each of these outputs will have one real key in them

00:30:49.020 --> 00:30:52.890
<v Sjors Provoost>so that's one third of your data right which you are paying fees for and the

00:30:52.890 --> 00:30:57.080
<v Sjors Provoost>third way is that you're not dealing with the sigops limit.

00:30:57.320 --> 00:31:02.000
<v Aaron van Wirdum>Yes, you want to get to why the block failed, but I want to make sure we're done

00:31:02.000 --> 00:31:07.940
<v Aaron van Wirdum>with the whole Stamps thing. And it's been a bit all over the place with the pros

00:31:07.940 --> 00:31:13.120
<v Aaron van Wirdum>and the cons and the comparisons. But one thing we sort of mentioned, but it's

00:31:13.120 --> 00:31:19.090
<v Aaron van Wirdum>worth repeating, is that a potential kind of benefit of Stamps

00:31:19.090 --> 00:31:23.190
<v Aaron van Wirdum>is that they can also be removed, spent.

00:31:23.830 --> 00:31:25.790
<v Sjors Provoost>Right, that's using that one valid key.

00:31:25.790 --> 00:31:29.990
<v Aaron van Wirdum>Yeah, so if you use that one valid key to actually spend the funds that were in

00:31:29.990 --> 00:31:35.170
<v Aaron van Wirdum>there then the UTXO set disappears again. The stamp disappears from the UTXO set,

00:31:35.170 --> 00:31:39.160
<v Sjors Provoost>yes, which is the same for the ordinals for the inscriptions.

00:31:39.160 --> 00:31:41.700
<v Aaron van Wirdum>Is it? No it's not.

00:31:41.700 --> 00:31:43.140
<v Sjors Provoost>Yeah, you can just burn them you can…

00:31:43.140 --> 00:31:45.720
<v Aaron van Wirdum>Well, okay yeah now you're talking about Ordinals.

00:31:47.880 --> 00:31:51.140
<v Sjors Provoost>Well, the inscription is not even using the UTXO set in the first place.

00:31:51.360 --> 00:31:57.300
<v Aaron van Wirdum>Yes, I know. So Stamps is using the UTXO set, but it can also be

00:31:57.300 --> 00:32:01.040
<v Aaron van Wirdum>removed from the UTXO set if the coins are spent.

00:32:02.510 --> 00:32:06.010
<v Aaron van Wirdum>Right? I think there was one more thing I wanted to say about this. Oh, yeah. So

00:32:06.010 --> 00:32:10.970
<v Aaron van Wirdum>that's kind of, I don't know if it's funny or interesting or dumb or all of the

00:32:10.970 --> 00:32:16.670
<v Aaron van Wirdum>above, but it also means that you can create a stamp.

00:32:17.260 --> 00:32:23.220
<v Aaron van Wirdum>And then I can sell the stamp to you. Well, I mean, as dumb as we can

00:32:23.220 --> 00:32:27.180
<v Aaron van Wirdum>pretend that I sold the stamp to you by sending you a Counterparty transaction.

00:32:27.520 --> 00:32:32.810
<v Aaron van Wirdum>But then afterwards, since I have the private key that can remove the stamp from

00:32:32.810 --> 00:32:36.310
<v Aaron van Wirdum>the UTXO, I can still... Remove it even though…

00:32:36.310 --> 00:32:39.630
<v Sjors Provoost>This part I'm not sure whether that's true it could be it could be that you're

00:32:39.630 --> 00:32:42.290
<v Sjors Provoost>transferring everything but then I guess then you would have to rebroadcast the

00:32:42.290 --> 00:32:45.990
<v Sjors Provoost>whole the whole picture that would be really inefficient so yeah I'm guessing you

00:32:45.990 --> 00:32:50.230
<v Sjors Provoost>can as the original creator remove it from the UTXO set it's not as the current owner.

00:32:50.230 --> 00:32:55.070
<v Aaron van Wirdum>As far as I understand. Yes, exactly. Yeah, so that's we we both immediately

00:32:55.070 --> 00:32:59.230
<v Aaron van Wirdum>thought of the Banksy painting which would be the equivalent so you sell it and

00:32:59.230 --> 00:33:03.140
<v Aaron van Wirdum>then you destroy it. Yeah, okay before okay I know you really really want to get

00:33:03.140 --> 00:33:08.720
<v Aaron van Wirdum>to the invalid block. First of all Sjors, give us your expert opinion. What

00:33:08.720 --> 00:33:10.960
<v Aaron van Wirdum>should people use inscriptions or Stamps?

00:33:10.960 --> 00:33:11.560
<v Sjors Provoost>Neither.

00:33:11.560 --> 00:33:14.420
<v Aaron van Wirdum>Well, pick one though. You gotta pick one.

00:33:15.440 --> 00:33:20.800
<v Aaron van Wirdum>People are desperate to upload their Dickbutts onto the blockchain.

00:33:18.500 --> 00:33:19.100
<v Sjors Provoost>I cannot…

00:33:20.800 --> 00:33:22.240
<v Sjors Provoost>No, I can't see into the mind.

00:33:22.360 --> 00:33:23.080
<v Aaron van Wirdum>Which protocols should they use?

00:33:23.140 --> 00:33:26.500
<v Sjors Provoost>I can't see into the mind of why they would want to do this. So I can't make that

00:33:26.500 --> 00:33:29.220
<v Sjors Provoost>choice to them. We've explained the differences. It does actually, before we get

00:33:29.220 --> 00:33:33.160
<v Sjors Provoost>to the block, raise one other issue or one discussion that's been renewed now.

00:33:33.320 --> 00:33:37.460
<v Sjors Provoost>That even happened with ordinals. Sorry, with inscriptions. The discussion is we

00:33:37.460 --> 00:33:43.350
<v Sjors Provoost>have a limit on OP_RETURN. Right for 80 bytes and the question is for

00:33:43.350 --> 00:33:47.170
<v Sjors Provoost>in the mempool and the question is should we just get rid of that limit because

00:33:47.170 --> 00:33:52.250
<v Sjors Provoost>you know or at least increase it to something really large for two reasons one is

00:33:52.250 --> 00:33:56.230
<v Sjors Provoost>that these ordinals are getting around that limit anyway or these inscriptions

00:33:56.230 --> 00:34:00.310
<v Sjors Provoost>are getting around the limit anyway and if people do use OP_RETURN then at least

00:34:00.310 --> 00:34:05.160
<v Sjors Provoost>they're paying four times as many fees per byte that they're using And the other

00:34:05.160 --> 00:34:08.840
<v Sjors Provoost>is that then they would maybe stop using these bare multisigs.

00:34:09.000 --> 00:34:12.480
<v Aaron van Wirdum>But they wouldn't, though, because that's apparently the point for them. They

00:34:12.480 --> 00:34:15.720
<v Aaron van Wirdum>want it in the UTXO set. That's the selling point.

00:34:15.860 --> 00:34:19.220
<v Sjors Provoost>Yeah, and then they would have to modify the philosophy of Counterparty itself

00:34:19.220 --> 00:34:23.420
<v Sjors Provoost>because, as far as I know, Counterparty tries to use the most efficient way to

00:34:23.420 --> 00:34:28.730
<v Sjors Provoost>put stuff on the blockchain and by making these pictures slightly bigger. It has

00:34:28.730 --> 00:34:33.510
<v Sjors Provoost>to fall back to the inefficient way, but if we were to raise the OP_RETURN limit,

00:34:33.710 --> 00:34:37.270
<v Sjors Provoost>then Counterparty could just always use OP_RETURN, and there would be no reason

00:34:37.270 --> 00:34:41.190
<v Sjors Provoost>to use multisig unless you deliberately run an old version of Counterparty

00:34:41.190 --> 00:34:45.770
<v Sjors Provoost>software or something contrived like that. But it sounds like, given the

00:34:45.770 --> 00:34:47.290
<v Sjors Provoost>motivation, they might actually do that.

00:34:49.070 --> 00:34:54.110
<v Aaron van Wirdum>I mean that that's the selling point right it seems like okay so okay you want to

00:34:54.110 --> 00:34:57.650
<v Aaron van Wirdum>get to the invalid block desperately before we get there I'll say it use

00:34:57.650 --> 00:35:02.050
<v Aaron van Wirdum>inscriptions don't use Stamps it's ridiculous it's more expensive it's annoying

00:35:02.050 --> 00:35:07.510
<v Aaron van Wirdum>to fill the UTXO set with crap please if you must upload your Dickbutt use

00:35:07.510 --> 00:35:11.770
<v Aaron van Wirdum>inscriptions so… anyway why was there an invalid block?

00:35:12.710 --> 00:35:18.630
<v Sjors Provoost>Well, yes. So on April Fool's Day of all times, F2Pool produced a block that

00:35:18.630 --> 00:35:24.550
<v Sjors Provoost>was invalid with the message back—bad sigops count or something like that. And

00:35:24.550 --> 00:35:29.390
<v Sjors Provoost>that means this sigops limit was violated. And as we explained last week, there

00:35:29.390 --> 00:35:32.750
<v Sjors Provoost>is this extra limit in the block, not just the size, but the...

00:35:32.750 --> 00:35:36.050
<v Aaron van Wirdum>First of all, first of all, how do we know there was an invalid block? If it's

00:35:36.050 --> 00:35:37.810
<v Aaron van Wirdum>invalid, why do we know about it even?

00:35:38.690 --> 00:35:41.350
<v Sjors Provoost>Well, if your node sees it, it'll tell you it's invalid.

00:35:42.560 --> 00:35:45.920
<v Sjors Provoost>And the reason your node saw it, there can be two reasons for that. One reason

00:35:45.920 --> 00:35:49.400
<v Sjors Provoost>could be that, well, you happen to have been connected to the miner, they sent it

00:35:49.400 --> 00:35:53.300
<v Sjors Provoost>to you, or you were connected to somebody evil, and they sent it to you even

00:35:53.300 --> 00:35:57.000
<v Sjors Provoost>though they knew it was valid. Or, and this is what happened, at least in case of

00:35:57.000 --> 00:36:02.250
<v Sjors Provoost>my own node, you received it through a compact block. And I don't think we've

00:36:02.250 --> 00:36:05.750
<v Sjors Provoost>done an episode about compact blocks, so we can do that some other time. But the

00:36:05.750 --> 00:36:08.950
<v Sjors Provoost>idea of a compact block is to send the block as fast as possible through the

00:36:08.950 --> 00:36:13.960
<v Sjors Provoost>network, not wasting as little time as possible while not making it unsafe,

00:36:14.260 --> 00:36:19.760
<v Sjors Provoost>basically. And so what you do is when you receive a compact block, you check the

00:36:19.760 --> 00:36:25.040
<v Sjors Provoost>header. And if the header has enough work, then you will send on the message.

00:36:25.420 --> 00:36:30.420
<v Sjors Provoost>So you send it first and then you check the block. And that's why that block

00:36:30.420 --> 00:36:30.980
<v Sjors Provoost>would have been spread.

00:36:31.420 --> 00:36:31.620
<v Aaron van Wirdum>Okay.

00:36:31.900 --> 00:36:34.680
<v Sjors Provoost>There's more to compact blocks, but that's the most important aspect of it here.

00:36:34.800 --> 00:36:39.690
<v Aaron van Wirdum>Okay. So that's why we know, or at least that's why you know. No, it was posted

00:36:39.690 --> 00:36:44.280
<v Aaron van Wirdum>probably in… message forums and stuff, right? People know about this block. I

00:36:44.280 --> 00:36:45.440
<v Aaron van Wirdum>mean, I didn't, but...

00:36:45.440 --> 00:36:48.300
<v Sjors Provoost>Yeah, the other way you would find out about the block is you read about it, and

00:36:48.300 --> 00:36:51.220
<v Sjors Provoost>some people have posted the full block, so you can download it and send it to

00:36:51.220 --> 00:36:53.160
<v Sjors Provoost>your own node and see what your node thinks of it.

00:36:53.260 --> 00:36:57.080
<v Aaron van Wirdum>Okay, so there was an invalid block, and you mentioned the sigops limit was

00:36:57.080 --> 00:36:58.020
<v Aaron van Wirdum>reached. Is that what you said?

00:36:58.200 --> 00:37:03.560
<v Sjors Provoost>Yeah, so as we explained last week, when you use raw multisig… what happens is

00:37:03.560 --> 00:37:08.320
<v Sjors Provoost>that it counts as 20 sigops. So there's this counter called the sigops counter,

00:37:08.580 --> 00:37:14.350
<v Sjors Provoost>and each raw multisig counts as 20 of these units. We'll just call them

00:37:14.350 --> 00:37:19.590
<v Sjors Provoost>units. And, well, with SegWit, you know, that was multiplied by 4, but then the

00:37:19.590 --> 00:37:23.190
<v Sjors Provoost>maximum was also multiplied by 4, so we can kind of ignore that. We can just say

00:37:23.190 --> 00:37:27.430
<v Sjors Provoost>it counts as 20 points, whereas a normal single signature transaction counts as 1

00:37:27.430 --> 00:37:31.720
<v Sjors Provoost>point. So even if you're only using a one-of-one multisig, you're still using

00:37:31.720 --> 00:37:37.380
<v Sjors Provoost>those 20 points. So these Counterparty transactions are using 20 points for

00:37:37.450 --> 00:37:42.810
<v Sjors Provoost>each output. So not for each transaction, but for each output. And there's 20,000

00:37:42.810 --> 00:37:48.210
<v Sjors Provoost>points to a block. That's the limit. So you can have 1,000 of these things in

00:37:48.210 --> 00:37:50.190
<v Sjors Provoost>there. Now, one single...

00:37:50.190 --> 00:37:51.010
<v Aaron van Wirdum>Go on.

00:37:51.370 --> 00:37:55.810
<v Sjors Provoost>Today, we looked at one example of these Counterparty transactions, and we saw it

00:37:55.810 --> 00:38:01.330
<v Sjors Provoost>was creating six outputs for like a... Tiny, tiny picture. And so that is

00:38:01.330 --> 00:38:06.710
<v Sjors Provoost>6 times 20 is 120

00:38:06.710 --> 00:38:08.030
<v Sjors Provoost>sigops.

00:38:09.380 --> 00:38:15.240
<v Aaron van Wirdum>So that means there can be less than 200 of these pictures

00:38:15.240 --> 00:38:15.940
<v Aaron van Wirdum>in a block?

00:38:16.320 --> 00:38:16.860
<v Sjors Provoost>Exactly.

00:38:17.600 --> 00:38:22.220
<v Aaron van Wirdum>It's never a good idea to do math live, right? But I'm saying that right, I think?

00:38:23.810 --> 00:38:24.730
<v Sjors Provoost>Yeah, I think so.

00:38:26.660 --> 00:38:28.900
<v Sjors Provoost>Less than less than 200 per block.

00:38:28.900 --> 00:38:33.500
<v Aaron van Wirdum>Right, so and that's what happened so there were more were there more 200?

00:38:33.500 --> 00:38:37.920
<v Sjors Provoost>So this is the tricky part I've been trying today and yesterday to figure out

00:38:37.920 --> 00:38:41.800
<v Sjors Provoost>exactly how many of these sigops points were used because Bitcoin Core won't tell

00:38:41.800 --> 00:38:45.340
<v Sjors Provoost>you the only thing Bitcoin Core will do is it it'll count them internally and

00:38:45.340 --> 00:38:48.580
<v Sjors Provoost>when there's too many it says too many and it stops counting so it doesn't give

00:38:48.580 --> 00:38:51.900
<v Sjors Provoost>you the total doesn't say where they are Now you can use other tools to try and

00:38:51.900 --> 00:38:56.520
<v Sjors Provoost>figure that out. And I'm not super good at those tools. So anyway I've been

00:38:56.520 --> 00:39:00.400
<v Sjors Provoost>counting, I think the highest number I was able to get at was with the SegWit

00:39:00.400 --> 00:39:06.200
<v Sjors Provoost>counting, which is four times the limit. I got 79,828 in total, which is

00:39:06.200 --> 00:39:09.990
<v Sjors Provoost>less than 80,000, which means I'm counting something wrong.

00:39:10.190 --> 00:39:10.950
<v Aaron van Wirdum>Can you repeat that?

00:39:11.490 --> 00:39:13.970
<v Sjors Provoost>79,828 points.

00:39:14.370 --> 00:39:15.630
<v Aaron van Wirdum>Wait, wasn't the limit?

00:39:15.890 --> 00:39:21.790
<v Sjors Provoost>Well, with SegWit, the limit is 80,000. So, and then you have to multiply by

00:39:21.790 --> 00:39:27.210
<v Sjors Provoost>four, the punishment. But if I look only at those OP_RETURN transactions, those

00:39:27.210 --> 00:39:29.590
<v Sjors Provoost>bare multisig transactions,

00:39:31.060 --> 00:39:34.460
<v Sjors Provoost>then I find how many?

00:39:36.510 --> 00:39:42.490
<v Sjors Provoost>890 bare multisig transactions. So that's not the number of assets, because you

00:39:42.490 --> 00:39:46.070
<v Sjors Provoost>probably have to divide by five or six, depending on how big they are. But that's

00:39:46.070 --> 00:39:50.930
<v Sjors Provoost>pretty close to the limit. Right, because they count, in SegWit, they count as 20

00:39:50.930 --> 00:39:56.010
<v Sjors Provoost>times 4, basically. So you get 71,000 points just for all this Counterparty

00:39:56.010 --> 00:39:59.330
<v Sjors Provoost>stuff. I'm saying Counterparty stuff that might be somebody else using bare

00:39:59.330 --> 00:40:01.930
<v Sjors Provoost>multisig, but I'm just going to assume it was only the Counterparty people.

00:40:02.250 --> 00:40:02.490
<v Aaron van Wirdum>Right.

00:40:02.890 --> 00:40:07.450
<v Sjors Provoost>So, you know, 71,000 out of 80,000 was already used for this Counterparty stuff.

00:40:07.850 --> 00:40:10.790
<v Sjors Provoost>And then, of course, there's other transactions out there that also count.

00:40:11.050 --> 00:40:16.770
<v Aaron van Wirdum>So in short, this block was invalid because people were stamping too

00:40:16.770 --> 00:40:19.210
<v Aaron van Wirdum>much. That's what it sort of sounds like.

00:40:19.370 --> 00:40:24.570
<v Sjors Provoost>So if a miner is configured correctly, it won't produce an invalid block. It will

00:40:24.570 --> 00:40:29.770
<v Sjors Provoost>simply just not include all the pictures. It has to decide what to throw out. So

00:40:29.770 --> 00:40:33.390
<v Sjors Provoost>ideally, when you create a block as a miner, you just want to look at the highest

00:40:33.390 --> 00:40:38.440
<v Sjors Provoost>fees and sort them from high to low. But unfortunately, when all these pictures

00:40:38.440 --> 00:40:41.900
<v Sjors Provoost>are in there, you really need to make sure that you're taking into account that

00:40:41.900 --> 00:40:45.700
<v Sjors Provoost>you don't go over this limit. And Bitcoin Core will do that for you if you let it

00:40:45.700 --> 00:40:49.580
<v Sjors Provoost>construct a block. And some miners probably use Bitcoin Core to create the block,

00:40:49.660 --> 00:40:53.380
<v Sjors Provoost>but other miners think they can do it more efficiently and they might be correct

00:40:53.380 --> 00:40:53.820
<v Sjors Provoost>about that.

00:40:55.090 --> 00:40:58.490
<v Sjors Provoost>But then if you do it wrong, then you could produce an invalid block.

00:40:59.100 --> 00:41:04.840
<v Aaron van Wirdum>So usually, you just mentioned, usually when you're constructing a block, you're

00:41:04.840 --> 00:41:09.860
<v Aaron van Wirdum>just filling the block as full as possible with as many fees as possible.

00:41:10.080 --> 00:41:13.820
<v Sjors Provoost>Yeah, and that itself is also a non-trivial problem, but at least it's like a one

00:41:13.820 --> 00:41:18.820
<v Sjors Provoost>variable. But keep in mind that you can have transactions that are groups, like

00:41:18.820 --> 00:41:23.220
<v Sjors Provoost>clusters of transactions. And so you can't arbitrarily remove things from a group

00:41:23.220 --> 00:41:27.810
<v Sjors Provoost>because there has to be a chain. It has to be complete. The actual puzzle of

00:41:27.810 --> 00:41:30.890
<v Sjors Provoost>finding the most economically efficient block is non-trivial.

00:41:31.050 --> 00:41:31.510
<v Aaron van Wirdum>Yes.

00:41:31.670 --> 00:41:34.690
<v Sjors Provoost>But it's made very, very non-trivial because of the sigops limit.

00:41:34.950 --> 00:41:39.010
<v Aaron van Wirdum>Yeah, this sounds like there needs to be another limit being weighed in when

00:41:39.010 --> 00:41:44.830
<v Aaron van Wirdum>calculating fees. So you might need... So while inscriptions actually

00:41:44.830 --> 00:41:50.430
<v Aaron van Wirdum>gives you a discount, Stamps might, if miners are configured correctly, be more

00:41:50.430 --> 00:41:52.050
<v Aaron van Wirdum>expensive than usual.

00:41:52.640 --> 00:41:57.680
<v Sjors Provoost>Exactly. If you can choose between two transactions with the exact same size and

00:41:57.680 --> 00:42:01.500
<v Sjors Provoost>the exact same fee rate, you'd want to pick the one that does not have bare

00:42:01.500 --> 00:42:02.260
<v Sjors Provoost>multisig in it.

00:42:02.500 --> 00:42:02.680
<v Aaron van Wirdum>Right.

00:42:02.880 --> 00:42:05.760
<v Sjors Provoost>But the question is, can you just translate that to say, well, it's the

00:42:05.760 --> 00:42:10.100
<v Sjors Provoost>equivalent of so many sats per byte extra premium? I don't think it's that

00:42:10.100 --> 00:42:15.760
<v Sjors Provoost>simple. My guess is Bitcoin Core internally uses some heuristic to make it

00:42:15.760 --> 00:42:19.970
<v Sjors Provoost>expensive enough so it never goes over the limit. But that heuristic might not be

00:42:19.970 --> 00:42:23.530
<v Sjors Provoost>the most economically efficient one. It might just be the safest one because

00:42:23.530 --> 00:42:28.050
<v Sjors Provoost>nobody's using that feature. So it doesn't have to be efficient. Well, until now.

00:42:29.050 --> 00:42:32.130
<v Sjors Provoost>So somebody might have thought, hey, I'm not getting the maximum revenue because

00:42:32.130 --> 00:42:36.230
<v Sjors Provoost>of this Bitcoin Core thing is not giving me the perfect block. I'll just try it

00:42:36.230 --> 00:42:39.930
<v Sjors Provoost>myself. And then they might have done that. You know, they might have started

00:42:39.930 --> 00:42:45.890
<v Sjors Provoost>doing that just after the first hype around Counterparty died out. So they didn't

00:42:45.890 --> 00:42:50.810
<v Sjors Provoost>really take that into account, and then it went perfectly fine for four years,

00:42:50.950 --> 00:42:52.490
<v Sjors Provoost>and then boom, it blew up.

00:42:53.810 --> 00:42:59.790
<v Aaron van Wirdum>Right. Yeah, what you're saying is this block was not mined with any sort of

00:42:59.790 --> 00:43:02.570
<v Aaron van Wirdum>Bitcoin Core software. No, it must have been…

00:43:02.730 --> 00:43:03.990
<v Sjors Provoost>And another reason we know that…

00:43:03.990 --> 00:43:04.710
<v Aaron van Wirdum>To some extent, right?

00:43:06.310 --> 00:43:09.990
<v Sjors Provoost>I don't know how miners produce their blocks, but the one observation that you

00:43:09.990 --> 00:43:14.570
<v Sjors Provoost>can do is you can look at mempool.space and another website called

00:43:14.570 --> 00:43:19.150
<v Sjors Provoost>miningpool.observer. Now, it turns out if you go to miningpool.observer, which is

00:43:19.150 --> 00:43:23.130
<v Sjors Provoost>one site, what that site does is it actually uses Bitcoin Core to produce a

00:43:23.130 --> 00:43:26.910
<v Sjors Provoost>template of a block. So it says, hey, Bitcoin Core, if there was a block right

00:43:26.910 --> 00:43:31.490
<v Sjors Provoost>now, what would be in there? And it does that every 10 seconds. And so then it

00:43:31.490 --> 00:43:34.810
<v Sjors Provoost>looks at the real block. But unfortunately, it didn't look at the invalid block.

00:43:34.890 --> 00:43:39.910
<v Sjors Provoost>It looked at the valid block. And then you can see that the valid block looks

00:43:39.910 --> 00:43:42.030
<v Sjors Provoost>almost identical to what was in Bitcoin Core.

00:43:43.370 --> 00:43:47.770
<v Sjors Provoost>And so that suggests that the miner that produced the valid block was probably

00:43:47.770 --> 00:43:51.730
<v Sjors Provoost>using Bitcoin Core because it came to almost the same result. And the difference

00:43:51.730 --> 00:43:55.310
<v Sjors Provoost>was three transactions, and that could just be because they didn't see those

00:43:55.310 --> 00:43:58.450
<v Sjors Provoost>three. And those were not Counterparty transactions. Those were very small,

00:43:58.470 --> 00:44:04.370
<v Sjors Provoost>normal transactions. Now, on the other hand, we have mempool.space, which

00:44:04.370 --> 00:44:08.880
<v Sjors Provoost>has its own way of calculating what would be ideal for a block. And it does not

00:44:08.880 --> 00:44:14.380
<v Sjors Provoost>use Bitcoin Core's method of doing it. And it also compares every 10 seconds or

00:44:14.380 --> 00:44:16.820
<v Sjors Provoost>whatever what it expects in a block. And it shows you a really nice graphic

00:44:16.820 --> 00:44:21.060
<v Sjors Provoost>nowadays with pink being the color of blocks of transactions that are not

00:44:21.060 --> 00:44:25.800
<v Sjors Provoost>included. And then you see lots of big transactions that were not included. And

00:44:25.800 --> 00:44:29.730
<v Sjors Provoost>many of these were these Counterparty transactions. So what that means is that

00:44:29.860 --> 00:44:34.800
<v Sjors Provoost>whatever heuristic mempool.space is using would include these transactions

00:44:34.800 --> 00:44:39.240
<v Sjors Provoost>because they are probably paying a very good fee rate. And then it would say,

00:44:39.300 --> 00:44:42.940
<v Sjors Provoost>hey, why is the miner not including them? Well, it doesn't know, but of course

00:44:42.940 --> 00:44:44.100
<v Sjors Provoost>it's because of the sigops limit.

00:44:44.300 --> 00:44:44.680
<v Aaron van Wirdum>Right.

00:44:45.160 --> 00:44:50.880
<v Sjors Provoost>And so probably the miner would have been using an algorithm that's closer to

00:44:50.880 --> 00:44:54.780
<v Sjors Provoost>what mempool.space is doing. Not the same code necessarily, but something similar

00:44:54.780 --> 00:44:57.340
<v Sjors Provoost>because it makes sense from an economic point of view, but you're ignoring this

00:44:57.340 --> 00:45:02.740
<v Sjors Provoost>limit. But ideally you'd want to have a way to compare the invalid block to what

00:45:02.740 --> 00:45:07.100
<v Sjors Provoost>these tools are doing to see what the miner is doing. So in that sense... This

00:45:07.100 --> 00:45:10.280
<v Sjors Provoost>new protocol has given us interesting information. It's shown us that some miners

00:45:10.280 --> 00:45:12.100
<v Sjors Provoost>use different ways to compose their blocks.

00:45:12.660 --> 00:45:14.460
<v Aaron van Wirdum>Right. Moral of the story.

00:45:14.660 --> 00:45:16.380
<v Sjors Provoost>And they have not commented yet on it.

00:45:17.100 --> 00:45:23.060
<v Aaron van Wirdum>If you're mining blocks, use the sigops limit because retards are uploading

00:45:23.060 --> 00:45:26.240
<v Aaron van Wirdum>dumb images in very efficient ways on the blockchain.

00:45:26.800 --> 00:45:30.060
<v Sjors Provoost>Yeah, and I guess either you want to use the Bitcoin Core way of doing it. But

00:45:30.060 --> 00:45:33.900
<v Sjors Provoost>like I said, it may not be the most economically efficient algorithm. I haven't

00:45:33.900 --> 00:45:39.000
<v Sjors Provoost>studied it in enough detail. Or if you do roll your own, maybe just don't include

00:45:39.000 --> 00:45:44.180
<v Sjors Provoost>bare multisig at all. Just, you know, don't—it's not enough—it's not worth for

00:45:44.180 --> 00:45:50.120
<v Sjors Provoost>those few extra satoshis to risk making an invalid block. Or if you do

00:45:50.120 --> 00:45:52.500
<v Sjors Provoost>include them, make absolutely sure you don't go over the limit.

00:45:52.740 --> 00:45:56.860
<v Aaron van Wirdum>I mean, that's maybe what Bitcoin Knots does, right? I think they don't include

00:45:56.860 --> 00:45:57.820
<v Aaron van Wirdum>bare multisig at all.

00:45:59.260 --> 00:46:03.960
<v Sjors Provoost>Yeah, you can always, if you're a miner and you have a mempool, presumably, you

00:46:03.960 --> 00:46:09.490
<v Sjors Provoost>can configure that mempool to reject whatever you don't like. But there are

00:46:09.490 --> 00:46:14.950
<v Sjors Provoost>downsides to doing that. For example, if you rely on compact blocks yourself as a

00:46:14.950 --> 00:46:18.990
<v Sjors Provoost>miner, that's going to slow down if your mempool is incomplete. Because compact

00:46:18.990 --> 00:46:24.110
<v Sjors Provoost>blocks, which we talked about earlier, you're basically sending a header over to

00:46:24.110 --> 00:46:27.370
<v Sjors Provoost>the next peer, or you're sending a hash over to the next peer, and a list of

00:46:27.370 --> 00:46:31.890
<v Sjors Provoost>transactions that are included in it. And so, and then you look at that list of

00:46:31.890 --> 00:46:36.310
<v Sjors Provoost>transactions, which is like a summary and any transactions you don't have, you're

00:46:36.310 --> 00:46:41.200
<v Sjors Provoost>going to ask from your peer. So that means if, if, if this, if the last block did

00:46:41.200 --> 00:46:46.220
<v Sjors Provoost>include something you don't like, well, then you won't have those transactions

00:46:46.220 --> 00:46:50.340
<v Sjors Provoost>and you then have to call your peers to get those transactions. All the while

00:46:50.340 --> 00:46:54.100
<v Sjors Provoost>you're missing, you know, seconds of revenue perhaps, because it might,

00:46:54.240 --> 00:46:56.520
<v Sjors Provoost>especially these big ones could take you a few seconds to download.

00:46:57.850 --> 00:46:58.250
<v Aaron van Wirdum>Yep.

00:46:59.490 --> 00:46:59.890
<v Aaron van Wirdum>Okay.

00:47:00.310 --> 00:47:03.950
<v Sjors Provoost>So it's a very non-trivial thing. Like if you don't want to mine these things,

00:47:04.150 --> 00:47:07.950
<v Sjors Provoost>there's a cost to that too. But if you do mine them, there's a cost as well if

00:47:07.950 --> 00:47:08.630
<v Sjors Provoost>you make a mistake.

00:47:10.270 --> 00:47:11.130
<v Aaron van Wirdum>Yeah, makes sense.

00:47:11.430 --> 00:47:12.950
<v Sjors Provoost>Taproot gets rid of the sigops limit.

00:47:13.090 --> 00:47:14.890
<v Aaron van Wirdum>Taproot gets rid of the sigops?

00:47:15.030 --> 00:47:15.370
<v Sjors Provoost>Yeah, so Taproot.

00:47:15.370 --> 00:47:16.230
<v Aaron van Wirdum>But we have Taproot.

00:47:16.430 --> 00:47:18.770
<v Sjors Provoost>Yeah, so Taproot transactions do not count towards this limit.

00:47:19.720 --> 00:47:20.400
<v Aaron van Wirdum>Ah, I see.

00:47:20.440 --> 00:47:24.460
<v Sjors Provoost>Which means if blocks were only Taproot, this whole problem wouldn't exist.

00:47:24.960 --> 00:47:29.780
<v Aaron van Wirdum>I see. But yeah, you can't make bare multisig Taproot transactions, Sjors?

00:47:30.220 --> 00:47:30.740
<v Sjors Provoost>Correct.

00:47:31.800 --> 00:47:37.460
<v Aaron van Wirdum>Okay, I think that covered it all. We sort of explained what Stamps are and how

00:47:37.460 --> 00:47:43.030
<v Aaron van Wirdum>they compare to inscriptions and why they're much dumber and why the block was invalid.

00:47:44.570 --> 00:47:48.210
<v Sjors Provoost>And why it's very hard to count sigops. Well, we didn't say why, but I can tell

00:47:48.210 --> 00:47:49.650
<v Sjors Provoost>you it's hard to count sigops.

00:47:50.830 --> 00:47:52.550
<v Aaron van Wirdum>I think it's time to close this off.

00:47:52.670 --> 00:47:54.990
<v Sjors Provoost>I think so too. So thank you for listening to Bitcoin.

00:47:55.470 --> 00:47:55.910
<v Aaron van Wirdum>Explained.

