OCEAN Reactivates Lightning After Damage from Dashjr's Bet on BIP-110

• The incompatibility arose from the fork initiated by Luke Dashjr in August.
• OCEAN has reactivated Lightning payments after a month-long pause due to BIP-110.

The mining pool OCEAN announced on September 4 that Lightning payments are back to normal after a month of suspension caused by the technical incompatibility left by the BIP-110 fork in early August.

The company took the opportunity to announce that it will also reduce its on-chain payment threshold from approximately one million to 500,000 satoshis, with the arrival of an upcoming update to its TIDES system.

A month-long pause in a payment channel is not a minor operational detail for a pool that bases a significant part of its value proposition on fast and non-custodial payments. The breakdown came from a bet outside the business: BIP-110 was the proposal that OCEAN decided to support alone, and its failure directly affected the service to miners already using Lightning.

The timeline matters. OCEAN was the only pool that provided technical support for BIP-110, an initiative driven by Luke Dashjr to restrict non-monetary data in Bitcoin transactions. When that minority chain lagged behind the main network after concentrating only a fraction of the hashrate, the pool's payment infrastructure was trapped in that incompatibility for weeks.

This technical wear did not happen in a vacuum. Three weeks after the failed fork, Dashjr left the company he helped found, citing differences over the direction of Bitcoin mining. His departure coincides with the cost left by his bet: a service paused for a month right in the channel that small miners, whom OCEAN claims to prioritize, value the most.

A mining pool lives on the operational trust of those who point their hashrate at it. When that trust is jeopardized by a governance stance that did not gain the network's support, the service pays the price, not the idea.

BIP-110 was never a proposal with broad consensus among miners. Only OCEAN wanted to sustain it in practice, while the rest of the ecosystem chose to ignore it and continue with the existing rules. This isolation explains why the alternative chain barely advanced a handful of blocks before stagnating.

Sustaining a technical minority has a price, and that price is not always paid in abstract reputation. In this case, it was paid in a concrete product: miners configured for Lightning had to wait a month for their rewards to be processed through normal channels or, alternatively, reach the threshold for an on-chain payment.

The decision to reduce the on-chain threshold to 500,000 sats is, at its core, a response to small miners who felt the problem firsthand. It is a reasonable correction, but also a signal that the pause affected precisely the segment that Lightning was supposed to serve better: those mining with less capacity and relying on frequent and accessible payments.

Nothing in OCEAN's statement directly attributes the pause to Dashjr or his departure. But the sequence speaks for itself: support for a minority proposal, failed fork, month-long technical breakdown, and the departure of the co-founder who pushed that bet, all in less than thirty days.

The lesson for any pool that decides to play in the realm of Bitcoin consensus is simple. The network does not forgive solitary bets, and when the payment infrastructure depends on staying aligned with the chain that effectively wins the hashrate, straying from that majority comes at a cost that sooner or later reaches the users.

This content is provided for general informational purposes only and doesn't constitute financial, investment, legal, or tax advice. Any events, rewards, online promotions, or related information mentioned herein should not be considered a recommendation, solicitation, or invitation to purchase, sell, trade, or otherwise deal in any crypto assets. Crypto assets are highly volatile and may result in loss. The availability of WEEX services, products, and related events may vary by region. You are responsible for ensuring that your participation is in accordance with applicable local laws and regulations.