Ethereum: Understanding ZKSync “system contracts” and EVM Proompomiles
In the introduction and implementation of intelligent contracts in the Ethereum network, developers must select Bet very popular approaches: ZK-Syted (ZS) system contracts and EVM-promotales. In this article, we explore the differences between the two approaches and examine when each is appropriate.
What are the ZKSync systems?
The ZKSynched Systems are a new standard for the introduction of the Ethereum Smart, which was introduced in June 2021. They aim to improve the performance and safety of Z -sync deployment by implementing a more efficient and solid way to complete the code in Blockchain.
This is how it works:
- ZS contracts use EVM (Ethereum virtual machine) under the hood, as do other Ethereum contracts.
However, the ZS contracts have an additional layer of abstraction. They are essential pre -composed configurations that include all the necessary codes that are performed in the block chain.
- When the developer wants to introduce a contract for ZK-Syntched, they can use a tool such as ZKSync or hardhat to create a ZS contract configuration from their code.
What are the EVM promoumoppiles?
EVM Proompices, also known as ‘system contracts’, are similar to ZK-Sync system contracts, but instead operate on EVM. They allow developers to assemble and introduce Ethereum smart contracts directly into the block chain without a separate assembly process.
This is how it works:
- When the developer wants to enable the contract, they can use a tool like a web3.js or truffel reference to create their EVM Proompompile code.
- The preComile is then stored in a decentralized storage solution, such as an inter -planetary file system (IPFS).
- To complete the contract in the block chain, the developer must link to the Prompile ZS contract lineup with a tool such as ZKSYC or Hardhat.
Main Differences:
Here are the most important distinctions between ZK-System agreements and EVM-SEWs:
And and the ZK-Sync system contracts EVM Promompices (System Contracts) |
And — | — | — |
And
performance | Requires a separate assembly process Works on EVM
And
Code abstraction | Additional layer of abstraction built on agreement From EVM under the bonnet
And
Recording Requirements | Requires separate storage solutions (eg ZS contracts) | No need for separate storage solutions
When to choose ZK -Synthem contracts?
ZK-Sync contracts are a good choice when:
- You want more control in the performance environment and the abstraction of the code.
- Your agreement requires additional features or optimization that cannot be achieved with EVM pre -compensation.
When to choose EVM promoumopiles (system contracts)?
EVM Proompices (system contracts) are a good choice when:
- You need to install the contract directly in the block chain without a separate assembly process.
- Your contract is small in size and requests minimal optimization.
In summary, although both synchronized system contracts and EVM pre -compensation can be used to introduce the Ethereum Smart, they have clear differences in the performance environment, the code abstraction and the storage requirements. Understanding thesis workers developers can choose an approach that best suits their needs and goals.
