To be fair, I think he’s referring to the issue with Core 30. The mining pool centralization problem is already solved with Datum - it just needs much wider adoption. Core 30 is an entirely different issue. BIP-444 could be a potential solution, but it remains to be seen whether a USAF will gain enough traction and support to make it happen. If it does, I’ll be more bullish than ever.

Replies (1)

Could be, it is not very relevant what he is referring to, I just analyzed the message. Core 30 opens up major attack vectors as well. But to say "the mining pool centralization problem is already solved with Datum - it just needs much wider adoption", is like saying "the MoE problem is already solved with Bitcoin/Monero - you just have to get people to use them". Inside OCEAN, DATUM is now the default; network-wide it's still ~1% or less. OCEAN is only about ~1% of total Bitcoin hashrate (order of magnitude; varies over time). If ~65–94% of OCEAN’s hashrate is on DATUM, that implies ~0.6–0.9% of the network hashrate is mining with DATUM today. Stratum V2 is available at Braiins Pool and OCEAN/DEMAND’s pool, plus scattered tests elsewhere, but network adoption remains ~1% of hashrate or below. So mining pool centralization isn't a solved problem for now. Solvable problem, but not solved.