Key Takeaways


The episode argues that Bitcoin’s real centralization risk sits at the pool layer: six–seven pools direct ~90% of block construction, turning most “miners” into hashers who outsource trust, payouts, and block templates via Stratum v1. This creates a choke point for cartel behavior (e.g., fee manipulation, filtering Lightning), regulatory coercion (OFAC-style censorship), and smoother adoption of contentious changes, especially when relay-policy shifts can be de-facto standardized by a few pools. The hosts distinguish hashing vs. mining, relay policy vs. consensus rules, and hard vs. soft forks, warning that the danger isn’t one dramatic break but precedent and process, changes pushed with limited rough consensus because centralization lowers the friction. The counterweight is re-decentralizing block construction: more node-running miners, home/SMB setups, waste-heat use cases, and business models less dependent on fiat financing that prioritizes scale over alignment with Bitcoin’s incentives.

Best Quotes

Conclusion

Bitcoin’s durability depends on keeping changes hard and decision-making diffuse; concentrated pools invert that logic by making unilateral shifts easier and community signaling weaker. While today’s issues may seem incremental, the long-term risk is cumulative erosion of neutrality through small, precedent-setting moves. The remedy is agency: miners and users running nodes, diversifying pools/clients, experimenting with entrepreneurial energy reuse, and favoring incentives that reward profitability and independence over fiat-fueled growth. Decentralization isn’t aesthetic, it’s the mechanism that preserves Bitcoin’s security, censorship resistance, and social consensus.

Timestamps

0:00 - Brisket Inflation

2:30 - Mining Pools and Stratum V1 Explanation

5:49 - Trust Relationships and Hash Rate Distribution

7:49 - Mining's Security Function

11:21 - Pool Centralization Risks

13:38 - Cartel Scenarios and Hard Fork Dynamics

17:00 - Censorship vs. Invalidation Scenarios

20:50 - Government Pressure and Decentralization Benefits

24:30 - Consensus Rules: Hard Forks vs. Soft Forks

32:10 - Soft Fork Dynamics and Wipeout Risk

34:03 - Relay Policy vs. Consensus Rules

39:21 - Op Return Debate and Mining Pool Decision Making

46:05 - Developer vs. Miner Centralization Concerns

49:32 - Relay Policy Precedent Concerns

55:14 - Process Criticism and Community Feedback

59:33 - Mining Distribution Impact on Arguments

01:04:16 - Contentious Soft Fork Scenarios

01:11:25 - Game Theory and Economic Majorities

01:16:46 - Fiat Money's Impact on Mining Centralization

01:23:42 - Path to Decentralization

01:25:33 - Innovation and Home Mining Future

Transcript

(00:05) Jimmy, thanks for doing this. Topic of the day is mining centralization. But before we get there, I want to quiz you. Just went down the street to Coopers. Got brisket. I want you to guess what the current price of brisket per pound is at Coopers. It's downtown prime location, Austin, which obviously Oh, yeah.

(00:36) Obviously, um, very popular around here. I'm going to guess 32.99. 3950. What? Yeah. Do Do you have any recollection? We've been going to Coopers for a long time around bit devs. Do you have any recollection of the earliest price you would have remembered at Coopers? Well, Cooper didn't open until like 5 years ago. No, it it it's been at least 2018.

(01:00) Okay. So, 7 years ago, something like that. Yeah. But, um I want to say like 22 299 was maybe like the earliest I can remember. The lowest I saw when I I started going there more frequently when I started Unchained, which would have been 2018, 1799. Yeah. I remember when I first moved to Austin, I went to uh Rudy's.

(01:30) I think it was like 629 or something. Yeah, this was 2012. It's just amazing. I I've triggered a number of people carrying the torch on SAFE's ribeye as an inflation index and I'm conditioned to the increase in prices and even at Coopers, I think I went and I saw it at 33 or $34. But there was something about that 3950. Yeah.

(01:57) And I know that I've seen it, you know, back in time at the same location. 17.99 more than 100%. Yeah. Just Well, you know, in Bitcoin terms, that's actually quite cheap now. like compared to that. I saw a tweet that you put out about something that you were looking to purchase, seeing that it was some amount more expensive and then realized that it was cheaper in Bitcoin terms.

(02:23) And it is it is true that that brisket is still cheaper in Bitcoin terms. Way cheaper. The dollar inflation still still hits. It does. Still hits. It does. Um, start paying attention, freaks. But um all right, on to the real topic of the day, mining centralization and and specifically we're going to get into pool mining pool centralization.

(02:48) Explain in your words the relationship between Bitcoin miners and mining pools just to set some context. Right. So the reason why pools exist in the first place is because you want variance reduction, right? Um if you have a tiny amount of hash rate um you have uh you know whatever hash rate you have divided by the global hash rate percentage chance of finding the next block.

(03:15) It's obviously not going to be very much. And instead of uh you know waiting for the one jackpot hit if you will, you can pull all of your resources and split it equally. That's what a mining pool is supposed to be. Um unfortunately the first design of mining pool stuff uh uses something called stratum v1 and this is where the mining pool tells everybody hey here's the block you have to mine including this output address that goes to the pool and will do the splitting up afterwards. Um and that means that the pool

(03:55) essentially acts as the block template constructor. And in fact for any member of the pool they don't have to run a node at all. They just have to take the template modify it in whatever way to uh roll the nons or whatever and just hash until they find the block right or find really what they do is they find shares and then submit those shares and if the uh pool if they find a block then it gets spread equally.

(04:28) That's the idea behind pools and that's how um it's more or less executed. Uh but you know, one of the things that makes it kind of bad is that the pool operator gets to decide what goes into each block. And that means that there's a centralized block production industrial complex, if you will. There's only maybe 15 pools that have something like 95% of the hash rate and uh that that are running stratum v1. Um I think brain brains pool they run stratum v2.

(05:05) Um, Ocean obviously runs DATM and then there's like CK solo pool and they they make it so that you can uh mine solo and decide on your um template yourself. Uh, and but they they take up I believe less than 5%. So 95% of hash rate essentially is controlled by like 16 pool operators. And we know that some of them have like economic, you know, interests in the other.

(05:38) So, it's probably more like 10 at the most, right? Like entities. Yeah. And so, you mentioned that like most Bitcoin miners, if they're working with a centralized pool, are not running their own node. They don't have to. No. Um, and that when they are performing work, say on-site where they're consuming power and running the Bitcoin hashing algorithm, they're basically their their primary communication channel is back through the pool.

(06:10) They they send the pool all of their work and then not only does their work go back through the pool and the pool does the accounting of how much work all the miners participating in their pool do but then the money goes directly to the pool. Mhm. And then they have to get paid out. Yeah. And the pools pay out the miners. Right.

(06:36) It's it's a big trust relationship honestly because every hasher, right? Like we shouldn't call these people that are participating in a pool not really running their own nodes or constructing blocks like any an actual minor. They're not really mining as much as they are hashing. The mining pools are mining because they're constructing their own blocks.

(06:55) Um but that's they they have to have um this big trust relationship because the pool does the payout, right? Um, and you know,