spacesmutjeUnderstanding zkSync: The role of the Sequencer
The role of a sequencer in zkSync is crucial for the operation and efficiency of the zk-rollup system. The sequencer is responsible for several key functions that ensure the smooth processing and finalization of transactions on the zkSync network.Key Responsibilities of a Sequencer in zkSyncTransaction Ordering and Batching:The sequencer collects transactions from users, orders them, and batches them into blocks. This ordered sequence of transactions is essential for maintaining the integrity...
spacesmutjeUnderstanding zkSync: CRS - Common Reference String
The Common Reference String (CRS) is a crucial component in setting up certain types of zero-knowledge proofs, particularly non-interactive zero-knowledge proofs (NIZKs) and zk-SNARKs. Let's break this down in detail with some relatable examples:Purpose of the CRSThe CRS serves as a shared, trusted setup that both the prover and verifier use to create and verify proofs. It's like a mutually agreed-upon rulebook that both parties refer to during the proof process.How it worksImagine ...
spacesmutjeUnderstanding zkSync: ZKP, zk-SNARK, zk-STARK
Zero-knowledge proofs, zk-SNARKs, and zk-STARKs are all cryptographic techniques that allow one party (the prover) to prove to another party (the verifier) that they know a piece of information, without revealing the information itself. However, there are important differences between these approaches:Zero-Knowledge Proofs (ZKPs)ZKPs are the broadest category, encompassing both zk-SNARKs and zk-STARKs. They allow a prover to demonstrate knowledge of a secret without revealing any information ...
Build. Create. Strive. Be yourself. There is a place for you in web3.
spacesmutjeUnderstanding zkSync: The role of the Sequencer
The role of a sequencer in zkSync is crucial for the operation and efficiency of the zk-rollup system. The sequencer is responsible for several key functions that ensure the smooth processing and finalization of transactions on the zkSync network.Key Responsibilities of a Sequencer in zkSyncTransaction Ordering and Batching:The sequencer collects transactions from users, orders them, and batches them into blocks. This ordered sequence of transactions is essential for maintaining the integrity...
spacesmutjeUnderstanding zkSync: CRS - Common Reference String
The Common Reference String (CRS) is a crucial component in setting up certain types of zero-knowledge proofs, particularly non-interactive zero-knowledge proofs (NIZKs) and zk-SNARKs. Let's break this down in detail with some relatable examples:Purpose of the CRSThe CRS serves as a shared, trusted setup that both the prover and verifier use to create and verify proofs. It's like a mutually agreed-upon rulebook that both parties refer to during the proof process.How it worksImagine ...
spacesmutjeUnderstanding zkSync: ZKP, zk-SNARK, zk-STARK
Zero-knowledge proofs, zk-SNARKs, and zk-STARKs are all cryptographic techniques that allow one party (the prover) to prove to another party (the verifier) that they know a piece of information, without revealing the information itself. However, there are important differences between these approaches:Zero-Knowledge Proofs (ZKPs)ZKPs are the broadest category, encompassing both zk-SNARKs and zk-STARKs. They allow a prover to demonstrate knowledge of a secret without revealing any information ...
Build. Create. Strive. Be yourself. There is a place for you in web3.
Subscribe to spacesmutje
Subscribe to spacesmutje
Share Dialog
Share Dialog
<100 subscribers
<100 subscribers
A transaction on zkSync goes through the following process to be submitted and finalized on the Ethereum Layer 1 (L1):
Transaction Submission:
A user submits a transaction to the zkSync network by sending it to the zkSync sequencer node[1][14].
The sequencer collects transactions into batches or blocks[14].
Transaction Execution:
The sequencer executes the transactions in the batch using the zkEVM (a zkSync-specific virtual machine similar to the Ethereum Virtual Machine)[1][14].
This execution happens off-chain, separate from the Ethereum L1 chain.
Proof Generation:
After executing the batch of transactions, the sequencer generates a cryptographic zero-knowledge proof (ZK-proof) that attests to the validity of the state transition resulting from those transactions[1][5][14].
This ZK-proof is generated using advanced cryptographic techniques like zk-SNARKs or zk-STARKs.
Data Availability:
The sequencer submits the transaction data and state updates (known as the state diff) to the zkSync smart contract deployed on the Ethereum L1[3][5][14].
This data is necessary for anyone to reconstruct the zkSync state and verify the ZK-proof.
Proof Submission:
The sequencer submits the generated ZK-proof to the zkSync smart contract on the Ethereum L1[1][5][14].
Proof Verification:
The zkSync smart contract verifies the validity of the submitted ZK-proof[1][5][14].
If the proof is valid, it updates the zkSync state root on the Ethereum L1, effectively finalizing the batch of transactions.
Finality:
Once the state root is updated on the Ethereum L1, the transactions in that batch are considered final and irreversible, inheriting the security and finality properties of the Ethereum L1 blockchain[1][5][20].
This process allows zkSync to leverage the security of Ethereum while processing transactions off-chain for scalability. The ZK-proofs cryptographically guarantee the validity of the off-chain computations, and the Ethereum L1 acts as a secure data availability and settlement layer for the zkSync transactions[1][5][14].
Citations: [1] https://plisio.net/de/blog/zksync-the-next-step-in-ethereum-s-evolution [2] https://blog.suhailkakar.com/the-developers-guide-to-zero-knowledge-and-zksync-era [3] https://blog.krypcore.com/a-beginners-guide-to-zk-zero-knowledge-rollups-c1850dda4a8c?gi=38beacfd09b4 [4] https://docs.zksync.io/build/developer-reference/account-abstraction.html [5] https://ethereum.org/en/developers/docs/scaling/zk-rollups/ [6] https://zksync.io/ethos [7] https://www.kucoin.com/learn/crypto/top-ethereum-zk-rollup-projects [8] https://blog.thirdweb.com/zk-rollup/ [9] https://pixelplex.io/blog/overview-of-zk-rollups/ [10] https://www.kvarnx.com/content/what-is-the-difference-between-optimistic-rollups-and-zk-rollups [11]
A transaction on zkSync goes through the following process to be submitted and finalized on the Ethereum Layer 1 (L1):
Transaction Submission:
A user submits a transaction to the zkSync network by sending it to the zkSync sequencer node[1][14].
The sequencer collects transactions into batches or blocks[14].
Transaction Execution:
The sequencer executes the transactions in the batch using the zkEVM (a zkSync-specific virtual machine similar to the Ethereum Virtual Machine)[1][14].
This execution happens off-chain, separate from the Ethereum L1 chain.
Proof Generation:
After executing the batch of transactions, the sequencer generates a cryptographic zero-knowledge proof (ZK-proof) that attests to the validity of the state transition resulting from those transactions[1][5][14].
This ZK-proof is generated using advanced cryptographic techniques like zk-SNARKs or zk-STARKs.
Data Availability:
The sequencer submits the transaction data and state updates (known as the state diff) to the zkSync smart contract deployed on the Ethereum L1[3][5][14].
This data is necessary for anyone to reconstruct the zkSync state and verify the ZK-proof.
Proof Submission:
The sequencer submits the generated ZK-proof to the zkSync smart contract on the Ethereum L1[1][5][14].
Proof Verification:
The zkSync smart contract verifies the validity of the submitted ZK-proof[1][5][14].
If the proof is valid, it updates the zkSync state root on the Ethereum L1, effectively finalizing the batch of transactions.
Finality:
Once the state root is updated on the Ethereum L1, the transactions in that batch are considered final and irreversible, inheriting the security and finality properties of the Ethereum L1 blockchain[1][5][20].
This process allows zkSync to leverage the security of Ethereum while processing transactions off-chain for scalability. The ZK-proofs cryptographically guarantee the validity of the off-chain computations, and the Ethereum L1 acts as a secure data availability and settlement layer for the zkSync transactions[1][5][14].
Citations: [1] https://plisio.net/de/blog/zksync-the-next-step-in-ethereum-s-evolution [2] https://blog.suhailkakar.com/the-developers-guide-to-zero-knowledge-and-zksync-era [3] https://blog.krypcore.com/a-beginners-guide-to-zk-zero-knowledge-rollups-c1850dda4a8c?gi=38beacfd09b4 [4] https://docs.zksync.io/build/developer-reference/account-abstraction.html [5] https://ethereum.org/en/developers/docs/scaling/zk-rollups/ [6] https://zksync.io/ethos [7] https://www.kucoin.com/learn/crypto/top-ethereum-zk-rollup-projects [8] https://blog.thirdweb.com/zk-rollup/ [9] https://pixelplex.io/blog/overview-of-zk-rollups/ [10] https://www.kvarnx.com/content/what-is-the-difference-between-optimistic-rollups-and-zk-rollups [11]
No activity yet