Ontology halts mainnet transactions as technical team investigates potential security issue

Ontology suspended mainnet block production to investigate a potential security concern, pausing the network while its technical team and validators reviewed the issue.

A public-node snapshot showed a gap of about five hours and six minutes since the chain’s last recorded block.

The project announced the pause at 09:09 UTC on Aug. 31. Ontology called it a preventive measure and said it had not confirmed a security incident or found any indication that user assets had been lost or compromised. Based on the project’s assessment at the time, its ONT and ONG crypto assets, along with other on-chain assets, remained unaffected.

Public node remained at block 20,770,893

Ontology’s first-party notice said it identified the potential concern during a daily security check. The notice did not specify the technical condition under review, which systems might be involved, or what findings would allow production to resume.

The project said the suspension’s duration was undetermined and that it would issue a separate announcement before or when the network resumed. It also said it would not process on-chain transactions while block production remained suspended. Ontology did not disclose a public restart timetable in the notice.

Those statements keep the episode distinct from a confirmed exploit or attack. The network interruption is clear, but the project’s asset-safety statement was a preliminary assessment made while the review was still underway. Ontology did not report a loss, compromise, or active attack in either of its initial updates.

Ontology’s developer documentation lists dappnode1.ont.io as a public MainNet node. A height request captured at 13:30:49 UTC returned block 20,770,893.

The record for that block carries a timestamp of 08:24:26 UTC on Aug. 31. The difference between the block timestamp and the later snapshot was five hours, six minutes, and 23 seconds.

That calculation measures time since the last block visible through the documented node. The node data does not explain why production stopped, but its unchanged height aligns with Ontology’s statement that the mainnet had been suspended.

The next material update is whether validators resume block production and what Ontology’s review finds. A restart would establish the final duration, while a later technical explanation could show whether the precautionary halt prevented an incident or addressed a concern that did not develop into one.