OCEAN Pool suffers a “bug” and payments to bitcoin miners are delayed.
According to the X account of OCEAN Pool, an emerging mining platform that uses decentralized templates, the connection to the pool of a high-capacity miner caused a bug in the protocol, which is delaying payments to workers. This happened on October 28, 2025.
Overnight, a large miner entered OCEAN, causing a mistake and its associated security mechanisms. No work was lost, although statistics were affected and payments could be temporarily delayed pending a full analysis today.
Communiqué by OCEAN Pool, Bitcoin mining platform.
OCEAN clarifies that while the security mechanisms activated by the bug worked, the pool found a block of Bitcoin. At the time of the newsroom, they have found four of them. It also ensures that this is not causing loss of work or resources for platform participants, and that the rewards in BTC are secure, despite delays.
From the account of Public Pool, a direct competitor of OCEAN in Bitcoin’s collaborative mining, they questioned the decentralization of the platform created by Luke Dashjr, an attribute that its creators consider their hallmark.
Payments could be temporarily delayed? They said they were decentralized? How can a payment be delayed if the nodes build their own templates? This seems to be against all his publicity.
Public Pool, Bitcoin mining platform.
In a comprehensively decentralized pool, the settlement of payments to miners should occur automatically, without an intermediary who coordinates or deploys block rewards.
According to OCEAN’s documentation, this pool uses Lightning and BOLT12 to pay the miners. This mechanism pairs miners with BOLT12 offers, which theoretically automates payments and allows them to run without the pool as an intermediary.
However, the pool would still retain a significant degree of centralization by having to calculate the distribution of rewards to workers according to the work provided. The bug and security mechanisms activated by the event would have affected the statistics that allow such a calculation of reward distribution, which is why pool payments may be delayed.
At the time of writing, the OCEAN Pool data in real time shows the following notice:
I am currently working on fixing statistics to properly consider yesterday’s failure. During this time, the statistics will be delayed. The pool is in operation and no accepted job is lost. Thank you for your patience. -DevOps OCEAN
OCEAN, Bitcoin mining pool.
Before the large miner’s connection to the mining pool, the hashrate of OCEAN was around 12.5 EH/s (exahashes per second). On the 29th of the same month, this computing power reached a peak of up to 16.3 H/s. This is not the first time this pool has suffered a sudden rise in hash rate.
About The Author
