Have you ever watched someone walk away from free money and wondered what the hell they were thinking? That is exactly the feeling that hit me when I first saw the numbers on block 973,817. A single miner operating through the Ocean pool decided to leave a measurable slice of transaction fees sitting on the table, and the internet did what the internet always does: it lit up with accusations of censorship.
The Quiet Decision That Sparked a Loud Argument
It started with a consolidation transaction that never made it into the block. The developer who submitted it, known online as Kruw, noticed the omission almost immediately. He posted a side-by-side comparison that made the shortfall impossible to ignore. The expected template held 3,580 transactions. The actual block that got mined contained only 1,698. Block weight dropped from roughly 3.99 million weight units to 2.93 million. Transaction fees came in at 0.016 BTC instead of the 0.017 BTC that looked available. That works out to a 7.68 percent gap.
Now, 7.68 percent of the fee portion is not the end of the world when you look at the entire block reward. But in a pool environment where every satoshi eventually gets split among participants, that gap starts to feel personal. Kruw called the block “partially emptied” and asked Ocean’s public face, Coinjoined Chris, to step in and stop what he labeled censorship.
I have followed mining debates for years, and this one feels different. It is not about a government blacklist or a coordinated attack on certain address types. It is about one miner’s choice, the pool’s refusal to override that choice, and the uncomfortable question of whether collective fee income should ever trump individual autonomy.
What Actually Happened Inside Block 973,817
The excluded transaction carried a fee of 223 satoshis and a rate of about 0.15 satoshis per virtual byte. It had been sitting in the mempool for only four minutes when the block was found. On paper it looked like a routine consolidation move. In practice it became the flashpoint.
Ocean runs a system called DATUM that lets individual miners build their own block templates. That is the key technical detail most people miss when they jump straight to the censorship label. Under DATUM, the pool does not force a single shared template on every participant. Miners can pull transactions according to their own criteria. Some chase pure fee density. Others apply filters based on privacy tools, personal philosophy, or simple connectivity quirks.
Chris responded by acknowledging the economic cost while defending the design. He supports CoinJoin transactions and wants more of them included. He also believes financial privacy sits at the core of what Bitcoin is supposed to protect. Yet he drew a hard line: the pool should not punish a miner for the template that miner chooses to mine.
TIDES rewards contributed pow according to our payout rules, not whether OCEAN approves of a miner’s tx selection.
That sentence is doing a lot of work. TIDES is Ocean’s payout mechanism. It pays out based on the work contributed, not on how closely a miner’s template matches some ideal fee maximum. Chris essentially told the community that the pool’s job is to distribute rewards fairly for hash power delivered, not to act as a fee-maximizing police force.
Why the Fee Gap Feels Larger Than the Numbers Suggest
On a pure math level the shortfall is modest. The block still collected the majority of available fees. But pools operate on thin margins once you factor in electricity, hardware depreciation, and the constant pressure of difficulty adjustments. When one participant consistently leaves money behind, the rest of the pool starts to notice.
Kruw’s counter-argument was straightforward. If a miner’s template systematically underperforms, the pool could simply reject the share with a message like “Rejected share, check mempool connectivity.” That would create a soft pressure toward higher fee collection without writing a formal blacklist of specific transaction types.
Chris pushed back hard on that idea. He pointed out that no two nodes see the exact same mempool at the exact same moment. Propagation delays, different relay policies, and private transactions that never hit public relay networks all create legitimate differences. Declaring a 7.68 percent shortfall as automatic evidence of bad behavior opens the door to endless second-guessing.
Who decides the acceptable threshold? Ninety-nine percent of the theoretical maximum? Ninety-five? And what happens when a miner includes a high-fee private transaction that the pool’s monitoring nodes never saw? Suddenly the “underperforming” template looks like the better one.
I keep coming back to that point. In my experience watching these systems, the moment you introduce a central profitability check you start sliding toward the very centralization that many people joined Ocean to avoid.
Miner Freedom Versus Collective Income
This is the real tension. Bitcoin mining has always contained a quiet contradiction. The protocol itself is deliberately neutral about which valid transactions get included. Any miner can choose any set of valid transactions and still produce a valid block. At the same time, economic reality pushes most hash power toward fee maximization because electricity is not free.
Ocean’s DATUM design leans hard into the first principle. It gives miners the technical ability to express preferences. Some of those preferences will cost money. That is the price of actual choice.
Kruw sees the same design and reaches the opposite conclusion. In his view the only legitimate reason for a miner to build a custom template is to capture additional profit that a centralized template might have missed. Anything else is just leaving value on the table for the rest of the pool.
Both positions contain truth. The uncomfortable part is that they cannot both be fully satisfied at the same time.
The Privacy Angle That Refuses to Stay Quiet
Although the specific transaction that got dropped was described as a consolidation, the broader conversation kept circling back to CoinJoin and financial privacy. Chris has been vocal for a long time about wanting more privacy-preserving transactions in blocks. He has said publicly that he considers privacy fundamental.
That stance creates an interesting pressure. Privacy tools sometimes produce transactions that look less attractive on a pure fee-per-byte basis, especially in the short window before a block is found. A miner who prioritizes pure fee density might skip them. A miner who prioritizes the long-term health of the privacy ecosystem might include them even at a small cost.
When the cost lands on the rest of the pool, the conversation gets heated fast. People who never touch CoinJoin start asking why their payouts should subsidize someone else’s philosophy. People who care deeply about privacy start asking why a pool that markets itself around freedom is suddenly treating fee maximization as the only acceptable philosophy.
There is no clean answer. I have watched similar arguments play out in other corners of the ecosystem, and they almost always end with both sides feeling that the other is missing the point.
How DATUM Changes the Usual Pool Dynamics
Most traditional mining pools present a single template to every participant. The pool operator decides which transactions go in, the miners simply provide hash power, and the fees get split according to contributed work. That model is simple and efficient. It is also highly centralized at the template level.
DATUM flips the model. Miners receive the ability to construct their own templates while still participating in the pool’s payout system. The technical freedom is real. The economic consequences are also real. When one miner’s template underperforms, the difference is socialized across everyone who receives TIDES rewards from that block.
This creates a new kind of social contract. Participants are no longer just renting out hash power to a black-box template. They are joining a system that explicitly allows divergence. Whether that divergence is a feature or a bug depends on who you ask on any given day.
Chris has been consistent on this point. He wants the freedom to remain, even when he personally disagrees with a particular miner’s choices. That consistency is rare enough in this space that it is worth noticing.
Could Soft Rejection Rules Solve the Problem?
Kruw’s suggestion of rejecting underperforming shares is the kind of practical compromise that sounds reasonable until you try to implement it. The moment you set a threshold, you need monitoring infrastructure that can reliably judge every template against a theoretical maximum. That infrastructure has to account for private transactions, differing mempool views, and the simple fact that fee rates move continuously.
Any threshold will be arbitrary. Set it too high and you start rejecting legitimate work during periods of rapid mempool change. Set it too low and the rule becomes meaningless. Either way you have introduced a new layer of central judgment that DATUM was designed to avoid.
I am not convinced there is a clean technical solution that preserves both full miner autonomy and guaranteed fee maximization. The two goals pull in opposite directions.
What This Means for the Broader Mining Landscape
Ocean is not the largest pool. Its decisions do not dictate the behavior of the entire network. But it has positioned itself as a place that values miner agency more than most. When a dispute like this surfaces, it becomes a live stress test of that positioning.
Other pools that run more centralized template systems avoid this particular argument. They simply maximize fees by default and leave the philosophical questions to someone else. That approach is quieter. It is also less interesting if you care about the long-term question of who actually controls the composition of Bitcoin blocks.
The more hash power that sits behind systems like DATUM, the more visible these trade-offs become. We may see more of these public disagreements. Some will be about privacy tools. Others will be about ordinals, inscriptions, or whatever the next contested use of block space turns out to be. The underlying tension will remain the same: individual selection versus collective economic interest.
A Closer Look at the Numbers That Started Everything
Let us walk through the comparison again without the heat. Expected transactions: 3,580. Actual: 1,698. Expected weight units: approximately 3.99 million. Actual: 2.93 million. Expected fees: 0.017 BTC. Actual: 0.016 BTC. Difference: 7.68 percent of the fee component.
That is a clear shortfall. It is also still a valid block under the consensus rules. The miner who produced it did nothing that violates the protocol. The question is only whether the pool’s social and economic rules should impose additional constraints.
Chris’s position is that they should not. Kruw’s position is that they must, at least when the shortfall is this visible. The rest of us get to decide which framing feels more sustainable over time.
The Human Element Behind the Technical Debate
It is easy to treat this as a pure systems discussion. In reality there are people on both sides who care deeply about the outcome. Miners who rely on pool income to keep machines running do not enjoy seeing potential revenue left uncollected. Developers who spend time building privacy tools do not enjoy watching those tools get filtered out of blocks for economic reasons.
Chris sits in the middle of that tension every day. He has stated support for the privacy side while refusing to weaponize the payout system against the economic side. That is a difficult line to walk, and it is not surprising that the line is being tested in public.
I find myself more sympathetic to the autonomy argument than I expected. Once you start rejecting shares because the template did not meet an external profitability standard, you have recreated the centralized control that many people were trying to escape. The cost of that escape is occasional inefficiency. Whether that cost is worth paying is a judgment call each participant has to make.
Possible Paths Forward Without Breaking the Model
There are softer options than hard rejection. Transparent reporting of template performance over time could let participants decide for themselves whether to continue sharing hash power with underperforming miners. Reputation systems that remain optional rather than enforced by the pool itself could create social pressure without formal rules.
Some miners might simply choose to switch pools if they believe the fee leakage is too high. That market response is already available and does not require Ocean to change its core design.
The pool could also improve its own monitoring and education so that miners understand the economic impact of their selection policies more clearly. Better information often reduces the need for formal enforcement.
None of these approaches will satisfy everyone. They do, however, keep the door open to continued experimentation with miner-controlled templates.
Why This Dispute Matters Beyond One Block
Bitcoin’s value proposition has always included the idea that no single party can dictate which transactions are allowed. That idea lives primarily at the consensus layer. Mining pools sit one level above consensus and can still exert significant influence through template selection and payout rules.
When a pool deliberately chooses not to exercise that influence, it is making a statement. The current dispute is testing how durable that statement remains when real money is left on the table.
If Ocean holds its position, it reinforces the idea that miner freedom includes the freedom to be economically suboptimal. If pressure eventually forces a change, it will demonstrate that collective fee income is a stronger force than the design principles that were advertised.
Either outcome will teach the rest of the mining ecosystem something useful about the practical limits of decentralization at the pool layer.
The Longer View on Transaction Selection Power
Over the next few years we are likely to see more sophisticated tools for template construction. Some will optimize purely for fees. Others will incorporate scoring systems that weight privacy, specific use cases, or even social signals. The existence of those tools will make the current argument look almost quaint.
What will not change is the fundamental trade-off. Every time a miner exercises selection power in a way that reduces fees, someone else in the pool absorbs the cost. Every time a pool removes that selection power, it concentrates control. There is no free lunch here.
The Ocean situation simply made the trade-off visible in public numbers that anyone can check. That visibility is valuable even when the conversation gets uncomfortable.
Personal Reflections After Watching the Exchange
I have spent enough time around mining operations to know that pure ideology rarely survives contact with electricity bills. At the same time, I have seen enough centralized systems drift into quiet forms of filtering that I remain wary of any proposal that reintroduces top-down template control.
Perhaps the most interesting aspect of this whole episode is how quickly a technical design choice became a values debate. DATUM was built to give miners agency. That agency produced a result that some participants disliked. The disagreement that followed is not a bug in the system. It is evidence that the system is actually doing what it claimed.
Whether the community decides that result is acceptable will shape how similar systems are received in the future. I am watching closely, and I suspect I am not the only one.
In the end the block was still valid. The fees that were collected still got paid out according to the rules. The transaction that was left out will almost certainly find its way into a later block. Life on the Bitcoin network continues. What changed is the public conversation about how much freedom individual miners should actually have when that freedom has a price tag attached.
That conversation is far from over. And that, more than the specific 7.68 percent gap, is what makes this particular dispute worth paying attention to.
Looking Ahead Without Easy Answers
Future blocks will continue to be built by a mix of highly optimized templates and more idiosyncratic ones. Some pools will keep tight control. Others will experiment with greater miner freedom. The market will sort out which approach attracts more lasting hash power.
In the meantime, participants in systems like Ocean’s will keep navigating the same tension that surfaced around block 973,817. Every time a miner chooses a lower-fee template for reasons that go beyond pure economics, the rest of the pool will feel it. Every time the pool refuses to override that choice, it reaffirms a particular vision of what mining participation is supposed to mean.
There is no perfect resolution. There is only the ongoing process of deciding which trade-offs we are willing to live with. The numbers from that one block simply made the trade-offs harder to ignore.
And sometimes that is the most useful thing a single block can do.
