Luke Dashjr Exits OCEAN: Bitcoin Mining's Quiet Power Struggle

On August 29, 2026, one of Bitcoin's longest-tenured developers walked away from the mining pool he co-founded. Luke Dashjr — a Bitcoin Core contributor since 2011 — resigned as chairman, chief technology officer, and director of OCEAN, and parent company Mummolin bought back his entire equity stake. The joint statement called the separation mutual and blamed “differing views on the future of bitcoin mining.” That is the polite version. The real story runs through a failed soft fork, a spam-filter war, and a question Bitcoin has never fully answered: who actually decides what goes into a block?

A 16-Year Veteran Walks

Dashjr is not a minor figure. He has been committing code to Bitcoin since 2011, maintains the Bitcoin Knots node software, and co-founded OCEAN in November 2023 with backing that included Jack Dorsey. OCEAN's whole pitch was decentralization: a transparent, non-custodial pool that pays block rewards directly to miners instead of holding their coins, built as an answer to the handful of giant pools that dominate block production.

Now he holds none of it. The buyback price was not disclosed, and OCEAN says it will keep operating the pool as before. Dashjr, for his part, is launching a new venture called CONVOY, which he says will continue the mission of decentralizing Bitcoin mining.

The Fight Behind the Split

The separation statement cited “recent protocol developments” without naming them, but the timeline speaks plainly enough. Dashjr spent 2026 championing BIP-110, a controversial proposal to temporarily restrict the storage of non-financial data — inscriptions and other arbitrary payloads — on Bitcoin. It failed. An attempt to enforce it as a separate chain stalled when miners quietly declined to follow, and in mid-August Dashjr was removed as a Bitcoin Improvement Proposal editor. He took a sabbatical from OCEAN. Two weeks later, he was out entirely.

OCEAN itself hedged through the whole episode. In July it offered miners dedicated BIP-110 and non-signaling endpoints, letting each operation pick a side. On August 9 it moved its default endpoint back to the main chain while keeping both options live. Read between the lines: the pool's customers did not want the fork, and the pool followed its customers rather than its co-founder.

Underneath the drama sits a real philosophical divide. One camp holds that Bitcoin is money and miners should filter out data that is not payments. The other holds that Bitcoin is a neutral settlement layer, and any transaction that pays the fee gets in. Dashjr has been the loudest voice in the first camp for years. The market, so far, keeps siding with the second.

Why This Matters More Than One Résumé

Bitcoin mining is concentrated. Foundry USA, AntPool, and F2Pool together produce well over half of recent blocks, according to mempool.space. OCEAN is small by comparison — roughly 2.5 to 2.9 percent of blocks in late August, around 25 exahashes per second — but it punched above its weight on one specific issue: its DATUM system lets individual miners construct their own block templates instead of accepting whatever the pool builds.

That is the actual decentralization frontier in 2026. The hardware is scattered across the globe, but the decision about which transactions make it into blocks is concentrated in a few template-building servers. If a government leaned on three pool operators, it could pressure most of the network's transaction selection. Tools that push template construction out to individual miners — DATUM, Stratum V2 — are the countermeasure, and losing or gaining champions for them matters far more than any executive shuffle.

CONVOY: A Name, Not Yet a Pool

As of publication, CONVOY is an announcement and an X account. No endpoint, no codebase, no fee schedule, no template policy, no disclosed miners or infrastructure, no launch date. That is not a criticism — it is just where things stand. The measurable test comes later: either blocks start appearing with a CONVOY coinbase tag and hashrate follows Dashjr, or they don't. Bitcoin has a way of settling arguments with data.

What You Can Actually Do

You do not need to pick a side in the filter wars to act on this story. If you hold bitcoin, note that nothing about this episode touched your coins — the consensus rules did not change, and a contentious fork died because nodes and miners declined to follow it. That is the system working. If you want to watch the power dynamics yourself, check the mining dashboard on mempool.space once in a while; pool shares are public, and you can see concentration (or CONVOY's arrival) with your own eyes. If you mine — even a lottery-ticket Bitaxe on your desk — ask whether your pool lets you build your own block templates. And if you run a node, remember that relay policy is a choice: Bitcoin Core and Bitcoin Knots ship different defaults, and your node enforces whichever rules you choose to run. That is the entire point.

The block size wars settled who controls Bitcoin's rules: the people running nodes, not the companies with the biggest machines. This decade's version of that fight is over block templates, and it is being fought by people who show up, write code, and sometimes lose. If you follow this stuff closely enough to have an opinion on BIP-110, you are already deep in the culture — BitCloset makes heavyweight apparel for people who chose Bitcoin.

Further Reading

Back to blog

Leave a comment