Original author: Haotian (Twitter: @tmel0211), blockchain security practitioner
Some friends have criticized @zkSync for always being down, but to be precise, it is more accurate to say that it has "unstable block production" rather than being completely down.
Essentially, the time at which transactions submitted by Sequencer are ultimately Verified is unstable, but users do not perceive this instability on the interaction end because zkSync's Verify design has inherent confirmation lag.
The instability in the future decentralization stage will be alleviated. I drew a workflow to discuss with everyone.

The reason why users perceive "downtime" may be due to transaction failures caused by compatibility issues between some DApps and the underlying blockchain. After all, developing DApps on zkSync is already a big challenge in itself.
I observed that the status change from Commit to Verified in the official browser usually takes about 30 minutes to 1 hour, but this does not significantly affect the user interaction with the DApp.
This article focuses on popularizing the technical underlying logic of zkSync, helping readers gain a clear understanding of zkSync.

As shown in the workflow, zkSync operates in the following steps:
1. User sends batch transactions to Sequencer through relay for sorting.
2. The Sequencer is responsible for sorting, aggregating, and packaging transactions into batches to form a Merkle tree.
3. zkPorter generates zk-SNARK proofs for the Merkle tree; the zk-SNARK proofs are relayed to the Validators of L2 and the Commit Hash is generated for the L1 main chain; Validators are responsible for verifying the proofs.
4. The correctness of zk-SNARK proof is verified and submitted to the L1 smart contract to generate the Verify Hash.
5. Matching the Commit Hash and Verify Hash of zkSync smart contracts on L1.
6. After successful matching, a Verified Transaction is generated and ultimately recorded on the blockchain.
7. If the matching fails, the original Commit Hash is invalidated, and the Sequencer resubmits the batch to go through the process again.
Here it is important to emphasize that zkSync adopts "Two-Phase Commit (2PC)" and finally determines the legal transaction batch through the hash verification of the two stages of Commit Hash and Verify Hash.
This approach can ensure the consistency and security of data in the system operation process. In my personal understanding, it is also a decentralized idea that demonstrates the mutual constraints between the Sequencer and Validator system components, which is commendable.
zkSync's Workflow mainly consists of four roles: Relay, Sequencer, zkPorter, and Validator. There are many "unstable factors" in the coordination work.
Can be summarized as node functional stability, node collaboration stability, and algorithm and underlying protocol complexity. Any error in any link may result in block delay. Common Arbitrum Sequencer technical failures are typical, and zkSync will face even more challenges.
As for the algorithm complexity, it is the destiny of the zkSync chain and requires the full efforts of ecosystem developers to overcome. As for the stability of node intelligence and collaboration, I believe it will be effectively improved after the arrival of the decentralized stage in the future. The logic is also simple:
Multiple distributed nodes can avoid network instability caused by single point failures, which enhances system robustness. The distributed token incentive mechanism can provide a source of motivation for developers to maintain node stability.
Looking at it from a different perspective, Verifing's long verification time in the early stages of the ecosystem is not a problem. It can effectively enhance the security of the chain and avoid malicious behavior from certain nodes in the system.
In short, if you clarify the entire operation process of zkSync, further understand the technical complexity of layer 2 and the "special" mechanisms designed for security, it can strengthen your confidence in the L2 technology track.
Original Link
Welcome to join the official BlockBeats community:
Telegram Subscription Group: https://t.me/theblockbeats
Telegram Discussion Group: https://t.me/BlockBeats_App
Official Twitter Account: https://twitter.com/BlockBeatsAsia