Ontology halts mainnet block production over potential security concern

Ontology has temporarily halted mainnet block production after its core developers identified a potential security concern during a routine check, leaving on-chain transactions suspended while validators conduct an emergency review.

• Ontology has temporarily halted mainnet block production after its core developers identified a potential security concern during a routine security check.
• No confirmed security incident or user asset loss has been identified, with ONT, ONG and other on-chain assets currently considered unaffected.
• On-chain transactions will remain unavailable during the security review, and users have been advised to avoid time-sensitive transactions.
• Ontology has not set a restart time and said block production will resume only after the network has been assessed and deemed safe.

The Ontology Network said in an official announcement that its core development team detected the potential issue during a daily security check and immediately moved to stop block production as a precaution. No security incident has been confirmed, and the team said it has found no evidence that ONT, ONG or other user assets have been lost or compromised.

Ontology mainnet remains paused during security review

With block production stopped, transactions submitted to the Ontology mainnet cannot be processed until network operations resume. The team has not provided an estimated time for the restart and said the review will take priority over restoring the chain quickly.

Ontology described the halt as a preventive measure, distinguishing it from a response to an active attack or confirmed theft. Developers and network validators are reviewing the mainnet and related components to determine whether the potential concern presents an actual security risk.

Users have been told not to move ONT, ONG or other assets because of the announcement. However, the network advised against attempting time-sensitive on-chain transactions while the pause remains in place.

The team has not disclosed the technical nature of the potential security concern, which component triggered the review or whether developers have identified a vulnerability requiring a software change.

Ontology said it is working with validators and relevant ecosystem partners during the investigation. A separate announcement will be released before or when block production resumes, after the security assessment and any required upgrades have been completed.

No user asset losses have been identified

The network emphasized that the current investigation has not produced evidence of compromised user funds.

"There is currently no indication of any loss or compromise of user assets," the team said. "ONT, ONG, and other on-chain assets remain unaffected based on our current assessment."

The distinction leaves the mainnet in an unusual operational state: the chain is intentionally unable to process transactions, but Ontology has not reported an exploit, unauthorized asset movement or an ongoing attack.

Ontology did not say whether exchanges or other services using the chain would separately restrict ONT or ONG deposits and withdrawals during the review.

Ontology has not set a restart time

For now, the mainnet will remain unable to produce blocks while developers and validators work through the security review.

Ontology said the duration of the shutdown is undetermined and that it will prioritize a complete examination of the potential risk over speed. Normal block production will resume only after the network has been assessed and the team considers it safe to operate.

Any upgrades found necessary during the investigation would have to be completed before the restart, according to the announcement. The team did not specify whether an upgrade is currently expected or whether the review could end without requiring changes to the network software.

Ontology said updates on the investigation will be published through its official channels as more information becomes available. The network plans to issue a separate notice before or at the time operations resume once the security review and any required upgrades have been completed.