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

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

00:00:24.400 --> 00:00:24.880
<v Sjors Provoost>Explained.

00:00:25.140 --> 00:00:25.460
<v Aaron van Wirdum>Hey, Sjors.

00:00:25.880 --> 00:00:26.140
<v Sjors Provoost>Hello.

00:00:26.540 --> 00:00:27.580
<v Aaron van Wirdum>Sjors, we have a sponsor.

00:00:28.020 --> 00:00:30.020
<v Sjors Provoost>That is correct. We have a new sponsor.

00:00:30.120 --> 00:00:30.780
<v Aaron van Wirdum>Isn't that great?

00:00:31.320 --> 00:00:37.080
<v Sjors Provoost>That's right. Our new sponsor is Coinkite, the company behind the COLDCARD.

00:00:37.720 --> 00:00:42.360
<v Sjors Provoost>And dear listener, if you have no idea what a COLDCARD is, please let us know

00:00:42.360 --> 00:00:45.240
<v Sjors Provoost>because then we'll explain it because otherwise it's a bit ridiculous if we

00:00:45.240 --> 00:00:48.340
<v Sjors Provoost>explain it because we, I think we, we think you all know.

00:00:48.750 --> 00:00:51.930
<v Aaron van Wirdum>Oh my God, this is the worst ad read in history, Sjors.

00:00:52.410 --> 00:00:52.890
<v Sjors Provoost>Excellent.

00:00:53.550 --> 00:00:55.550
<v Aaron van Wirdum>Can we at least mention it's a hardware wallet?

00:00:55.910 --> 00:00:57.250
<v Sjors Provoost>Yes, it's a hardware wallet.

00:00:57.470 --> 00:01:02.420
<v Aaron van Wirdum>It's a hardware wallet you can use to store Bitcoin. All right, Sjors, today

00:01:02.420 --> 00:01:08.250
<v Aaron van Wirdum>we're going to discuss a new mining pool launched. Well, kind of.

00:01:08.530 --> 00:01:14.110
<v Aaron van Wirdum>Ocean pool. I was invited to the launch event. It was sort of a mini conference.

00:01:15.280 --> 00:01:20.240
<v Sjors Provoost>I felt a very strong FOMO for that one. I saw the the video uh you guys were in

00:01:20.240 --> 00:01:24.560
<v Sjors Provoost>the middle of nowhere and some like like video like some horror movie video shoot

00:01:24.560 --> 00:01:26.500
<v Sjors Provoost>game basically scene right?

00:01:26.500 --> 00:01:31.080
<v Aaron van Wirdum>Yeah well it was quite nice actually. There was like this hydro plant uh very

00:01:31.080 --> 00:01:35.340
<v Aaron van Wirdum>what's a good english word for this? Rustic I don't know if that's the right word

00:01:35.340 --> 00:01:40.410
<v Aaron van Wirdum>maybe but it was nice let's just say it was nice nice environment, And yeah they

00:01:40.410 --> 00:01:46.030
<v Aaron van Wirdum>launched this pool so it's really the relaunch or re-brand or

00:01:46.030 --> 00:01:51.530
<v Aaron van Wirdum>re-something of Eligius, if that's how I pronounce that pool, the Luke Dashjr

00:01:51.530 --> 00:01:56.830
<v Aaron van Wirdum>pool. This time it's backed by Jack Dorsey, among other investors.

00:01:57.810 --> 00:02:03.770
<v Aaron van Wirdum>And their goal, their intention is to re-decentralize mining, essentially, or

00:02:03.770 --> 00:02:04.710
<v Aaron van Wirdum>decentralize mining.

00:02:04.870 --> 00:02:06.190
<v Sjors Provoost>Right, and they're calling it Ocean.

00:02:07.090 --> 00:02:08.510
<v Aaron van Wirdum>Yeah, didn't I mention that?

00:02:08.750 --> 00:02:08.970
<v Sjors Provoost>No.

00:02:09.330 --> 00:02:15.290
<v Aaron van Wirdum>Okay, yes, Ocean, Ocean pool. Um, yeah so decentralizing mining pools or at

00:02:15.290 --> 00:02:21.190
<v Aaron van Wirdum>least this one or mining in general ultimately is the goal. The sort of

00:02:21.190 --> 00:02:26.970
<v Aaron van Wirdum>most notable innovation that they started with that they launched with is

00:02:26.970 --> 00:02:32.860
<v Aaron van Wirdum>they have this non-custodial setup kind of or I mean that's that's the goal

00:02:32.860 --> 00:02:34.140
<v Aaron van Wirdum>that's the intention that's the…

00:02:34.140 --> 00:02:38.360
<v Sjors Provoost>Yeah, I guess uh one diplomatic way to call it would be custody minimized

00:02:39.580 --> 00:02:44.080
<v Sjors Provoost>I mean, you can have long legal discussion about what custody means, but I think

00:02:44.080 --> 00:02:46.420
<v Sjors Provoost>we care most about the technical sides of it.

00:02:46.940 --> 00:02:47.380
<v Aaron van Wirdum>Right.

00:02:47.600 --> 00:02:50.840
<v Sjors Provoost>And then you can ask practical questions like, could the mining pool steal your

00:02:50.840 --> 00:02:54.740
<v Sjors Provoost>money? Could they be forced to steal your money? Et cetera, et cetera. And we can

00:02:54.740 --> 00:02:57.580
<v Sjors Provoost>try to get into some of the nuance there of what they're actually doing.

00:02:57.820 --> 00:03:03.590
<v Aaron van Wirdum>So to clarify this, what mining pools usually do is... well

00:03:03.590 --> 00:03:08.690
<v Aaron van Wirdum>I don't want to get into the whole thing but basically when a mining pool finds

00:03:08.690 --> 00:03:14.160
<v Aaron van Wirdum>new coins the mining pool gets these coins. And in fact these coins can't be

00:03:14.160 --> 00:03:18.480
<v Aaron van Wirdum>spent for 100 blocks right? Yeah and then after these 100 blocks well that's

00:03:18.480 --> 00:03:23.810
<v Aaron van Wirdum>actually not what happens with most pools um I was I was going to say after 100

00:03:23.810 --> 00:03:28.390
<v Aaron van Wirdum>blocks these coins are distributed to the miners, but that's not actually how

00:03:28.390 --> 00:03:29.090
<v Aaron van Wirdum>mining pools work.

00:03:29.150 --> 00:03:32.450
<v Sjors Provoost>I would say there's a bigger separation there, right? The mining pool as a whole

00:03:32.450 --> 00:03:37.270
<v Sjors Provoost>has a wallet and the coins they earn go into that wallet and the miners are paid

00:03:37.270 --> 00:03:41.550
<v Sjors Provoost>from that wallet. But it is a bit of an omnibus and not necessarily trivial to

00:03:41.550 --> 00:03:45.970
<v Sjors Provoost>understand which [unclear] belongs to which specific individual miner.

00:03:46.730 --> 00:03:50.810
<v Aaron van Wirdum>Yeah, a way that they will explain it or Bitcoin Mechanic, for example, is

00:03:50.810 --> 00:03:56.420
<v Aaron van Wirdum>essentially... Most Bitcoin miners or hashers, as we've also called it,

00:03:56.880 --> 00:03:59.880
<v Aaron van Wirdum>aren't actually mining Bitcoin. They're just selling their hash power to a mining

00:03:59.880 --> 00:04:03.580
<v Aaron van Wirdum>pool, basically. And the pool operator is the one that's actually...

00:04:03.580 --> 00:04:08.180
<v Sjors Provoost>Well, that sounds a little bit like a separate issue, though it's a bit related

00:04:08.180 --> 00:04:12.420
<v Sjors Provoost>to whether you're really... What it is that you're doing as a miner, are you

00:04:12.420 --> 00:04:16.100
<v Sjors Provoost>producing blocks or are you just delivering hash rate to a buyer? And that

00:04:16.100 --> 00:04:20.590
<v Sjors Provoost>depends on the... uh the incentive model the the exact business model. I think

00:04:20.590 --> 00:04:25.470
<v Sjors Provoost>we'll get into that a bit later. But the idea of holding coins custody you know

00:04:25.470 --> 00:04:29.770
<v Sjors Provoost>you could you could do that with this model too I think you just don't have to.

00:04:29.810 --> 00:04:34.530
<v Aaron van Wirdum>Right. Yeah, it is a slightly separate issue. I just wanted to point it out real

00:04:34.530 --> 00:04:40.530
<v Aaron van Wirdum>quick but yes. Uh yeah so the main innovation here is essentially that hashers

00:04:40.530 --> 00:04:45.270
<v Aaron van Wirdum>as well they'll call them, So to clarify that there's the mining pool or the

00:04:45.270 --> 00:04:49.640
<v Aaron van Wirdum>mining pool operator that's you know doing most of the Bitcoin stuff you know

00:04:49.640 --> 00:04:54.020
<v Aaron van Wirdum>downloading blockchain and constructing the blockchain template which is a big

00:04:54.020 --> 00:04:57.820
<v Aaron van Wirdum>part of it which might not happen in the future with Stratum V2 but we've made

00:04:57.820 --> 00:05:01.800
<v Aaron van Wirdum>another episode about that at least right now most mining pools still create

00:05:01.800 --> 00:05:07.440
<v Aaron van Wirdum>block templates or which transactions go into a block and I

00:05:08.120 --> 00:05:13.210
<v Aaron van Wirdum>lost my train of thought but I think I was going to say with Ocean uh The new

00:05:13.210 --> 00:05:16.590
<v Aaron van Wirdum>coins are directly paid to the hashers. Oh, I was still explaining that.

00:05:16.710 --> 00:05:20.650
<v Sjors Provoost>The coinbase transaction, which is what every new block contains, has a number of

00:05:20.650 --> 00:05:26.130
<v Sjors Provoost>outputs. And typically these just go to the general wallet of the pool. But with

00:05:26.130 --> 00:05:31.290
<v Sjors Provoost>this new Ocean pool, as much as possible, the coinbase transactions go directly

00:05:31.290 --> 00:05:32.430
<v Sjors Provoost>to the miners.

00:05:33.060 --> 00:05:33.580
<v Aaron van Wirdum>Right.

00:05:33.880 --> 00:05:37.780
<v Sjors Provoost>With the caveat that you cannot do that for all mine transactions.

00:05:39.050 --> 00:05:41.350
<v Sjors Provoost>Not for all miners, And the two reasons…

00:05:41.350 --> 00:05:45.530
<v Aaron van Wirdum>Let's get into that. First let's point out some advantages of this and the

00:05:45.530 --> 00:05:49.970
<v Aaron van Wirdum>biggest one is probably… So right now if you're a hasher and you want to join a

00:05:49.970 --> 00:05:55.810
<v Aaron van Wirdum>pool most pools have sort of KYC stuff going on like you need to actually tell

00:05:55.810 --> 00:05:59.430
<v Aaron van Wirdum>the pool who you are at least some of the big ones have this and Ocean does not

00:05:59.430 --> 00:05:59.890
<v Aaron van Wirdum>have this.

00:05:59.890 --> 00:06:04.030
<v Sjors Provoost>Yeah, but I don't think that's inherent to this model at all like you could still

00:06:04.030 --> 00:06:05.670
<v Sjors Provoost>have KYC in this model or not

00:06:07.540 --> 00:06:12.280
<v Aaron van Wirdum>Yeah. So, well, I mean, I guess in their view or what they will argue or what

00:06:12.280 --> 00:06:16.740
<v Aaron van Wirdum>they think or what they believe is that it's sort of this way it's legally

00:06:16.740 --> 00:06:18.460
<v Aaron van Wirdum>possible to not do KYC.

00:06:18.620 --> 00:06:21.480
<v Sjors Provoost>Well, we're not lawyers. I'm a developer. You're a journalist.

00:06:21.640 --> 00:06:21.820
<v Aaron van Wirdum>Right.

00:06:21.980 --> 00:06:23.080
<v Sjors Provoost>But let's...

00:06:23.080 --> 00:06:27.440
<v Aaron van Wirdum>But in any case, they aren't doing KYC stuff. That's for sure. Right now you can

00:06:27.440 --> 00:06:28.620
<v Aaron van Wirdum>just plug in and start mining.

00:06:28.820 --> 00:06:32.280
<v Sjors Provoost>One thing that they're doing very practically is that you as a miner don't create

00:06:32.280 --> 00:06:37.120
<v Sjors Provoost>an account or you don't have to. You just provide an... um but a Bitcoin address

00:06:37.120 --> 00:06:40.020
<v Sjors Provoost>straight as you're directly from the miner.

00:06:40.020 --> 00:06:45.930
<v Aaron van Wirdum>Right. Okay, so you mentioned so you so you get

00:06:45.930 --> 00:06:51.910
<v Aaron van Wirdum>paid directly from the coinbase as a hasher to the extent that it is possible

00:06:51.910 --> 00:06:56.390
<v Sjors Provoost>Yeah, and that extent is quite limited because of two reasons. One is a coinbase

00:06:56.390 --> 00:07:00.970
<v Sjors Provoost>transaction can only have this many outputs. Or even if you could have as many as

00:07:00.970 --> 00:07:06.010
<v Sjors Provoost>you want, at some point it's just not worth paying the fees. Or not so much

00:07:06.010 --> 00:07:09.210
<v Sjors Provoost>paying the fees because the coinbase transaction doesn't pay fees, but you are

00:07:09.210 --> 00:07:15.190
<v Sjors Provoost>foregoing, you know, you're using up space that others could pay, you know, that

00:07:15.190 --> 00:07:18.790
<v Sjors Provoost>other people are paying you fees as a pool. So if you make a one megabyte

00:07:18.790 --> 00:07:22.270
<v Sjors Provoost>coinbase transaction, then you can do that and you pay zero fees for it, but you

00:07:22.270 --> 00:07:24.670
<v Sjors Provoost>are now no longer mining anything.

00:07:25.550 --> 00:07:28.550
<v Aaron van Wirdum>Right, well, you could create a four megabyte coinbase transaction.

00:07:28.970 --> 00:07:30.010
<v Sjors Provoost>I don't think so, because there's no witness.

00:07:30.270 --> 00:07:31.870
<v Aaron van Wirdum>Maybe two? Oh, right.

00:07:33.390 --> 00:07:37.170
<v Aaron van Wirdum>Okay, let's separate these issues. So first of all, you said you can't

00:07:37.170 --> 00:07:41.450
<v Aaron van Wirdum>necessarily pay every hasher because the number of outputs in the coinbase

00:07:41.450 --> 00:07:42.390
<v Aaron van Wirdum>transaction is limited?

00:07:42.730 --> 00:07:46.090
<v Sjors Provoost>Or at least, I don't know if there's an actual limit there that matters, but

00:07:46.090 --> 00:07:50.350
<v Sjors Provoost>basically it's just not worth the opportunity cost of making very small payments

00:07:50.350 --> 00:07:51.010
<v Sjors Provoost>in the coinbase.

00:07:51.810 --> 00:07:56.650
<v Aaron van Wirdum>Oh, so it's the same issue. There is no actual limit to the number of outputs in

00:07:56.650 --> 00:07:57.170
<v Aaron van Wirdum>the coinbase transaction.

00:07:57.170 --> 00:08:00.590
<v Sjors Provoost>I think it's just the regular transaction, whatever that limit is. It might not

00:08:00.590 --> 00:08:02.490
<v Sjors Provoost>be one. I should know that, I guess.

00:08:04.010 --> 00:08:09.970
<v Sjors Provoost>So the second limit is a little bit more mundane. Apparently some

00:08:09.970 --> 00:08:15.330
<v Sjors Provoost>of the mining hardware out there starts to panic if you put more than 20

00:08:15.330 --> 00:08:18.750
<v Sjors Provoost>outputs in a coinbase transaction. So that has nothing to do with the Bitcoin

00:08:18.750 --> 00:08:20.790
<v Sjors Provoost>limits. It's just that some mining equipment...

00:08:22.230 --> 00:08:26.330
<v Sjors Provoost>just panics when there's too many outputs. So in practice, the limit is about 20.

00:08:26.870 --> 00:08:31.730
<v Sjors Provoost>So the 20, and in this case, the top 20 miners get paid directly from the

00:08:31.730 --> 00:08:32.170
<v Sjors Provoost>coinbase.

00:08:33.490 --> 00:08:37.830
<v Sjors Provoost>Then there's some amount left, and that essentially goes to a wallet, you could

00:08:37.830 --> 00:08:43.660
<v Sjors Provoost>say. But they make sure that... from that wallet after 100 blocks because then

00:08:43.660 --> 00:08:47.460
<v Sjors Provoost>you can spend it it immediately goes to the correct miners as if they were part

00:08:47.460 --> 00:08:48.460
<v Sjors Provoost>of the coinbase essentially.

00:08:48.460 --> 00:08:54.020
<v Aaron van Wirdum>Right. Okay, so we just so I thought wrongly

00:08:54.020 --> 00:08:58.580
<v Aaron van Wirdum>probably that there was a limit on the number of transactions on the coinbase

00:08:58.580 --> 00:09:02.780
<v Aaron van Wirdum>output and you just said that's probably not the case but there some hardware has

00:09:02.780 --> 00:09:06.140
<v Aaron van Wirdum>this issue that's that's where the limit comes from yeah okay and you say that

00:09:06.140 --> 00:09:06.960
<v Aaron van Wirdum>limit is 20.

00:09:07.920 --> 00:09:09.100
<v Sjors Provoost>Apparently roughly 20.

00:09:09.200 --> 00:09:13.280
<v Aaron van Wirdum>20-ish. Okay, there can only be 20 transaction outputs from a coinbase

00:09:13.280 --> 00:09:14.080
<v Aaron van Wirdum>transaction.

00:09:16.710 --> 00:09:21.270
<v Sjors Provoost>So that secondary transaction, which can only happen after 100 blocks because of

00:09:21.270 --> 00:09:26.440
<v Sjors Provoost>the coinbase maturity rule, that's a consensus rule, that transaction is kind of

00:09:26.440 --> 00:09:30.000
<v Sjors Provoost>just like it was part of the coinbase itself, right? It also has the same fee

00:09:30.000 --> 00:09:33.720
<v Sjors Provoost>trade-offs here where, yes, you can put whatever giant transaction you want in

00:09:33.720 --> 00:09:38.020
<v Sjors Provoost>there as a pool, but then you're foregoing fee revenue from other transactions.

00:09:38.690 --> 00:09:40.570
<v Sjors Provoost>This transaction just spends from the coinbase.

00:09:40.570 --> 00:09:44.970
<v Aaron van Wirdum>Okay, so if there's just if there's just too many hashers that need to be paid

00:09:44.970 --> 00:09:50.450
<v Aaron van Wirdum>from the coinbase if it's more than 20 essentially then some of them will be paid

00:09:50.450 --> 00:09:55.090
<v Aaron van Wirdum>later still as soon as possible but later and then the other thing was if you

00:09:55.090 --> 00:10:00.190
<v Aaron van Wirdum>mine if your hash if your hasher and you don't earn enough from a block then

00:10:00.190 --> 00:10:02.870
<v Aaron van Wirdum>you'll only also won't get paid immediately.

00:10:03.680 --> 00:10:09.380
<v Sjors Provoost>Right. So then the idea is to basically wait until you've accumulated

00:10:09.380 --> 00:10:14.820
<v Sjors Provoost>enough credit, as it were, and then you get paid. So there it really starts

00:10:14.820 --> 00:10:18.220
<v Sjors Provoost>looking like just a wallet that's custodial, but only for small amounts.

00:10:18.680 --> 00:10:23.820
<v Aaron van Wirdum>Right. OK, so that's how it works today. And then there are some ideas in the

00:10:23.820 --> 00:10:29.820
<v Aaron van Wirdum>future for the future to improve that a little bit more. So one

00:10:29.820 --> 00:10:31.760
<v Aaron van Wirdum>of them is using Lightning for payouts.

00:10:32.040 --> 00:10:36.140
<v Sjors Provoost>Yeah, that kind of makes intuitive sense when you have very small miners that

00:10:36.140 --> 00:10:39.560
<v Sjors Provoost>want to collect small rewards. Maybe they get like 20 satoshis every block.

00:10:40.740 --> 00:10:45.370
<v Sjors Provoost>Lightning is a way to do that. And then the question is, can you, you know, how

00:10:45.370 --> 00:10:49.510
<v Sjors Provoost>non-custodial can you make Lightning? I believe if you listen to the Stephan

00:10:49.510 --> 00:10:55.410
<v Sjors Provoost>Livera podcast, Bitcoin Mechanic explains some ideas of how to do that

00:10:55.410 --> 00:10:55.830
<v Sjors Provoost>roughly.

00:10:57.300 --> 00:11:01.580
<v Sjors Provoost>using, I believe, some sort of market where, like, if you have Lightning

00:11:01.580 --> 00:11:06.600
<v Sjors Provoost>liquidity, you essentially buy the rights to the payouts from the pool. So the

00:11:06.600 --> 00:11:10.460
<v Sjors Provoost>pool is not doing the Lightning payouts. They're just giving payouts to

00:11:10.460 --> 00:11:14.340
<v Sjors Provoost>addresses, but then somebody else does some swapping of who gets which coins.

00:11:15.280 --> 00:11:20.660
<v Aaron van Wirdum>Right. And then there's another potentially cool idea, which is not possible yet

00:11:20.660 --> 00:11:26.380
<v Aaron van Wirdum>on the Bitcoin network, but with CHECKTEMPLATEVERIFY it could actually be

00:11:26.380 --> 00:11:31.200
<v Aaron van Wirdum>implemented that if this 20 limit threshold in the coinbase is reached,

00:11:31.470 --> 00:11:37.290
<v Aaron van Wirdum>then the other hashers are still guaranteed their payment through a

00:11:37.290 --> 00:11:38.450
<v Aaron van Wirdum>CTV transaction.

00:11:39.090 --> 00:11:44.970
<v Sjors Provoost>And even better than that, regardless of this 20 limit, right now, if you're

00:11:44.970 --> 00:11:48.710
<v Sjors Provoost>putting something, you have to put the addresses in the coinbase right now. And

00:11:48.710 --> 00:11:52.710
<v Sjors Provoost>so you kind of don't want to do that when fees are really high because that's an

00:11:52.710 --> 00:11:57.400
<v Sjors Provoost>opportunity cost. But maybe you want to pay people when fees are low. So CTV is

00:11:57.400 --> 00:12:01.100
<v Sjors Provoost>quite interesting for that. We have not really discussed it in any podcast, but

00:12:01.100 --> 00:12:06.100
<v Sjors Provoost>it's basically a soft fork proposal that commits to certain transactions

00:12:06.100 --> 00:12:10.760
<v Sjors Provoost>happening in the future. And one of the intended use cases is congestion control.

00:12:10.900 --> 00:12:15.040
<v Sjors Provoost>And this would be a very nice use case for it, where the coinbase only has one

00:12:15.040 --> 00:12:20.140
<v Sjors Provoost>output or maybe a couple, which is the CTV transaction. And then all the miners

00:12:20.140 --> 00:12:24.480
<v Sjors Provoost>know for sure that they will get those coins, but they'll wait until fees are low

00:12:24.480 --> 00:12:25.980
<v Sjors Provoost>and then they'll get them.

00:12:26.690 --> 00:12:27.050
<v Aaron van Wirdum>Right.

00:12:28.390 --> 00:12:33.690
<v Aaron van Wirdum>All right. That was the non-custodial part of the pool, which is probably kind of

00:12:33.690 --> 00:12:36.230
<v Aaron van Wirdum>the main innovation, but it's not the only thing going on.

00:12:36.510 --> 00:12:38.410
<v Sjors Provoost>Yeah. Or the custody minimized part of the pool. Right.

00:12:38.510 --> 00:12:44.200
<v Aaron van Wirdum>All right. I'm sorry, Sjors. You're very right. The other thing is... um so the

00:12:44.200 --> 00:12:49.500
<v Aaron van Wirdum>the block template is transparent so usually

00:12:49.500 --> 00:12:54.120
<v Aaron van Wirdum>at most pools right now because they have this FPPS model which I briefly

00:12:54.120 --> 00:12:58.580
<v Aaron van Wirdum>mentioned earlier where hashers are basically just selling their hash power to a

00:12:58.580 --> 00:13:04.410
<v Aaron van Wirdum>mining pool and the mining pool just makes a block with it. Now on Ocean it's

00:13:04.410 --> 00:13:08.770
<v Aaron van Wirdum>completely transparent what the block will actually look like that everyone is

00:13:08.770 --> 00:13:09.450
<v Aaron van Wirdum>working on right?

00:13:09.450 --> 00:13:14.070
<v Sjors Provoost>Yeah, so I don't know how inherent this limitation is in normal pools I do know

00:13:14.070 --> 00:13:17.650
<v Sjors Provoost>that Stratum V2 doesn't have this problem in Stratum V2 you know exactly what

00:13:17.650 --> 00:13:21.750
<v Sjors Provoost>you're mining but in this case Ocean pool will show you what you're mining

00:13:21.750 --> 00:13:26.620
<v Sjors Provoost>without even using Stratum V2 and typically you don't know what you're mining you

00:13:26.620 --> 00:13:31.060
<v Sjors Provoost>just get a hash and you're grinding away on that hash um now you can go to at

00:13:31.060 --> 00:13:34.920
<v Sjors Provoost>least you can go to an API and check and this could be interesting especially for

00:13:34.920 --> 00:13:38.660
<v Sjors Provoost>bigger miners because bigger miners they're paid directly from the coinbase so

00:13:38.660 --> 00:13:43.020
<v Sjors Provoost>they can see that they're mining a block that pays them like they know for sure

00:13:43.020 --> 00:13:48.580
<v Sjors Provoost>um smaller miners again with the CTV technique they might also be able to check

00:13:48.580 --> 00:13:52.600
<v Sjors Provoost>this uh probably not in real time right because you don't want to spend 10

00:13:52.600 --> 00:13:55.900
<v Sjors Provoost>seconds calculating if you're If you're mining the correct block, you just want

00:13:55.900 --> 00:13:59.080
<v Sjors Provoost>to start mining. But you can at least, within a few seconds, see, hey, I'm being

00:13:59.080 --> 00:14:04.790
<v Sjors Provoost>scammed. I'm going to stop mining now. So that's quite nice for tiny miners that

00:14:04.790 --> 00:14:08.910
<v Sjors Provoost>have to be paid through Lightning. I don't think this offers any benefit in terms

00:14:08.910 --> 00:14:11.990
<v Sjors Provoost>of knowing that you're going to be paid. But you still know what you're mining.

00:14:11.990 --> 00:14:15.350
<v Sjors Provoost>You might realize that you're censoring certain stuff that you're not happy with,

00:14:15.770 --> 00:14:16.690
<v Sjors Provoost>etc. So that's good.

00:14:18.230 --> 00:14:22.590
<v Aaron van Wirdum>Yeah, the counter or one of the examples that Bitcoin Mechanic, for example, will

00:14:22.590 --> 00:14:23.550
<v Aaron van Wirdum>bring up is that...

00:14:24.790 --> 00:14:29.660
<v Aaron van Wirdum>There have been pools that have mined blocks that are basically one big

00:14:29.660 --> 00:14:33.300
<v Aaron van Wirdum>inscription or have big inscriptions in them, and hashers had no idea that that's

00:14:33.300 --> 00:14:36.060
<v Aaron van Wirdum>what they were doing. Now, maybe they also don't care that that's what they're

00:14:36.060 --> 00:14:40.660
<v Aaron van Wirdum>doing, but maybe they do care. In any case, with Ocean, hashers will actually

00:14:40.660 --> 00:14:41.640
<v Aaron van Wirdum>know what they're doing.

00:14:41.920 --> 00:14:44.760
<v Sjors Provoost>Yeah, but also with Stratum V2, I believe, they'll know.

00:14:45.180 --> 00:14:50.300
<v Aaron van Wirdum>So, yeah about Stratum V2 uh we already made an episode about that and I was also

00:14:50.300 --> 00:14:55.420
<v Aaron van Wirdum>already mentioned that but um it does seem like that sort of on the roadmap for

00:14:55.420 --> 00:14:56.380
<v Aaron van Wirdum>Ocean but they don't

00:14:56.380 --> 00:14:59.820
<v Sjors Provoost>I'm sure it is but I'm always skeptical of roadmaps. Right right show it to me.

00:14:59.820 --> 00:15:02.520
<v Aaron van Wirdum>Yeah, they don't have it now yet in any case

00:15:03.220 --> 00:15:06.200
<v Sjors Provoost>I'm sure they will but they don't have it yet.

00:15:06.840 --> 00:15:12.560
<v Aaron van Wirdum>All right and then we get to possibly the most

00:15:12.560 --> 00:15:16.850
<v Aaron van Wirdum>complex topic of all of them.

00:15:18.090 --> 00:15:22.870
<v Aaron van Wirdum>Yesterday, we had a sort of preparation call with, also with Bitcoin Mechanic and

00:15:22.870 --> 00:15:27.290
<v Aaron van Wirdum>with the CTO of the pool, Jason Hughes, and it was one of these calls where I was

00:15:27.290 --> 00:15:33.080
<v Aaron van Wirdum>on it and Sjors was just sort of going on adventure with the CTO and I

00:15:33.080 --> 00:15:36.980
<v Aaron van Wirdum>couldn't really keep up with everything you were discussing. So let's see what

00:15:36.980 --> 00:15:37.740
<v Aaron van Wirdum>you've figured out.

00:15:38.100 --> 00:15:41.540
<v Sjors Provoost>Yeah, so in case people think that I confidently understand stuff spontaneously,

00:15:41.900 --> 00:15:43.540
<v Sjors Provoost>no, that takes a lot of effort.

00:15:44.030 --> 00:15:46.930
<v Aaron van Wirdum>Right. Okay, so...

00:15:48.670 --> 00:15:50.690
<v Aaron van Wirdum>I'm barely even sure how to introduce this.

00:15:50.850 --> 00:15:56.330
<v Sjors Provoost>Well, I think we should generally talk about shares a little bit without any of

00:15:56.330 --> 00:15:59.810
<v Sjors Provoost>the crazy mechanics that are being used generally. But the idea is if you are

00:15:59.810 --> 00:16:03.010
<v Sjors Provoost>mining, you need to prove to the pool that you are actually doing some work.

00:16:03.270 --> 00:16:07.070
<v Aaron van Wirdum>Yeah, how does the pool decide which hashers get how much Bitcoin?

00:16:07.150 --> 00:16:10.910
<v Sjors Provoost>And I think we discussed this also in the Stratum V2 episode, by the way, so you

00:16:10.910 --> 00:16:14.410
<v Sjors Provoost>could re-listen to that. But the general idea is that you will mine a block with

00:16:14.410 --> 00:16:19.060
<v Sjors Provoost>a much, much, much lower difficulty. And for example, the block that you're

00:16:19.060 --> 00:16:23.600
<v Sjors Provoost>trying to mine, the pool wants to see it if it is like a thousand times easier

00:16:23.600 --> 00:16:24.980
<v Sjors Provoost>than the real block.

00:16:25.140 --> 00:16:27.640
<v Aaron van Wirdum>Yeah, you're basically mining invalid blocks.

00:16:28.140 --> 00:16:32.460
<v Sjors Provoost>Yeah, but they're not randomly invalid. They are like as if the proof of work

00:16:32.460 --> 00:16:37.480
<v Sjors Provoost>difficulty was still at the level it was when Satoshi started, basically. And the

00:16:37.480 --> 00:16:42.620
<v Sjors Provoost>nice thing is that when you do that... You cannot lie about it. You are providing

00:16:42.620 --> 00:16:45.740
<v Sjors Provoost>proof of work, just a little bit less proof of work because you're only sharing

00:16:45.740 --> 00:16:48.240
<v Sjors Provoost>it with the pool operator and not the whole internet.

00:16:48.480 --> 00:16:48.800
<v Aaron van Wirdum>Yeah.

00:16:48.900 --> 00:16:53.440
<v Sjors Provoost>So it's fine to have a little bit more spam. And generally, they'll aim to have

00:16:53.440 --> 00:16:57.780
<v Sjors Provoost>like eight blocks a second, sorry, eight blocks per minute. That's, I believe,

00:16:57.880 --> 00:16:58.560
<v Sjors Provoost>often an interval.

00:16:58.780 --> 00:17:02.420
<v Aaron van Wirdum>You're basically proving to the pool that you're at least trying to find a block.

00:17:02.820 --> 00:17:03.200
<v Sjors Provoost>Exactly.

00:17:03.500 --> 00:17:03.640
<v Aaron van Wirdum>Right.

00:17:03.880 --> 00:17:05.540
<v Sjors Provoost>And then occasionally you will find a block.

00:17:05.880 --> 00:17:11.630
<v Aaron van Wirdum>Right. Exactly. And then, yes. Okay, so Ocean has this way, it's called TIDES.

00:17:12.490 --> 00:17:15.950
<v Aaron van Wirdum>So how do you decide which hasher gets how much Bitcoin?

00:17:16.390 --> 00:17:20.870
<v Sjors Provoost>Yeah, that is the hard question. And I think we'll also get a little bit into how

00:17:20.870 --> 00:17:23.970
<v Sjors Provoost>other pools do that. But I actually don't really understand how other pools do

00:17:23.970 --> 00:17:27.730
<v Sjors Provoost>it. And I think I do understand how this pool does it. Because I think it's a

00:17:27.730 --> 00:17:29.450
<v Sjors Provoost>fairly elegant and simple system.

00:17:29.650 --> 00:17:33.550
<v Aaron van Wirdum>Well, I think how other pools do it is that's the FPPS system, right? So

00:17:33.550 --> 00:17:39.240
<v Aaron van Wirdum>basically a pool just says... we'll pay you X amount of Bitcoin for X amount of

00:17:39.240 --> 00:17:41.400
<v Aaron van Wirdum>hashes. And that's just it.

00:17:42.040 --> 00:17:44.440
<v Sjors Provoost>Yeah, but there's a little nuance of how much X is.

00:17:45.360 --> 00:17:51.130
<v Aaron van Wirdum>How X is calculated, you mean? Yeah. I've never really looked into

00:17:51.130 --> 00:17:55.170
<v Aaron van Wirdum>that, and let's skip that. That's the easiest thing to do here. And let's get

00:17:55.170 --> 00:17:56.610
<v Aaron van Wirdum>into how Ocean actually does it.

00:17:57.030 --> 00:18:02.680
<v Sjors Provoost>Right, that was sort of the idea. Okay, so basically the idea is

00:18:02.680 --> 00:18:08.480
<v Sjors Provoost>that there is a bucket, or it's not really a bucket, it's a queue, and

00:18:08.480 --> 00:18:12.760
<v Sjors Provoost>you are adding work, little loads of work, little shares of work, into a queue.

00:18:14.000 --> 00:18:18.400
<v Sjors Provoost>Let's say the two of us are mining, I've got my little vintage S9 that I've

00:18:18.400 --> 00:18:24.020
<v Sjors Provoost>clocked down to 1 terahertz, a terahash, so that it uses less power and makes

00:18:24.020 --> 00:18:28.300
<v Sjors Provoost>less noise, and it can sit here in my living room, basically, without driving me nuts.

00:18:29.940 --> 00:18:32.480
<v Sjors Provoost>And you have the same, so we're each hashing away.

00:18:32.480 --> 00:18:35.840
<v Aaron van Wirdum>It's just not clocked down and it's driving me crazy because I don't know how to do that.

00:18:36.560 --> 00:18:36.960
<v Sjors Provoost>Oh.

00:18:37.240 --> 00:18:37.720
<v Aaron van Wirdum>Go on.

00:18:38.280 --> 00:18:43.080
<v Sjors Provoost>Anyway, so both of us are mining and what we do is to the pool, we're proving

00:18:43.080 --> 00:18:46.960
<v Sjors Provoost>that we're doing this amount of work. And so the pool is keeping track of that.

00:18:47.300 --> 00:18:50.420
<v Sjors Provoost>You're submitting a share, I'm submitting a share, you're submitting a share, I'm

00:18:50.420 --> 00:18:56.370
<v Sjors Provoost>submitting a share. And over time, this builds up. And eventually a block

00:18:56.370 --> 00:19:01.710
<v Sjors Provoost>is found and then... In the simplest case, we've both submitted the same number

00:19:01.710 --> 00:19:05.950
<v Sjors Provoost>of shares. And, you know, the shares are adjusted for how strong our miners are.

00:19:06.090 --> 00:19:09.800
<v Sjors Provoost>But in this case, we assume the miners are equally strong. The block arrives,

00:19:10.020 --> 00:19:14.580
<v Sjors Provoost>then half the coinbase transaction output goes to me. Half the coinbase output

00:19:14.580 --> 00:19:16.640
<v Sjors Provoost>transaction goes to you. This is very simple.

00:19:18.240 --> 00:19:18.740
<v Sjors Provoost>Now,

00:19:19.940 --> 00:19:25.140
<v Sjors Provoost>let's... So this bucket of shares does not fill up to infinity.

00:19:25.740 --> 00:19:31.180
<v Sjors Provoost>So if we do this for a few years, then the division who gets how much does

00:19:31.180 --> 00:19:36.600
<v Sjors Provoost>not depend on the total amount of shares we submitted throughout history,

00:19:36.600 --> 00:19:41.800
<v Sjors Provoost>but it only depends on the recent past. It's kind of like a rolling window.

00:19:42.040 --> 00:19:42.700
<v Aaron van Wirdum>How recent?

00:19:43.240 --> 00:19:46.520
<v Sjors Provoost>The equivalent, so this is where it gets a little more complicated, is the

00:19:46.520 --> 00:19:52.500
<v Sjors Provoost>equivalent of eight blocks of work for the whole network. So the

00:19:52.500 --> 00:19:55.260
<v Sjors Provoost>number of hashes, or sorry, the number of shares it would take,

00:19:56.600 --> 00:19:58.500
<v Sjors Provoost>statistically, to produce eight blocks.

00:19:59.920 --> 00:20:03.120
<v Sjors Provoost>You know, with my miner, that would be, I don't know, two million years worth of

00:20:03.120 --> 00:20:07.740
<v Sjors Provoost>blocks or something. Or two million years worth of mining, let's say, and for

00:20:07.740 --> 00:20:13.420
<v Sjors Provoost>you, the same thing. But as soon as the mining pool has more shares than that, it

00:20:13.420 --> 00:20:18.360
<v Sjors Provoost>starts discarding old shares, or at least it starts ignoring them. Um, so it's,

00:20:18.480 --> 00:20:23.240
<v Sjors Provoost>and so in practice, um, let's take another example where we actually have to

00:20:23.240 --> 00:20:28.440
<v Sjors Provoost>really find a really fast miners. In fact, our miners are, uh, as fast as the

00:20:28.440 --> 00:20:29.260
<v Sjors Provoost>whole Bitcoin network.

00:20:30.750 --> 00:20:34.810
<v Sjors Provoost>Um, somehow we've turned off all the other miners in the network. And so this,

00:20:34.890 --> 00:20:39.890
<v Sjors Provoost>this Eligius pool, sorry, the Ocean pool is now the only pool and we are

00:20:39.890 --> 00:20:43.630
<v Sjors Provoost>continuing with the Bitcoin network at the same hash power. So just to keep the,

00:20:43.630 --> 00:20:45.210
<v Sjors Provoost>uh, the analogy a bit simple here.

00:20:45.430 --> 00:20:47.150
<v Aaron van Wirdum>Yes. Please.

00:20:47.510 --> 00:20:51.230
<v Sjors Provoost>Yes. Now, in this case, actually, sorry, our miners are a little bit different.

00:20:52.570 --> 00:20:57.270
<v Sjors Provoost>That is, my miner is as strong as the entire Bitcoin network is and your miner is

00:20:57.270 --> 00:21:01.650
<v Sjors Provoost>as strong as the entire Bitcoin network is. I'm going to turn it on. You're not.

00:21:01.870 --> 00:21:06.210
<v Sjors Provoost>And then at the end, you're going to turn it on and I'm going to turn it off.

00:21:06.330 --> 00:21:08.290
<v Sjors Provoost>Because then the question is, how much do we get?

00:21:08.690 --> 00:21:08.890
<v Aaron van Wirdum>Right.

00:21:09.330 --> 00:21:14.430
<v Sjors Provoost>So let's take the simplest possible example or about...

00:21:15.030 --> 00:21:20.950
<v Sjors Provoost>40 minutes, I turn it on, and then for 40 minutes, you turn it on, and by

00:21:20.950 --> 00:21:26.470
<v Sjors Provoost>just complete coincidence, blocks are found exactly every 10 minutes.

00:21:26.930 --> 00:21:28.590
<v Sjors Provoost>So then the question is, what happens?

00:21:30.120 --> 00:21:34.820
<v Sjors Provoost>Initially, I turn it on first, right? So initially, I get everything for the

00:21:34.820 --> 00:21:38.260
<v Sjors Provoost>first block, second block, third block, fourth block, because I was the only one

00:21:38.260 --> 00:21:42.640
<v Sjors Provoost>mining, and I'm the only one in the history, ignoring that there's a further

00:21:42.640 --> 00:21:47.810
<v Sjors Provoost>past. Now, you turn on your miner and I've turned off mine. So what happens in

00:21:47.810 --> 00:21:52.150
<v Sjors Provoost>the next block? Well, it's looking back at the equivalent of eight blocks, which

00:21:52.150 --> 00:21:57.450
<v Sjors Provoost>is more than so far what we've collected. And so you are going to get one-fifth

00:21:57.450 --> 00:22:00.450
<v Sjors Provoost>and I'm going to get four-fifths of the next block.

00:22:01.640 --> 00:22:03.000
<v Aaron van Wirdum>That sounds very unfair.

00:22:03.860 --> 00:22:07.720
<v Sjors Provoost>It doesn't because if we look at that history for the last eight blocks, you have

00:22:07.720 --> 00:22:10.620
<v Sjors Provoost>done one-fifth of the work and I've done four-fifths of the work.

00:22:12.440 --> 00:22:14.620
<v Aaron van Wirdum>Yes, but now I'm not getting one-fifth of the Bitcoin.

00:22:15.600 --> 00:22:16.940
<v Sjors Provoost>You are getting one-fifth of Bitcoin.

00:22:17.100 --> 00:22:19.300
<v Aaron van Wirdum>Not of all Bitcoins that have been issued so far.

00:22:19.740 --> 00:22:23.320
<v Sjors Provoost>No, you're getting one-fifth of the next block. Yeah, it's always what you get in

00:22:23.320 --> 00:22:25.900
<v Sjors Provoost>the next block. Now the block after that...

00:22:25.900 --> 00:22:27.360
<v Aaron van Wirdum>Feels like I'm being scammed here, Sjors.

00:22:27.520 --> 00:22:31.780
<v Sjors Provoost>I don't think so. I think the next block, you're getting two-sixths of it. Then

00:22:31.780 --> 00:22:35.280
<v Sjors Provoost>the next block, you're getting three-sixths of it. And then the next... Sorry,

00:22:35.440 --> 00:22:38.640
<v Sjors Provoost>three-seventh of it. And then the next block, you're getting half of it. Four out

00:22:38.640 --> 00:22:41.580
<v Sjors Provoost>of eight. Because now you have done half the work in the past eight blocks.

00:22:42.140 --> 00:22:46.740
<v Aaron van Wirdum>I'm still being scammed like you got all the bitcoins of the first four and you

00:22:46.740 --> 00:22:49.160
<v Aaron van Wirdum>still get part of the bitcoins of the last four

00:22:49.160 --> 00:22:51.160
<v Sjors Provoost>Even though it sounds pretty evil doesn't it?

00:22:51.160 --> 00:22:51.560
<v Aaron van Wirdum>Yes.

00:22:51.560 --> 00:22:57.120
<v Sjors Provoost>But now uh we continue in time and you keep hashing and I don't and it goes up

00:22:57.120 --> 00:23:01.000
<v Sjors Provoost>you get five eight six eight seven eight eight eight you get all of it

00:23:01.670 --> 00:23:06.810
<v Aaron van Wirdum>Yeah, but now I still did two thirds of the work Sjors and I didn't get two

00:23:06.810 --> 00:23:07.950
<v Aaron van Wirdum>thirds of the Bitcoin I think

00:23:09.670 --> 00:23:13.450
<v Aaron van Wirdum>Anyways, I do think probably if you keep the logic going long enough, then it

00:23:13.450 --> 00:23:16.030
<v Aaron van Wirdum>will probably work out. But so far, I'm still being scammed here.

00:23:16.210 --> 00:23:18.670
<v Sjors Provoost>I don't think you're getting scammed, but it is true that it's a bit hard to

00:23:18.670 --> 00:23:22.650
<v Sjors Provoost>reason about it because one of the problems is if you stop and there's no other

00:23:22.650 --> 00:23:27.670
<v Sjors Provoost>miner, then you get nothing, right? But if I then take over, you will continue to

00:23:27.670 --> 00:23:32.770
<v Sjors Provoost>get rewards for the next eight blocks or so. It'll decrease

00:23:32.770 --> 00:23:37.030
<v Sjors Provoost>as your work goes back into the past. So I think it works out.

00:23:39.960 --> 00:23:45.840
<v Aaron van Wirdum>Yeah, well, wasn't there a thing that with the actual first eight

00:23:45.840 --> 00:23:50.780
<v Aaron van Wirdum>blocks, so including the actual first eight blocks that I think Ocean is mining,

00:23:51.080 --> 00:23:55.080
<v Aaron van Wirdum>the logic is a bit different. So aren't you now explaining the logic that will

00:23:55.080 --> 00:23:58.440
<v Aaron van Wirdum>work fine later on, but not for the first eight?

00:24:01.110 --> 00:24:05.990
<v Sjors Provoost>No, I think it was fine for the first eight too, because we are simply splitting

00:24:05.990 --> 00:24:07.450
<v Sjors Provoost>the work between us in that case.

00:24:10.270 --> 00:24:14.010
<v Aaron van Wirdum>No, but we just established that I got scammed.

00:24:14.130 --> 00:24:18.600
<v Sjors Provoost>I don't think you got scammed. I think you're just bad at math. But I don't know

00:24:18.600 --> 00:24:19.120
<v Sjors Provoost>for sure either.

00:24:21.290 --> 00:24:25.290
<v Aaron van Wirdum>Surely I'm not bad at math. Like in your example, you mined the first four and I

00:24:25.290 --> 00:24:31.120
<v Aaron van Wirdum>mined the last eight. and we're still splitting the coins 50 the total coins 50 50

00:24:31.120 --> 00:24:35.600
<v Sjors Provoost>So, so you've mined the last eight but you still will get rewards in the future

00:24:35.600 --> 00:24:38.380
<v Sjors Provoost>right so you haven't had it yet but you will get it.

00:24:38.380 --> 00:24:39.340
<v Aaron van Wirdum>Right, right, right, right.

00:24:39.340 --> 00:24:42.420
<v Sjors Provoost>But somebody has to do the mining so the question then is, When when is that game

00:24:42.420 --> 00:24:47.370
<v Sjors Provoost>done? Well if I then take over you will get the part that you still owed.

00:24:47.610 --> 00:24:51.630
<v Aaron van Wirdum>Right, yes. Okay, now that actually makes sense. And [unclear], I am bad in math.

00:24:51.770 --> 00:24:55.590
<v Aaron van Wirdum>But in this case, I was still kind of right, I think. But yes, you're right.

00:24:55.770 --> 00:24:59.730
<v Sjors Provoost>So now let's take a slightly different experiment because in reality, blocks do

00:24:59.730 --> 00:25:04.330
<v Sjors Provoost>not arrive every 10 minutes. And so the question then is, well, what if blocks

00:25:04.330 --> 00:25:07.850
<v Sjors Provoost>arrive really quickly and then it takes a really long time? How does that

00:25:07.850 --> 00:25:12.430
<v Sjors Provoost>division work, right? It's not that the blocks, that the rewards are equally

00:25:12.430 --> 00:25:17.610
<v Sjors Provoost>divided between the actual blocks. It's based on the effort you're putting into

00:25:17.610 --> 00:25:22.370
<v Sjors Provoost>the system. So an example that I just wrote down this morning or afternoon

00:25:22.690 --> 00:25:27.250
<v Sjors Provoost>would be this. I am mining...

00:25:27.540 --> 00:25:33.240
<v Sjors Provoost>I mine seven blocks. Again, we are the entire pool. I mine seven blocks,

00:25:33.480 --> 00:25:37.770
<v Sjors Provoost>one every minute. And then I stop and you start mining.

00:25:39.630 --> 00:25:44.500
<v Sjors Provoost>And only after two hours... you find block number eight.

00:25:45.000 --> 00:25:48.780
<v Aaron van Wirdum>But that's just because of bad luck in your example, right?

00:25:48.900 --> 00:25:49.100
<v Sjors Provoost>Yes.

00:25:49.320 --> 00:25:51.660
<v Aaron van Wirdum>It's not lower hash power on my end, it's bad luck.

00:25:51.860 --> 00:25:52.500
<v Sjors Provoost>It's just bad luck.

00:25:52.560 --> 00:25:52.880
<v Aaron van Wirdum>Yeah, okay.

00:25:53.160 --> 00:25:58.000
<v Sjors Provoost>And so in this scenario, I got lucky. Well, again, this is kind of the

00:25:58.000 --> 00:26:01.700
<v Sjors Provoost>bootstrapping problem, but if we kind of ignore that, I get lucky the first seven

00:26:01.700 --> 00:26:05.820
<v Sjors Provoost>times I get 100% of the work of the coins, even though I only mine for seven

00:26:05.820 --> 00:26:07.580
<v Sjors Provoost>minutes. That's just because of the luck.

00:26:09.670 --> 00:26:14.530
<v Sjors Provoost>And then, but you have been mining now for eight hours, or sorry, two hours, or

00:26:14.530 --> 00:26:16.630
<v Sjors Provoost>one hour and 53 minutes, whatever you want to say.

00:26:18.100 --> 00:26:23.350
<v Sjors Provoost>The question then is, and you find a block, how much do you get and how much do I get?

00:26:25.750 --> 00:26:30.370
<v Aaron van Wirdum>I mean, judging by your logic so far, I'm going to be scammed somehow, so tell me.

00:26:31.070 --> 00:26:32.670
<v Sjors Provoost>No, you get 100%.

00:26:33.210 --> 00:26:34.470
<v Aaron van Wirdum>Of what?

00:26:34.730 --> 00:26:36.550
<v Sjors Provoost>Of the reward in that eighth block.

00:26:38.070 --> 00:26:42.310
<v Aaron van Wirdum>Oh, right so this is because statistically there's been eight blocks on the

00:26:42.310 --> 00:26:43.910
<v Aaron van Wirdum>network even though there haven't right

00:26:43.910 --> 00:26:47.670
<v Sjors Provoost>Yeah, or in you know the accounting system is checking how much work you

00:26:47.670 --> 00:26:51.970
<v Sjors Provoost>submitted and you have submitted more than eight blocks worth of work now because

00:26:51.970 --> 00:26:56.810
<v Sjors Provoost>it's two hours so that's about you know normally you'd expect 12 blocks in that

00:26:56.810 --> 00:27:02.190
<v Sjors Provoost>time period. So you have submitted eight blocks roughly equivalent worth of work,

00:27:02.210 --> 00:27:06.070
<v Sjors Provoost>and therefore all the old stuff that I submitted no longer counts for the

00:27:06.070 --> 00:27:10.470
<v Sjors Provoost>accounting. You get all of it. You still got unlucky, but in a way it's fair.

00:27:10.690 --> 00:27:14.710
<v Sjors Provoost>That depends on your definition of fair, but yeah. But this is to make the

00:27:14.710 --> 00:27:19.820
<v Sjors Provoost>distinction between... It's not actually eight blocks. It's not the last eight

00:27:19.820 --> 00:27:23.160
<v Sjors Provoost>blocks. It's about the equivalent amount of work that went into the pool.

00:27:23.520 --> 00:27:26.180
<v Aaron van Wirdum>Yes, and that's calculated just based on the difficulty?

00:27:27.020 --> 00:27:31.000
<v Sjors Provoost>Yes, that is exactly. That's based on the current difficulty. So it gets a bit

00:27:31.000 --> 00:27:36.120
<v Sjors Provoost>more complicated, I guess, if the difficulty goes up or down. But every two

00:27:36.120 --> 00:27:40.060
<v Sjors Provoost>weeks, you know, the difficulty is constant and then it changes once. So as long

00:27:40.060 --> 00:27:43.680
<v Sjors Provoost>as you don't go over that boundary, the math is pretty simple. But this is, I

00:27:43.680 --> 00:27:47.800
<v Sjors Provoost>believe, also one reason why old shares are not thrown away. Because you could be

00:27:47.800 --> 00:27:52.520
<v Sjors Provoost>in a situation where the difficulty goes up, and now the equivalent of eight days

00:27:52.520 --> 00:27:56.460
<v Sjors Provoost>is more than it was before, and so you need to go back in time and look into the

00:27:56.460 --> 00:27:59.660
<v Sjors Provoost>log of the people that were doing something a little bit before the window.

00:28:02.700 --> 00:28:08.480
<v Sjors Provoost>Let's say the difficulty doubles overnight. Now you're looking at the

00:28:08.480 --> 00:28:13.980
<v Sjors Provoost>equivalent of eight days, which is, in reality, would have been 16 days of

00:28:14.820 --> 00:28:20.420
<v Sjors Provoost>actual work, if you're looking at the past. So you cannot throw away the past, Or

00:28:20.420 --> 00:28:22.580
<v Sjors Provoost>at least, you know, not unreasonably.

00:28:22.920 --> 00:28:27.820
<v Aaron van Wirdum>All right. Well, I'm glad you sort of understand this part of the Ocean pool. Did

00:28:27.820 --> 00:28:30.640
<v Aaron van Wirdum>we cover this part sufficiently, you think?

00:28:30.800 --> 00:28:31.440
<v Sjors Provoost>I think so.

00:28:31.820 --> 00:28:32.480
<v Aaron van Wirdum>Okay, good.

00:28:33.530 --> 00:28:37.770
<v Sjors Provoost>Yeah, so the funny thing is we did not cover a number of topics that are quite

00:28:37.770 --> 00:28:42.870
<v Sjors Provoost>popular when talking about mining pools. We did not talk about pool hopping. We

00:28:42.870 --> 00:28:47.730
<v Sjors Provoost>did not talk about PPS and FPPS and all these different rewards.

00:28:46.480 --> 00:28:47.160
<v Aaron van Wirdum>I did.

00:28:47.600 --> 00:28:49.670
<v Sjors Provoost>[unclear]. But not in much detail.

00:28:51.010 --> 00:28:53.550
<v Sjors Provoost>Partially it's because I don't fully understand those systems.

00:28:55.330 --> 00:28:58.770
<v Sjors Provoost>But partially it's because we already explained this system and you guys are

00:28:58.770 --> 00:29:03.010
<v Sjors Provoost>getting tired and our editor is getting tired. So we might actually come back to

00:29:03.010 --> 00:29:04.030
<v Sjors Provoost>it some other time.

00:29:04.770 --> 00:29:07.250
<v Aaron van Wirdum>Right, yeah, maybe that's an episode on its own, I guess.

00:29:08.670 --> 00:29:14.260
<v Aaron van Wirdum>Let's stick to Ocean for now. There's one other aspect about it

00:29:14.260 --> 00:29:19.320
<v Aaron van Wirdum>that's kind of controversial, which is that they're filtering for

00:29:19.320 --> 00:29:25.000
<v Aaron van Wirdum>quote-unquote spam. They're filtering transactions that they consider to be spam.

00:29:25.360 --> 00:29:30.730
<v Sjors Provoost>Yeah, so I believe to be precise, they are using Bitcoin Knots default settings

00:29:30.730 --> 00:29:36.630
<v Sjors Provoost>so that's an alternative version of Bitcoin Core by Luke Dashjr and it does not

00:29:36.630 --> 00:29:42.470
<v Sjors Provoost>relay transactions with an OP_RETURN of more than 20 bytes I believe so

00:29:42.470 --> 00:29:47.170
<v Sjors Provoost>that's less than the default in the default in Bitcoin Core and because it

00:29:47.170 --> 00:29:51.110
<v Sjors Provoost>doesn't relay them it doesn't have it in its mempool and so when it generates a

00:29:51.110 --> 00:29:52.870
<v Sjors Provoost>block template these things are not in there

00:29:53.780 --> 00:29:54.300
<v Aaron van Wirdum>Right.

00:29:54.420 --> 00:29:58.500
<v Sjors Provoost>It also does not have a transaction accelerator, right? So in general, these big

00:29:58.500 --> 00:30:00.060
<v Sjors Provoost>ordinal transactions are not in there.

00:30:01.710 --> 00:30:07.190
<v Sjors Provoost>The big ones, so I guess there's three things, right? Normal pools don't just,

00:30:07.450 --> 00:30:11.850
<v Sjors Provoost>they don't filter out stuff, mostly, with one exception that we talked about last

00:30:11.850 --> 00:30:15.890
<v Sjors Provoost>episode. But they also don't include very large things. They don't include

00:30:15.890 --> 00:30:17.810
<v Sjors Provoost>transactions over, I think it's 400 kilobyte.

00:30:20.200 --> 00:30:20.460
<v Aaron van Wirdum>Right.

00:30:20.460 --> 00:30:24.540
<v Sjors Provoost>But this pool doesn't put anything in there with OP_RETURNs more than 20 bytes.

00:30:24.960 --> 00:30:25.240
<v Aaron van Wirdum>Right.

00:30:26.440 --> 00:30:31.700
<v Aaron van Wirdum>Yeah, I guess I'm not really sure do you have an opinion on this let's just start

00:30:31.700 --> 00:30:36.720
<v Aaron van Wirdum>there or what would you I guess the problem or the critique or the controversy or

00:30:36.720 --> 00:30:41.720
<v Aaron van Wirdum>whatever you want to call it is that this would potentially make the pool less

00:30:41.720 --> 00:30:46.460
<v Aaron van Wirdum>profitable because if there's a transaction that pays a high fee but has a too

00:30:46.460 --> 00:30:50.200
<v Aaron van Wirdum>big OP_RETURN then this pool isn't going to Ocean pool is not going to include it

00:30:50.200 --> 00:30:51.460
<v Aaron van Wirdum>while another pool might

00:30:51.460 --> 00:30:56.240
<v Sjors Provoost>Yeah, but the most fair comparison would be another equivalent of Ocean pool

00:30:56.240 --> 00:31:00.600
<v Sjors Provoost>Ocean two pool which would include those transactions and then I think it's

00:31:00.600 --> 00:31:03.100
<v Sjors Provoost>fairly straightforward that the other pool would just make more money.

00:31:03.100 --> 00:31:07.780
<v Aaron van Wirdum>Yeah, well let's break it down a little bit so because I did discuss this with

00:31:09.390 --> 00:31:15.310
<v Aaron van Wirdum>Bitcoin Mechanic and also Jason, the CTO. So what they will argue, I just want to

00:31:15.310 --> 00:31:18.390
<v Aaron van Wirdum>mention what they will argue. So they will argue that this is not necessarily

00:31:18.390 --> 00:31:22.430
<v Aaron van Wirdum>true because there are... Yeah, so like you said... It's kind of an unfair

00:31:22.430 --> 00:31:25.730
<v Aaron van Wirdum>comparison if you compare it to other mining pools. So it's not necessarily true.

00:31:25.990 --> 00:31:29.450
<v Sjors Provoost>I think if you compare it to an Ocean 2 pool, it's very clear. It's better to

00:31:29.450 --> 00:31:33.030
<v Sjors Provoost>include more. But if you compare it to actual other pools, it's a different story.

00:31:33.610 --> 00:31:37.370
<v Aaron van Wirdum>Right, exactly. And the reason for that is that Ocean does have other benefits

00:31:37.370 --> 00:31:40.530
<v Aaron van Wirdum>that other pools don't have, including profitability benefits.

00:31:42.700 --> 00:31:48.580
<v Aaron van Wirdum>One obvious example is some of the pools have... Once in a while, there's

00:31:48.580 --> 00:31:52.100
<v Aaron van Wirdum>this thing in the news that someone accidentally paid 100 Bitcoin fee or

00:31:52.100 --> 00:31:52.840
<v Aaron van Wirdum>something like that.

00:31:52.980 --> 00:31:54.040
<v Sjors Provoost>That seems to be a trend.

00:31:54.380 --> 00:31:59.650
<v Aaron van Wirdum>And then the mining pool will pay it back. Just because they're being nice to

00:31:59.650 --> 00:32:01.710
<v Aaron van Wirdum>whoever accidentally included that high fee.

00:32:01.930 --> 00:32:05.950
<v Sjors Provoost>They may be nice or they may not want to get sued. Some combination of both.

00:32:06.410 --> 00:32:10.790
<v Aaron van Wirdum>In either case, Ocean will not do that because they essentially cannot.

00:32:11.530 --> 00:32:13.450
<v Sjors Provoost>They can, but they [unclear]…

00:32:13.650 --> 00:32:17.170
<v Aaron van Wirdum>No, they cannot because the hashers are directly paid from the coinbase. So now

00:32:17.170 --> 00:32:20.210
<v Aaron van Wirdum>the hashers themselves have to decide if they want to give it back or not.

00:32:21.090 --> 00:32:22.610
<v Sjors Provoost>Yeah, that's true for the first.

00:32:23.910 --> 00:32:27.650
<v Sjors Provoost>But it depends. So it depends on how quickly they figure out it's an accident. If

00:32:27.650 --> 00:32:31.290
<v Sjors Provoost>they figure it out while it's in the mempool, they could theoretically not mine

00:32:31.290 --> 00:32:37.010
<v Sjors Provoost>it, I guess. That would be the easiest thing. Or they could mine it and then not

00:32:37.010 --> 00:32:40.590
<v Sjors Provoost>include it in the rewards for those people. But that would obviously require some

00:32:40.590 --> 00:32:44.260
<v Sjors Provoost>serious intervention and some very quick intervention. Now the miners…

00:32:43.590 --> 00:32:45.610
<v Aaron van Wirdum>Right now they're not doing it.

00:32:45.870 --> 00:32:50.230
<v Sjors Provoost>No, and the miners that they pay out after 100 blocks, they have 100 blocks to

00:32:50.230 --> 00:32:53.630
<v Sjors Provoost>think about it. So they could again you know but then you would be treating the

00:32:53.630 --> 00:32:59.290
<v Sjors Provoost>first 20 miners different from the from the the rest so yeah it's certainly a lot

00:32:59.290 --> 00:33:02.370
<v Sjors Provoost>less easy for them to decide that on behalf of the individual miners

00:33:02.370 --> 00:33:07.670
<v Aaron van Wirdum>Yeah, another argument would be that FPPS which I mentioned which most people use

00:33:07.670 --> 00:33:11.730
<v Aaron van Wirdum>which is that the mining pool basically just pays you for a hash power yeah is

00:33:11.730 --> 00:33:14.910
<v Aaron van Wirdum>essentially undervalued and one of the reasons for that is that

00:33:17.660 --> 00:33:22.600
<v Aaron van Wirdum>miners will collect out-of-band payments. Wait, I don't know if it makes sense

00:33:22.600 --> 00:33:23.260
<v Aaron van Wirdum>what I just said.

00:33:23.420 --> 00:33:28.100
<v Sjors Provoost>Well, so the problem is more about transparency. So if we very briefly explain

00:33:28.100 --> 00:33:33.360
<v Sjors Provoost>FPPS, it is... basically saying that you would get paid for the hash power that

00:33:33.360 --> 00:33:37.840
<v Sjors Provoost>you're putting into it, which is then how much sats should you be paid for your

00:33:37.840 --> 00:33:41.700
<v Sjors Provoost>hash power? And that calculation is based on the block reward plus the sort of

00:33:41.700 --> 00:33:45.520
<v Sjors Provoost>the expected fees or the average fees over time or some whatever complicated

00:33:45.520 --> 00:33:50.220
<v Sjors Provoost>algorithm. It's not that trivial to compare. So when a miner receives, when such

00:33:50.220 --> 00:33:55.990
<v Sjors Provoost>a pool processes payments out of bound, like an accelerator, they may or may not

00:33:55.990 --> 00:34:00.850
<v Sjors Provoost>pay their miners for that. It's non-trivial to figure out if that's happening or not.

00:34:01.010 --> 00:34:01.390
<v Aaron van Wirdum>Right.

00:34:01.770 --> 00:34:05.050
<v Sjors Provoost>Whereas in this pool example, it's very clear when it's not happening.

00:34:05.430 --> 00:34:05.610
<v Aaron van Wirdum>Right.

00:34:06.890 --> 00:34:12.170
<v Aaron van Wirdum>In either case, I think we both sort of agree that if there was an Ocean 2 pool

00:34:12.170 --> 00:34:16.870
<v Aaron van Wirdum>that just does everything exactly the same as Ocean and somehow they also have

00:34:16.870 --> 00:34:20.310
<v Aaron van Wirdum>the same size and the same hash power, the same variance, the same luck.

00:34:21.780 --> 00:34:26.660
<v Aaron van Wirdum>And Ocean does not include these transactions while Ocean 2 pool would, then

00:34:26.660 --> 00:34:31.200
<v Aaron van Wirdum>Ocean 2 pool would at least be as profitable and usually more profitable.

00:34:31.540 --> 00:34:37.070
<v Sjors Provoost>Yes, and Ocean 2 pool could also have an out-of-band transaction accelerator and

00:34:37.070 --> 00:34:41.410
<v Sjors Provoost>not pay the individual miners. However, it would be kind of obvious that their

00:34:41.410 --> 00:34:46.230
<v Sjors Provoost>transactions being included at a implausibly low fee. And so as a miner, you

00:34:46.230 --> 00:34:49.650
<v Sjors Provoost>would definitely notice that and you'd say, hey, I am definitely not getting sats

00:34:49.650 --> 00:34:53.010
<v Sjors Provoost>for that. Because I can see exactly how many sats I am getting from these

00:34:53.010 --> 00:34:57.180
<v Sjors Provoost>transactions. So, you know, somebody's getting the sats and it's not me,

00:34:57.300 --> 00:35:00.820
<v Sjors Provoost>therefore, you know, maybe I'll switch to another pool or... Yeah.

00:35:01.220 --> 00:35:01.360
<v Aaron van Wirdum>Right.

00:35:02.810 --> 00:35:04.410
<v Aaron van Wirdum>Yeah, just to point this out,

00:35:05.850 --> 00:35:10.910
<v Aaron van Wirdum>Jason and Mechanic also disagree with this, or at least they weren't necessarily

00:35:10.910 --> 00:35:16.670
<v Aaron van Wirdum>agreeing. They seem to be disagreeing. They seem to... Their argument was that...

00:35:17.170 --> 00:35:21.670
<v Aaron van Wirdum>There could be more complex things going on, like child pays for parents type of

00:35:21.670 --> 00:35:25.930
<v Aaron van Wirdum>stuff that Ocean 2 pool would not see, and Ocean pool, like their pool, would

00:35:25.930 --> 00:35:29.510
<v Aaron van Wirdum>actually include, and therefore they would still be more profitable.

00:35:29.870 --> 00:35:33.230
<v Sjors Provoost>The way you're describing that to me makes no sense, but that is because it's

00:35:33.230 --> 00:35:34.910
<v Sjors Provoost>like a Chinese Whispers game, so.

00:35:35.510 --> 00:35:41.150
<v Aaron van Wirdum>Yeah, right. I'm just sort of trying to convey someone else's argument here,

00:35:41.310 --> 00:35:46.640
<v Aaron van Wirdum>which I'm not very convinced by, but, you know, I am trying my best.

00:35:46.640 --> 00:35:51.600
<v Aaron van Wirdum>In the case anyone is wondering the reason we don't have them on the podcast is

00:35:51.600 --> 00:35:57.010
<v Aaron van Wirdum>because we just want to do our podcast in person not over calls or internet or

00:35:57.010 --> 00:35:59.310
<v Aaron van Wirdum>Zoom or whatever else is available.

00:35:59.310 --> 00:36:02.350
<v Sjors Provoost>Exactly, which is also the reason why we didn't do a lot of episodes in the last

00:36:02.350 --> 00:36:06.350
<v Sjors Provoost>couple of months Right, but we are back in this very cold country and I guess

00:36:06.350 --> 00:36:07.130
<v Sjors Provoost>that's all.

00:36:07.130 --> 00:36:08.210
<v Aaron van Wirdum>I think so.

00:36:08.210 --> 00:36:10.770
<v Sjors Provoost>Sure. All right, then thank you for listening to Bitcoin,

00:36:10.770 --> 00:36:11.550
<v Aaron van Wirdum>Explained.

