01:44
News on October 20, Aptos released yesterday's mainnet incident report that the Aptos network began to experience transaction delays around 16:15 PDT on October 18 (07:15 Beijing time on October 19). Transaction load is not an issue with this event, and the submitted trades are not lost and no forks have occurred. Non-deterministic code caused the issue, and a fix has been deployed. The issue was resolved around 12:30 Beijing time on October 19.
On August 22, the Aptos core codebase submitted performance-focused code changes, and on October 16, the FeeStatement event went live, detailing fees/refunds for transactions. The initial code change introduced non-determinism that was only revealed by FeeStatement. Specifically, validators agreed that the gas budget for the transaction was not enough to execute the transaction, and due to the non-determinism introduced in the code change in August, they were unable to agree on the amount of gas used so far.
After identifying the actual event output discrepancies for non-deterministic transaction execution, the problem is traced back to the FeeStatement event and code change in the code. At the same time, a developer starts running transaction simulations with code changes to revert mapping changes, repeating execution to ensure consistent results. In addition, the resumption of code commits has landed, and docker builds for validator operators have begun, after which a new version is released.

