Ontology restored mainnet operations on September 2 following an emergency security pause that began on August 31. The network has made version 3.1.5 mandatory for all sync-node operators to ensure compatibility with the restored chain and stable synchronization.
The network initially described the trigger as a potential security concern discovered during a daily security check. A September 1 update escalated that description, with Ontology identifying malicious attack activity targeting the network while remediation and testing were underway.
During the pause, Ontology instructed users to avoid time-sensitive on-chain transactions but stated that users did not need to move ONT, ONG, or other assets. The network's assessment indicates that the activity did not involve or compromise user assets.
Version 3.1.5 disables registrations for several legacy native contracts and modifies cross-chain message deserialization, though Ontology has not publicly disclosed the specific attack path or vulnerability exploited. The upgrade is required to maintain compatibility and prevent synchronization issues for node operators running older software.
Ontology's restoration announcement confirms the mainnet's return to operation but does not establish whether all ecosystem services have resumed normal operation across public RPC providers, exchange deposits and withdrawals, wallets, and decentralized applications. The network has not published an independent forensic report or postmortem analysis of the incident.
The company stated that monitoring will continue with technical and security partners as remediation efforts proceed.
