ZKsync Recommends Extending EraVM Execution Delay to 24 Hours

ZKsync has recommended extending the execution delay time of the EraVM chain from the current 3 hours to 24 hours, and announced that it will gradually phase out the existing execution environment over the next six months. Funds stored in regular externally owned accounts (EOA) do not require immediate action, but funds locked in smart contracts need to be verified according to the transition schedule of each chain. On the 4th, ZKsync announced five security measures to be applied to the EraVM chain on its official blog, including the immediate introduction of an upgrade framework, extension of execution delay time, and development of a second proof-of-stake validator, EraVender. The extension of the execution delay time is a measure to widen the response options before the blockchain state reaches an irreversible stage in the event of a potential attack. The EraVM is a virtual machine responsible for transaction execution in the ZKsync protocol, and this upgrade will affect chain operators and application developers. Individuals with funds stored in regular externally owned accounts currently do not need to take action, but those with funds held through smart contracts need to check the transition plans of each chain. The ZKsync Atlas chain is not affected by this upgrade.

This content is provided for general informational purposes only and doesn't constitute financial, investment, legal, or tax advice. Any events, rewards, online promotions, or related information mentioned herein should not be considered a recommendation, solicitation, or invitation to purchase, sell, trade, or otherwise deal in any crypto assets. Crypto assets are highly volatile and may result in loss. The availability of WEEX services, products, and related events may vary by region. You are responsible for ensuring that your participation is in accordance with applicable local laws and regulations.