In this episode of Bitcoin, Explained, Aaron and Sjors explain what features are offered by Ocean, the relaunched and rebranded Eligius mining pool. They discuss how payouts from this pool are (partially) non-custodial, how the block template creation is fully transparent, and how payout distribution is determined. Aaron and Sjors also briefly touch on the “spam” filtering employed by Ocean, and how that potentially affects profitability of the pool. Our new sponsor: CoinKite, maker of the ColdCard Chapters 00:00:00 Introduction and Coinkite sponsorship 00:01:01 Ocean launches: reviving Eligius and decentralizing mining 00:02:08 Custody-minimized mining and direct coinbase payouts 00:06:40 Payout limits, hardware constraints and small miners 00:10:18 Future payouts with Lightning and CHECKTEMPLATEVERIFY 00:12:28 Transparent block templates and Stratum V2 00:15:06 Mining shares: proving work to a pool 00:17:05 TIDES: sharing rewards through a rolling work window 00:24:56 Block luck, difficulty and the TIDES accounting window 00:29:08 Transaction filtering, fees and pool profitability
Audio and video play straight from the show's own hosting. PodSubs stores and serves no media.
Transcript
From the show. Tap a time to play from there.
Aaron van WirdumLive from Utrecht, this is Bitcoin.
Sjors ProvoostExplained.
Aaron van WirdumHey, Sjors.
Sjors ProvoostHello.
Aaron van WirdumSjors, we have a sponsor.
Sjors ProvoostThat is correct. We have a new sponsor.
Aaron van WirdumIsn't that great?
Sjors ProvoostThat's right. Our new sponsor is Coinkite, the company behind the COLDCARD. And dear listener, if you have no idea what a COLDCARD is, please let us know because then we'll explain it because otherwise it's a bit ridiculous if we explain it because we, I think we, we think you all know.
Aaron van WirdumOh my God, this is the worst ad read in history, Sjors.
Sjors ProvoostExcellent.
Aaron van WirdumCan we at least mention it's a hardware wallet?
Sjors ProvoostYes, it's a hardware wallet.
Aaron van WirdumIt's a hardware wallet you can use to store Bitcoin. All right, Sjors, today we're going to discuss a new mining pool launched. Well, kind of. Ocean pool. I was invited to the launch event. It was sort of a mini conference.
Sjors ProvoostI felt a very strong FOMO for that one. I saw the the video uh you guys were in the middle of nowhere and some like like video like some horror movie video shoot game basically scene right?
Aaron van WirdumYeah well it was quite nice actually. There was like this hydro plant uh very what's a good english word for this? Rustic I don't know if that's the right word maybe but it was nice let's just say it was nice nice environment, And yeah they launched this pool so it's really the relaunch or re-brand or re-something of Eligius, if that's how I pronounce that pool, the Luke Dashjr pool. This time it's backed by Jack Dorsey, among other investors.
Aaron van WirdumAnd their goal, their intention is to re-decentralize mining, essentially, or decentralize mining.
Sjors ProvoostRight, and they're calling it Ocean.
Aaron van WirdumYeah, didn't I mention that?
Sjors ProvoostNo.
Aaron van WirdumOkay, yes, Ocean, Ocean pool. Um, yeah so decentralizing mining pools or at least this one or mining in general ultimately is the goal. The sort of most notable innovation that they started with that they launched with is they have this non-custodial setup kind of or I mean that's that's the goal that's the intention that's the…
Sjors ProvoostYeah, I guess uh one diplomatic way to call it would be custody minimized I mean, you can have long legal discussion about what custody means, but I think we care most about the technical sides of it.
Aaron van WirdumRight.
Sjors ProvoostAnd then you can ask practical questions like, could the mining pool steal your money? Could they be forced to steal your money? Et cetera, et cetera. And we can try to get into some of the nuance there of what they're actually doing.
Aaron van WirdumSo to clarify this, what mining pools usually do is... well I don't want to get into the whole thing but basically when a mining pool finds new coins the mining pool gets these coins. And in fact these coins can't be spent for 100 blocks right? Yeah and then after these 100 blocks well that's actually not what happens with most pools um I was I was going to say after 100 blocks these coins are distributed to the miners, but that's not actually how
Aaron van Wirdummining pools work.
Sjors ProvoostI would say there's a bigger separation there, right? The mining pool as a whole has a wallet and the coins they earn go into that wallet and the miners are paid from that wallet. But it is a bit of an omnibus and not necessarily trivial to understand which [unclear] belongs to which specific individual miner.
Aaron van WirdumYeah, a way that they will explain it or Bitcoin Mechanic, for example, is essentially... Most Bitcoin miners or hashers, as we've also called it, aren't actually mining Bitcoin. They're just selling their hash power to a mining pool, basically. And the pool operator is the one that's actually...
Sjors ProvoostWell, that sounds a little bit like a separate issue, though it's a bit related to whether you're really... What it is that you're doing as a miner, are you producing blocks or are you just delivering hash rate to a buyer? And that depends on the... uh the incentive model the the exact business model. I think we'll get into that a bit later. But the idea of holding coins custody you know you could you could do that with this model too I think you just don't have to.
Aaron van WirdumRight. Yeah, it is a slightly separate issue. I just wanted to point it out real quick but yes. Uh yeah so the main innovation here is essentially that hashers as well they'll call them, So to clarify that there's the mining pool or the mining pool operator that's you know doing most of the Bitcoin stuff you know downloading blockchain and constructing the blockchain template which is a big part of it which might not happen in the future with Stratum V2 but we've made another episode about that at least right now most mining pools still create
Aaron van Wirdumblock templates or which transactions go into a block and I lost my train of thought but I think I was going to say with Ocean uh The new coins are directly paid to the hashers. Oh, I was still explaining that.
Sjors ProvoostThe coinbase transaction, which is what every new block contains, has a number of outputs. And typically these just go to the general wallet of the pool. But with this new Ocean pool, as much as possible, the coinbase transactions go directly to the miners.
Aaron van WirdumRight.
Sjors ProvoostWith the caveat that you cannot do that for all mine transactions. Not for all miners, And the two reasons…
Aaron van WirdumLet's get into that. First let's point out some advantages of this and the biggest one is probably… So right now if you're a hasher and you want to join a pool most pools have sort of KYC stuff going on like you need to actually tell the pool who you are at least some of the big ones have this and Ocean does not have this.
Sjors ProvoostYeah, but I don't think that's inherent to this model at all like you could still have KYC in this model or not
Aaron van WirdumYeah. So, well, I mean, I guess in their view or what they will argue or what they think or what they believe is that it's sort of this way it's legally possible to not do KYC.
Sjors ProvoostWell, we're not lawyers. I'm a developer. You're a journalist.
Aaron van WirdumRight.
Sjors ProvoostBut let's...
Aaron van WirdumBut in any case, they aren't doing KYC stuff. That's for sure. Right now you can just plug in and start mining.
Sjors ProvoostOne thing that they're doing very practically is that you as a miner don't create an account or you don't have to. You just provide an... um but a Bitcoin address straight as you're directly from the miner.
Aaron van WirdumRight. Okay, so you mentioned so you so you get paid directly from the coinbase as a hasher to the extent that it is possible
Sjors ProvoostYeah, and that extent is quite limited because of two reasons. One is a coinbase transaction can only have this many outputs. Or even if you could have as many as you want, at some point it's just not worth paying the fees. Or not so much paying the fees because the coinbase transaction doesn't pay fees, but you are foregoing, you know, you're using up space that others could pay, you know, that other people are paying you fees as a pool. So if you make a one megabyte coinbase transaction, then you can do that and you pay zero fees for it, but you
Sjors Provoostare now no longer mining anything.
Aaron van WirdumRight, well, you could create a four megabyte coinbase transaction.
Sjors ProvoostI don't think so, because there's no witness.
Aaron van WirdumMaybe two? Oh, right. Okay, let's separate these issues. So first of all, you said you can't necessarily pay every hasher because the number of outputs in the coinbase transaction is limited?
Sjors ProvoostOr at least, I don't know if there's an actual limit there that matters, but basically it's just not worth the opportunity cost of making very small payments in the coinbase.
Aaron van WirdumOh, so it's the same issue. There is no actual limit to the number of outputs in the coinbase transaction.
Sjors ProvoostI think it's just the regular transaction, whatever that limit is. It might not be one. I should know that, I guess. So the second limit is a little bit more mundane. Apparently some of the mining hardware out there starts to panic if you put more than 20 outputs in a coinbase transaction. So that has nothing to do with the Bitcoin limits. It's just that some mining equipment... just panics when there's too many outputs. So in practice, the limit is about 20. So the 20, and in this case, the top 20 miners get paid directly from the
Sjors Provoostcoinbase. Then there's some amount left, and that essentially goes to a wallet, you could say. But they make sure that... from that wallet after 100 blocks because then you can spend it it immediately goes to the correct miners as if they were part of the coinbase essentially.
Aaron van WirdumRight. Okay, so we just so I thought wrongly probably that there was a limit on the number of transactions on the coinbase output and you just said that's probably not the case but there some hardware has this issue that's that's where the limit comes from yeah okay and you say that limit is 20.
Sjors ProvoostApparently roughly 20.
Aaron van Wirdum20-ish. Okay, there can only be 20 transaction outputs from a coinbase transaction.
Sjors ProvoostSo that secondary transaction, which can only happen after 100 blocks because of the coinbase maturity rule, that's a consensus rule, that transaction is kind of just like it was part of the coinbase itself, right? It also has the same fee trade-offs here where, yes, you can put whatever giant transaction you want in there as a pool, but then you're foregoing fee revenue from other transactions. This transaction just spends from the coinbase.
Aaron van WirdumOkay, so if there's just if there's just too many hashers that need to be paid from the coinbase if it's more than 20 essentially then some of them will be paid later still as soon as possible but later and then the other thing was if you mine if your hash if your hasher and you don't earn enough from a block then you'll only also won't get paid immediately.
Sjors ProvoostRight. So then the idea is to basically wait until you've accumulated enough credit, as it were, and then you get paid. So there it really starts looking like just a wallet that's custodial, but only for small amounts.
Aaron van WirdumRight. OK, so that's how it works today. And then there are some ideas in the future for the future to improve that a little bit more. So one of them is using Lightning for payouts.
Sjors ProvoostYeah, that kind of makes intuitive sense when you have very small miners that want to collect small rewards. Maybe they get like 20 satoshis every block. Lightning is a way to do that. And then the question is, can you, you know, how non-custodial can you make Lightning? I believe if you listen to the Stephan Livera podcast, Bitcoin Mechanic explains some ideas of how to do that roughly. using, I believe, some sort of market where, like, if you have Lightning liquidity, you essentially buy the rights to the payouts from the pool. So the
Sjors Provoostpool is not doing the Lightning payouts. They're just giving payouts to addresses, but then somebody else does some swapping of who gets which coins.
Aaron van WirdumRight. And then there's another potentially cool idea, which is not possible yet on the Bitcoin network, but with CHECKTEMPLATEVERIFY it could actually be implemented that if this 20 limit threshold in the coinbase is reached, then the other hashers are still guaranteed their payment through a CTV transaction.
Sjors ProvoostAnd even better than that, regardless of this 20 limit, right now, if you're putting something, you have to put the addresses in the coinbase right now. And so you kind of don't want to do that when fees are really high because that's an opportunity cost. But maybe you want to pay people when fees are low. So CTV is quite interesting for that. We have not really discussed it in any podcast, but it's basically a soft fork proposal that commits to certain transactions happening in the future. And one of the intended use cases is congestion control.
Sjors ProvoostAnd this would be a very nice use case for it, where the coinbase only has one output or maybe a couple, which is the CTV transaction. And then all the miners know for sure that they will get those coins, but they'll wait until fees are low and then they'll get them.
Aaron van WirdumRight. All right. That was the non-custodial part of the pool, which is probably kind of the main innovation, but it's not the only thing going on.
Sjors ProvoostYeah. Or the custody minimized part of the pool. Right.
Aaron van WirdumAll right. I'm sorry, Sjors. You're very right. The other thing is... um so the the block template is transparent so usually at most pools right now because they have this FPPS model which I briefly mentioned earlier where hashers are basically just selling their hash power to a mining pool and the mining pool just makes a block with it. Now on Ocean it's completely transparent what the block will actually look like that everyone is
Aaron van Wirdumworking on right?
Sjors ProvoostYeah, so I don't know how inherent this limitation is in normal pools I do know that Stratum V2 doesn't have this problem in Stratum V2 you know exactly what you're mining but in this case Ocean pool will show you what you're mining without even using Stratum V2 and typically you don't know what you're mining you just get a hash and you're grinding away on that hash um now you can go to at least you can go to an API and check and this could be interesting especially for bigger miners because bigger miners they're paid directly from the coinbase so they can see that they're mining a block that pays them like they know for sure
Sjors Provoostum smaller miners again with the CTV technique they might also be able to check this uh probably not in real time right because you don't want to spend 10 seconds calculating if you're If you're mining the correct block, you just want to start mining. But you can at least, within a few seconds, see, hey, I'm being scammed. I'm going to stop mining now. So that's quite nice for tiny miners that have to be paid through Lightning. I don't think this offers any benefit in terms of knowing that you're going to be paid. But you still know what you're mining. You might realize that you're censoring certain stuff that you're not happy with,
Sjors Provoostetc. So that's good.
Aaron van WirdumYeah, the counter or one of the examples that Bitcoin Mechanic, for example, will bring up is that... There have been pools that have mined blocks that are basically one big inscription or have big inscriptions in them, and hashers had no idea that that's what they were doing. Now, maybe they also don't care that that's what they're doing, but maybe they do care. In any case, with Ocean, hashers will actually know what they're doing.
Sjors ProvoostYeah, but also with Stratum V2, I believe, they'll know.
Aaron van WirdumSo, yeah about Stratum V2 uh we already made an episode about that and I was also already mentioned that but um it does seem like that sort of on the roadmap for Ocean but they don't
Sjors ProvoostI'm sure it is but I'm always skeptical of roadmaps. Right right show it to me.
Aaron van WirdumYeah, they don't have it now yet in any case
Sjors ProvoostI'm sure they will but they don't have it yet.
Aaron van WirdumAll right and then we get to possibly the most complex topic of all of them. Yesterday, we had a sort of preparation call with, also with Bitcoin Mechanic and with the CTO of the pool, Jason Hughes, and it was one of these calls where I was on it and Sjors was just sort of going on adventure with the CTO and I couldn't really keep up with everything you were discussing. So let's see what
Aaron van Wirdumyou've figured out.
Sjors ProvoostYeah, so in case people think that I confidently understand stuff spontaneously, no, that takes a lot of effort.
Aaron van WirdumRight. Okay, so... I'm barely even sure how to introduce this.
Sjors ProvoostWell, I think we should generally talk about shares a little bit without any of the crazy mechanics that are being used generally. But the idea is if you are mining, you need to prove to the pool that you are actually doing some work.
Aaron van WirdumYeah, how does the pool decide which hashers get how much Bitcoin?
Sjors ProvoostAnd I think we discussed this also in the Stratum V2 episode, by the way, so you could re-listen to that. But the general idea is that you will mine a block with a much, much, much lower difficulty. And for example, the block that you're trying to mine, the pool wants to see it if it is like a thousand times easier than the real block.
Aaron van WirdumYeah, you're basically mining invalid blocks.
Sjors ProvoostYeah, but they're not randomly invalid. They are like as if the proof of work difficulty was still at the level it was when Satoshi started, basically. And the nice thing is that when you do that... You cannot lie about it. You are providing proof of work, just a little bit less proof of work because you're only sharing it with the pool operator and not the whole internet.
Aaron van WirdumYeah.
Sjors ProvoostSo it's fine to have a little bit more spam. And generally, they'll aim to have like eight blocks a second, sorry, eight blocks per minute. That's, I believe, often an interval.
Aaron van WirdumYou're basically proving to the pool that you're at least trying to find a block.
Sjors ProvoostExactly.
Aaron van WirdumRight.
Sjors ProvoostAnd then occasionally you will find a block.
Aaron van WirdumRight. Exactly. And then, yes. Okay, so Ocean has this way, it's called TIDES. So how do you decide which hasher gets how much Bitcoin?
Sjors ProvoostYeah, that is the hard question. And I think we'll also get a little bit into how other pools do that. But I actually don't really understand how other pools do it. And I think I do understand how this pool does it. Because I think it's a fairly elegant and simple system.
Aaron van WirdumWell, I think how other pools do it is that's the FPPS system, right? So basically a pool just says... we'll pay you X amount of Bitcoin for X amount of hashes. And that's just it.
Sjors ProvoostYeah, but there's a little nuance of how much X is.
Aaron van WirdumHow X is calculated, you mean? Yeah. I've never really looked into that, and let's skip that. That's the easiest thing to do here. And let's get into how Ocean actually does it.
Sjors ProvoostRight, that was sort of the idea. Okay, so basically the idea is that there is a bucket, or it's not really a bucket, it's a queue, and you are adding work, little loads of work, little shares of work, into a queue. Let's say the two of us are mining, I've got my little vintage S9 that I've clocked down to 1 terahertz, a terahash, so that it uses less power and makes less noise, and it can sit here in my living room, basically, without driving me nuts.
Sjors ProvoostAnd you have the same, so we're each hashing away.
Aaron van WirdumIt's just not clocked down and it's driving me crazy because I don't know how to do that.
Sjors ProvoostOh.
Aaron van WirdumGo on.
Sjors ProvoostAnyway, so both of us are mining and what we do is to the pool, we're proving that we're doing this amount of work. And so the pool is keeping track of that. You're submitting a share, I'm submitting a share, you're submitting a share, I'm submitting a share. And over time, this builds up. And eventually a block is found and then... In the simplest case, we've both submitted the same number of shares. And, you know, the shares are adjusted for how strong our miners are. But in this case, we assume the miners are equally strong. The block arrives,
Sjors Provoostthen half the coinbase transaction output goes to me. Half the coinbase output transaction goes to you. This is very simple. Now, let's... So this bucket of shares does not fill up to infinity. So if we do this for a few years, then the division who gets how much does not depend on the total amount of shares we submitted throughout history, but it only depends on the recent past. It's kind of like a rolling window.
Aaron van WirdumHow recent?
Sjors ProvoostThe equivalent, so this is where it gets a little more complicated, is the equivalent of eight blocks of work for the whole network. So the number of hashes, or sorry, the number of shares it would take, statistically, to produce eight blocks. You know, with my miner, that would be, I don't know, two million years worth of blocks or something. Or two million years worth of mining, let's say, and for you, the same thing. But as soon as the mining pool has more shares than that, it
Sjors Provooststarts discarding old shares, or at least it starts ignoring them. Um, so it's, and so in practice, um, let's take another example where we actually have to really find a really fast miners. In fact, our miners are, uh, as fast as the whole Bitcoin network. Um, somehow we've turned off all the other miners in the network. And so this, this Eligius pool, sorry, the Ocean pool is now the only pool and we are continuing with the Bitcoin network at the same hash power. So just to keep the,
Sjors Provoostuh, the analogy a bit simple here.
Aaron van WirdumYes. Please.
Sjors ProvoostYes. Now, in this case, actually, sorry, our miners are a little bit different. That is, my miner is as strong as the entire Bitcoin network is and your miner is as strong as the entire Bitcoin network is. I'm going to turn it on. You're not. And then at the end, you're going to turn it on and I'm going to turn it off. Because then the question is, how much do we get?
Aaron van WirdumRight.
Sjors ProvoostSo let's take the simplest possible example or about... 40 minutes, I turn it on, and then for 40 minutes, you turn it on, and by just complete coincidence, blocks are found exactly every 10 minutes. So then the question is, what happens? Initially, I turn it on first, right? So initially, I get everything for the first block, second block, third block, fourth block, because I was the only one mining, and I'm the only one in the history, ignoring that there's a further
Sjors Provoostpast. Now, you turn on your miner and I've turned off mine. So what happens in the next block? Well, it's looking back at the equivalent of eight blocks, which is more than so far what we've collected. And so you are going to get one-fifth and I'm going to get four-fifths of the next block.
Aaron van WirdumThat sounds very unfair.
Sjors ProvoostIt doesn't because if we look at that history for the last eight blocks, you have done one-fifth of the work and I've done four-fifths of the work.
Aaron van WirdumYes, but now I'm not getting one-fifth of the Bitcoin.
Sjors ProvoostYou are getting one-fifth of Bitcoin.
Aaron van WirdumNot of all Bitcoins that have been issued so far.
Sjors ProvoostNo, you're getting one-fifth of the next block. Yeah, it's always what you get in the next block. Now the block after that...
Aaron van WirdumFeels like I'm being scammed here, Sjors.
Sjors ProvoostI don't think so. I think the next block, you're getting two-sixths of it. Then the next block, you're getting three-sixths of it. And then the next... Sorry, three-seventh of it. And then the next block, you're getting half of it. Four out of eight. Because now you have done half the work in the past eight blocks.
Aaron van WirdumI'm still being scammed like you got all the bitcoins of the first four and you still get part of the bitcoins of the last four
Sjors ProvoostEven though it sounds pretty evil doesn't it?
Aaron van WirdumYes.
Sjors ProvoostBut now uh we continue in time and you keep hashing and I don't and it goes up you get five eight six eight seven eight eight eight you get all of it
Aaron van WirdumYeah, but now I still did two thirds of the work Sjors and I didn't get two thirds of the Bitcoin I think Anyways, I do think probably if you keep the logic going long enough, then it will probably work out. But so far, I'm still being scammed here.
Sjors ProvoostI don't think you're getting scammed, but it is true that it's a bit hard to reason about it because one of the problems is if you stop and there's no other miner, then you get nothing, right? But if I then take over, you will continue to get rewards for the next eight blocks or so. It'll decrease as your work goes back into the past. So I think it works out.
Aaron van WirdumYeah, well, wasn't there a thing that with the actual first eight blocks, so including the actual first eight blocks that I think Ocean is mining, the logic is a bit different. So aren't you now explaining the logic that will work fine later on, but not for the first eight?
Sjors ProvoostNo, I think it was fine for the first eight too, because we are simply splitting the work between us in that case.
Aaron van WirdumNo, but we just established that I got scammed.
Sjors ProvoostI don't think you got scammed. I think you're just bad at math. But I don't know for sure either.
Aaron van WirdumSurely I'm not bad at math. Like in your example, you mined the first four and I mined the last eight. and we're still splitting the coins 50 the total coins 50 50
Sjors ProvoostSo, so you've mined the last eight but you still will get rewards in the future right so you haven't had it yet but you will get it.
Aaron van WirdumRight, right, right, right.
Sjors ProvoostBut somebody has to do the mining so the question then is, When when is that game done? Well if I then take over you will get the part that you still owed.
Aaron van WirdumRight, yes. Okay, now that actually makes sense. And [unclear], I am bad in math. But in this case, I was still kind of right, I think. But yes, you're right.
Sjors ProvoostSo now let's take a slightly different experiment because in reality, blocks do not arrive every 10 minutes. And so the question then is, well, what if blocks arrive really quickly and then it takes a really long time? How does that division work, right? It's not that the blocks, that the rewards are equally divided between the actual blocks. It's based on the effort you're putting into the system. So an example that I just wrote down this morning or afternoon would be this. I am mining...
Sjors ProvoostI mine seven blocks. Again, we are the entire pool. I mine seven blocks, one every minute. And then I stop and you start mining. And only after two hours... you find block number eight.
Aaron van WirdumBut that's just because of bad luck in your example, right?
Sjors ProvoostYes.
Aaron van WirdumIt's not lower hash power on my end, it's bad luck.
Sjors ProvoostIt's just bad luck.
Aaron van WirdumYeah, okay.
Sjors ProvoostAnd so in this scenario, I got lucky. Well, again, this is kind of the bootstrapping problem, but if we kind of ignore that, I get lucky the first seven times I get 100% of the work of the coins, even though I only mine for seven minutes. That's just because of the luck. And then, but you have been mining now for eight hours, or sorry, two hours, or one hour and 53 minutes, whatever you want to say. The question then is, and you find a block, how much do you get and how much do I get?
Aaron van WirdumI mean, judging by your logic so far, I'm going to be scammed somehow, so tell me.
Sjors ProvoostNo, you get 100%.
Aaron van WirdumOf what?
Sjors ProvoostOf the reward in that eighth block.
Aaron van WirdumOh, right so this is because statistically there's been eight blocks on the network even though there haven't right
Sjors ProvoostYeah, or in you know the accounting system is checking how much work you submitted and you have submitted more than eight blocks worth of work now because it's two hours so that's about you know normally you'd expect 12 blocks in that time period. So you have submitted eight blocks roughly equivalent worth of work, and therefore all the old stuff that I submitted no longer counts for the accounting. You get all of it. You still got unlucky, but in a way it's fair. That depends on your definition of fair, but yeah. But this is to make the
Sjors Provoostdistinction between... It's not actually eight blocks. It's not the last eight blocks. It's about the equivalent amount of work that went into the pool.
Aaron van WirdumYes, and that's calculated just based on the difficulty?
Sjors ProvoostYes, that is exactly. That's based on the current difficulty. So it gets a bit more complicated, I guess, if the difficulty goes up or down. But every two weeks, you know, the difficulty is constant and then it changes once. So as long as you don't go over that boundary, the math is pretty simple. But this is, I believe, also one reason why old shares are not thrown away. Because you could be in a situation where the difficulty goes up, and now the equivalent of eight days is more than it was before, and so you need to go back in time and look into the log of the people that were doing something a little bit before the window.
Sjors ProvoostLet's say the difficulty doubles overnight. Now you're looking at the equivalent of eight days, which is, in reality, would have been 16 days of actual work, if you're looking at the past. So you cannot throw away the past, Or at least, you know, not unreasonably.
Aaron van WirdumAll right. Well, I'm glad you sort of understand this part of the Ocean pool. Did we cover this part sufficiently, you think?
Sjors ProvoostI think so.
Aaron van WirdumOkay, good.
Sjors ProvoostYeah, so the funny thing is we did not cover a number of topics that are quite popular when talking about mining pools. We did not talk about pool hopping. We did not talk about PPS and FPPS and all these different rewards.
Aaron van WirdumI did.
Sjors Provoost[unclear]. But not in much detail. Partially it's because I don't fully understand those systems. But partially it's because we already explained this system and you guys are getting tired and our editor is getting tired. So we might actually come back to it some other time.
Aaron van WirdumRight, yeah, maybe that's an episode on its own, I guess. Let's stick to Ocean for now. There's one other aspect about it that's kind of controversial, which is that they're filtering for quote-unquote spam. They're filtering transactions that they consider to be spam.
Sjors ProvoostYeah, so I believe to be precise, they are using Bitcoin Knots default settings so that's an alternative version of Bitcoin Core by Luke Dashjr and it does not relay transactions with an OP_RETURN of more than 20 bytes I believe so that's less than the default in the default in Bitcoin Core and because it doesn't relay them it doesn't have it in its mempool and so when it generates a block template these things are not in there
Aaron van WirdumRight.
Sjors ProvoostIt also does not have a transaction accelerator, right? So in general, these big ordinal transactions are not in there. The big ones, so I guess there's three things, right? Normal pools don't just, they don't filter out stuff, mostly, with one exception that we talked about last episode. But they also don't include very large things. They don't include transactions over, I think it's 400 kilobyte.
Aaron van WirdumRight.
Sjors ProvoostBut this pool doesn't put anything in there with OP_RETURNs more than 20 bytes.
Aaron van WirdumRight. Yeah, I guess I'm not really sure do you have an opinion on this let's just start there or what would you I guess the problem or the critique or the controversy or whatever you want to call it is that this would potentially make the pool less profitable because if there's a transaction that pays a high fee but has a too big OP_RETURN then this pool isn't going to Ocean pool is not going to include it while another pool might
Sjors ProvoostYeah, but the most fair comparison would be another equivalent of Ocean pool Ocean two pool which would include those transactions and then I think it's fairly straightforward that the other pool would just make more money.
Aaron van WirdumYeah, well let's break it down a little bit so because I did discuss this with Bitcoin Mechanic and also Jason, the CTO. So what they will argue, I just want to mention what they will argue. So they will argue that this is not necessarily true because there are... Yeah, so like you said... It's kind of an unfair comparison if you compare it to other mining pools. So it's not necessarily true.
Sjors ProvoostI think if you compare it to an Ocean 2 pool, it's very clear. It's better to include more. But if you compare it to actual other pools, it's a different story.
Aaron van WirdumRight, exactly. And the reason for that is that Ocean does have other benefits that other pools don't have, including profitability benefits. One obvious example is some of the pools have... Once in a while, there's this thing in the news that someone accidentally paid 100 Bitcoin fee or something like that.
Sjors ProvoostThat seems to be a trend.
Aaron van WirdumAnd then the mining pool will pay it back. Just because they're being nice to whoever accidentally included that high fee.
Sjors ProvoostThey may be nice or they may not want to get sued. Some combination of both.
Aaron van WirdumIn either case, Ocean will not do that because they essentially cannot.
Sjors ProvoostThey can, but they [unclear]…
Aaron van WirdumNo, they cannot because the hashers are directly paid from the coinbase. So now the hashers themselves have to decide if they want to give it back or not.
Sjors ProvoostYeah, that's true for the first. But it depends. So it depends on how quickly they figure out it's an accident. If they figure it out while it's in the mempool, they could theoretically not mine it, I guess. That would be the easiest thing. Or they could mine it and then not include it in the rewards for those people. But that would obviously require some serious intervention and some very quick intervention. Now the miners…
Aaron van WirdumRight now they're not doing it.
Sjors ProvoostNo, and the miners that they pay out after 100 blocks, they have 100 blocks to think about it. So they could again you know but then you would be treating the first 20 miners different from the from the the rest so yeah it's certainly a lot less easy for them to decide that on behalf of the individual miners
Aaron van WirdumYeah, another argument would be that FPPS which I mentioned which most people use which is that the mining pool basically just pays you for a hash power yeah is essentially undervalued and one of the reasons for that is that miners will collect out-of-band payments. Wait, I don't know if it makes sense what I just said.
Sjors ProvoostWell, so the problem is more about transparency. So if we very briefly explain FPPS, it is... basically saying that you would get paid for the hash power that you're putting into it, which is then how much sats should you be paid for your hash power? And that calculation is based on the block reward plus the sort of the expected fees or the average fees over time or some whatever complicated algorithm. It's not that trivial to compare. So when a miner receives, when such a pool processes payments out of bound, like an accelerator, they may or may not
Sjors Provoostpay their miners for that. It's non-trivial to figure out if that's happening or not.
Aaron van WirdumRight.
Sjors ProvoostWhereas in this pool example, it's very clear when it's not happening.
Aaron van WirdumRight. In either case, I think we both sort of agree that if there was an Ocean 2 pool that just does everything exactly the same as Ocean and somehow they also have the same size and the same hash power, the same variance, the same luck. And Ocean does not include these transactions while Ocean 2 pool would, then Ocean 2 pool would at least be as profitable and usually more profitable.
Sjors ProvoostYes, and Ocean 2 pool could also have an out-of-band transaction accelerator and not pay the individual miners. However, it would be kind of obvious that their transactions being included at a implausibly low fee. And so as a miner, you would definitely notice that and you'd say, hey, I am definitely not getting sats for that. Because I can see exactly how many sats I am getting from these transactions. So, you know, somebody's getting the sats and it's not me, therefore, you know, maybe I'll switch to another pool or... Yeah.
Aaron van WirdumRight. Yeah, just to point this out, Jason and Mechanic also disagree with this, or at least they weren't necessarily agreeing. They seem to be disagreeing. They seem to... Their argument was that... There could be more complex things going on, like child pays for parents type of stuff that Ocean 2 pool would not see, and Ocean pool, like their pool, would actually include, and therefore they would still be more profitable.
Sjors ProvoostThe way you're describing that to me makes no sense, but that is because it's like a Chinese Whispers game, so.
Aaron van WirdumYeah, right. I'm just sort of trying to convey someone else's argument here, which I'm not very convinced by, but, you know, I am trying my best. In the case anyone is wondering the reason we don't have them on the podcast is because we just want to do our podcast in person not over calls or internet or Zoom or whatever else is available.
Sjors ProvoostExactly, which is also the reason why we didn't do a lot of episodes in the last couple of months Right, but we are back in this very cold country and I guess that's all.
Aaron van WirdumI think so.
Sjors ProvoostSure. All right, then thank you for listening to Bitcoin,
Aaron and Sjors discuss Bitcoin Core 32.1 and its updated security disclosure policy in this live conference recording, followed by audience questions. Links Bitcoin Core 32.1 release announcement and release notes...
Aaron and Sjors discuss the COLDCARD hack: the bug itself, how it could have happened, and some reflections on having had Coinkite as a sponsor. Note: If you’re using a COLDCARD and still haven’t moved your funds to a...
The COLDCARD hardware wallet has a critical vulnerability. If you are using the COLDCARD to store bitcoin, move them to a secure location as soon as you can. More information:...
Aaron and Sjors discuss what’s new in Bitcoin Core 31. Chapters 00:00:00 Episode 100 and Core 31 00:02:41 Cluster Mempool 00:10:45 Package Relay and Fee Selection 00:18:59 Private Broadcast over Tor 00:24:03 ASMAP and...