0x26fa2fd326fa…26fa2fd6

ConfirmedSecurity667 vB173 sat/vB3 min decode

Ocean Mining Denies Complicity in Luxor Pool Hack, Defends Payout Rules

Ocean Mining denies facilitating payments to Luxor pool hackers, defending its TIDES payout system after Luke Dashjr alleged the pool routed over $37,000 to attackers and collected fees.

Ocean Mining Rejects Complicity Claims Over Luxor Bitcoin Pool Hack
WitnessOcean Mining Rejects Complicity Claims Over Luxor Bitcoin Pool HackAkela999 / pixabay

Outputs

  1. Ocean denies involvement in the Luxor pool hack and says its systems were never compromised.

  2. Luke Dashjr alleged Ocean directed 0.16202083 BTC (~$10,510) to attackers and planned further payouts of 0.33029017 BTC (~$21,400).

  3. Dashjr claimed Ocean collected ~0.01 BTC (~$650) in fees from compromised mining activity.

  4. Ocean's TIDES payout system distributes rewards for valid work but does not verify machine ownership.

  5. Ocean pledged cooperation with Luxor, law enforcement and affected customers.

Mining pool Ocean has rejected accusations that it facilitated payments to attackers who hijacked Luxor customers' mining equipment, stating that its systems operated normally and that it had no involvement in the incident. The company issued the denial after Bitcoin developer and former Ocean chairman Luke Dashjr alleged the pool knowingly routed funds to the attackers and collected fees on the compromised mining activity.

"Ocean was not compromised. Our systems operated normally. We had no involvement in the incident," the company said in its statement.

Ocean did not name Dashjr directly or address the specific figures he cited. Instead, the response centered on the principles governing its payout architecture, arguing that blocking or redirecting rewards for valid mining work would undermine Bitcoin's permissionless design. "Bitcoin is either permissionless or it is not. There is no middle ground," Ocean declared.

What did Dashjr allege?

Dashjr accused Ocean of financially benefiting from the hijacking of Luxor customers' mining operations. He claimed the pool instructed participating miners to direct 0.16202083 BTC — approximately $10,510 at the time — to the attackers in two instances after the incident became public.

He further alleged that Ocean continued allocating rewards equivalent to 0.08123485 BTC, roughly $5,270, to the attackers, and that its website indicated plans for another 0.33029017 BTC, worth about $21,400, in subsequent distributions.

Dashjr also said Ocean had already collected 0.00330655 BTC in fees, approximately $210, tied to the compromised activity, and stood to receive another 0.0066058034 BTC, about $440. Combined, the fees would total nearly 0.01 BTC, or approximately $650 at the prices he cited.

"Yes, that's right: Ocean is profiting from a cyberattack on their own customers, and rewarding the attackers," Dashjr wrote.

How does Ocean's payout system work?

At the core of Ocean's defense sits its TIDES payout system. According to the company, TIDES automatically accounts for valid proof of work and distributes mining rewards directly to participants without requiring them to surrender custody of their funds.

The system verifies the validity of submitted mining work but does not determine whether the submitting party owns the mining hardware or was authorized to configure it. "We verify the work submitted, but not who owns the machines or whether someone was authorized to configure them," Ocean explained.

Once valid work has been submitted, the corresponding credit cannot be reassigned under the pool's payout rules. Ocean acknowledged the mining activity may have originated from equipment redirected without its owners' consent, but said its system processes valid work according to predetermined rules rather than discretionary judgments about who should receive rewards.

The company argued that allowing a pool to selectively block or redirect payouts would introduce centralized control over miners' earnings. A pool capable of arbitrarily deciding whose valid work counts, who receives payment, or when established rules apply would require miners to trust the operator with powers Bitcoin was designed to eliminate, Ocean said.

"Permissionless mining isn't a loophole. It's a principle," the company stated.

What operational risks does the incident expose?

Beyond defending its payout mechanism, Ocean used the episode to highlight what it described as the dangers of centralized mining infrastructure. The unauthorized redirection of Luxor's hashrate shows the vulnerabilities miners face when they delegate operational control of their equipment to third-party software providers.

"This incident underscores a fundamental risk of centralized mining: When you entrust control to a third party, you also inherit the risks of that third party's systems," Ocean said.

The company expressed sympathy for affected miners and pledged to cooperate with Luxor, law enforcement and customers investigating the attack. It urged miners to secure access to their equipment, update security measures and monitor their mining configurations for unauthorized changes.

The dispute now turns on whether Ocean acts on its pledge to assist investigators, and whether law enforcement or Luxor can trace the attacker-controlled payout addresses flagged by Dashjr before the roughly $21,400 in planned distributions clears.

via cryptonews.net (Source)

More from Tom Whitfield

Tom Whitfield

Show full bio

News editor covering technology and product news in crypto and web3 industry at Mempool Brief.

1,374 articles