Ontology halts mainnet transactions as technical team investigates potential security issue
Ontology suspended mainnet block manufacturing to analyze a potential security concern, pausing the community whereas its technical team and validators reviewed the issue.
A public-node snapshot confirmed a niche of about 5 hours and 6 minutes for the reason that chain’s final recorded block.
The undertaking announced the pause at 09:09 UTC on Aug. 31. Ontology known as it a safety measure and stated it had not confirmed a security incident or discovered any indication that consumer property had been misplaced or compromised. Based on the undertaking’s evaluation on the time, its ONT and ONG crypto property, together with different on-chain property, remained unaffected.
Public node remained at block 20,770,893
Ontology’s first-party notice stated it recognized the potential concern throughout a each day security examine. The discover didn’t specify the technical situation below evaluate, which methods is likely to be concerned, or what findings would permit manufacturing to renew.
The undertaking stated the suspension’s length was undetermined and that it could issue a separate announcement earlier than or when the community resumed. It additionally stated it could not course of on-chain transactions whereas block manufacturing remained suspended. Ontology didn’t disclose a public restart timetable within the discover.
Those statements hold the episode distinct from a confirmed exploit or assault. The community interruption is obvious, however the undertaking’s asset-safety assertion was a preliminary evaluation made whereas the evaluate was nonetheless underway. Ontology didn’t report a loss, compromise, or lively assault in both of its preliminary 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 distinction between the block timestamp and the later snapshot was 5 hours, six minutes, and 23 seconds.
That calculation measures time for the reason that final block seen via the documented node. The node information doesn’t clarify why manufacturing stopped, however its unchanged peak aligns with Ontology’s assertion that the mainnet had been suspended.
The subsequent materials replace is whether or not validators resume block manufacturing and what Ontology’s review finds. A restart would set up the ultimate length, whereas a later technical clarification may present whether or not the precautionary halt prevented an incident or addressed a priority that didn’t turn into one.
The put up Ontology halts mainnet transactions as technical team investigates potential security issue appeared first on CryptoSlate.
