Ethereum just took a major leap forward: Exploring ZK-EVM On L3 StarkNet π
Discover the fundamental concepts that even non-tech people can understand in this thread!
π½π½π½
Generally, a ZK-EVM (Zero-Knowledge Ethereum Virtual Machine) is a variant of the EVM that uses zero-knowledge or validity proof technology to allow cryptographic proof of the execution of Ethereum-like transactions.
This means that the prover can demonstrate that a transaction has been executed correctly in a very efficient way (validity proofs) or without revealing any sensitive information about the transaction itself (zk zk proofs).
There are several different types of ZK-EVM projects, each with its own goals and trade-offs.
Some aim to be fully compatible with Ethereum, while others make minor modifications to Ethereum data structures to make development easier and proof generation faster.
Others support only a subset of the EVM's functionality, while still others use a completely different execution model.
ZK-EVM projects can improve the Ethereum platform in several ways.
Scalability: ZK-EVMs can help Ethereum process more transactions faster and at a lower cost by moving some of the work off the main chain.
Privacy: ZK-ZK-EVMs can help protect the privacy of transactions on Ethereum by allowing them to be verified without revealing the underlying data.
Compatibility: ZK-EVMs can be used with the Ethereum platform without any changes, making it easy to use with existing Ethereum applications.
Security/Confidentiality: most ZK-EVMs use a technology called validity proofs to prove that transactions have been executed without revealing all the underlying data, which can add an extra layer of security to Ethereum applications.
Did you know that even though StarkNet uses a different execution model than the EVM, a ZK-EVM is being built on top of it in Cairo as an L3 solution?
π€It may seem confusingπ€, let me break it downπ§:
Cairo is a programming language developed by StarkWare that is used to create validity proofs.
A validity proof is a way to prove that something is true in a very efficient way.
For example, you could prove that you know the answer to a math problem without actually revealing to anyone the entire calculation.
The @KakarotZkEvm community is working on writing a Cairo program that can prove the execution of EVM opcodes, while the @nethermindeth team has been working on transpiling Solidity to Cairo.
This has allowed them to successfully "warp" Uniswap V3, a decentralized exchange running on Ethereum, to Cairo.
Let's focus on the @KakarotZkEvm for this example:
The Kakarot community is implementing a ZK-EVM on a layer of the StarkNet network called L3.
L3 on StarkNet is an additional layer that sits on top of StarkNet L2 Ethereum and allows devs to create and run their own custom environments within StarkNet.
These environments can have their own virtual machines (VMs) and state machines, which are systems that keep track of the current state.
The Cairo programming language can be used to create verifiers, which are used to prove the correctness of computations. These verifiers can be used to deploy and prove the custom environments within StarkNet.
This allows devs to have any smart contract logic within StarkNet that are separate from the main native language.
Yes, devs can create custom environments on L3 with different types of VMs, such as a zkEVM, StarkEx instance, Urbit VM or any other tech that produces data or statements (e.g.
flight recorders, credit cards, identity, government programs, charities, expenses etc)
These environments are still fully composable with other environments on StarkNet and other L2s or L1 Ethereum, which means they can talk and interact with each other.
In conclusion, Cairo on L3 StarkNet is an incredibly powerful tool that provides developers with the flexibility to create custom environments and execute smart contracts with any logic and data that are supported by their VMs and state machines.
This is all within a secure, transparent, and reliable space that is fully compatible with the Ethereum network and all its existing components.
In other words: Just as a ποΈ brush is a small, useful tool among many others in an artist's set, the zkEVM is just one small, useful component among the many other capabilities available in the larger and more diverse system that is Cairoπ.