zkSync Era is undergoing an upgrade and has great news for users and builders. After the most recent upgrade (VM version 1.4.2, Protocol version 22), which introduced EIP-4844 support and significantly reduced our rates by a factor of 10, this is the opportune time to introduce some new features and improvements to Protocol v24 .
The company experienced certain issues with v23 in its internal environments before deciding to standardize the improvements
Some of the improvements in the new version include the addition of precompiles for EVM curve operations, the zkSync Bridgehub, and a new precompile for P256Verify. In addition, certain operations have adopted revised pricing structures.
Creating trust and interoperability requires meeting specific quality requirements of the ZK Stack chain. To manage proof authentication across all chains, a standard set of Layer 1 smart contracts is required. Fair scale-up is required for all chains to prove the implementation of mechanisms.
Shared bridges are an important part of establishing uniform liquidity in the ecosystem. A single layer 1 bridge contract connects each L1 asset (ETH and ERC20s). These bridges facilitate user activities, such as withdrawals and deposits, across all ZK Stacks. There is also the positioning of their equivalents on the ZK Stack Chain.
The zkSync Bridgehub acts as the primary component that enables communication between bridges and all ZK Stack chain contracts through a centralized point; it makes it possible to secure L1 assets, including L3s and validiums, across all chains in the same contract. Additionally, all chains register at this connection point to communicate with other chains’ mailboxes, request L1>L2 transactions, and register to access the ecosystem.
State Transition Manager (STM) contracts are intended to authenticate evidence associated with all chains. In addition, it is responsible for implementing a DiamondProxy for each chain, which serves as the root and final representation of a chain on L1.
