A SNARK player actually announced that he was on par with STARK? The STARK era with @zksync is here so soon @Starknet shivering!
So, what is the new version Boojum upgraded by zkSync? Why did zkSync announce the upgrade of Stark so quickly? What is the essential difference between snark and stark? What impact will this upgrade have on the L2 market?
From the perspective of technical discussion, let’s quickly review and discuss.
Boojum is the transition version of zkSync from SNARK to STARK proof system. This means that zkSync’s Prover proof system will have the interface capability of STARK, but will still use the SNARK proof system to meet most mainstream needs.
Boojum is an option for zkSync to implement the zk Stack multi-chain strategy. Compared with SNARK, the STARK proof method has the ability of non-interactive verification and is suitable for complex non-recursive verification in a cross-chain environment.
The core difference between SNARK and STARK lies in the verification method. SNARK is based on mathematical assumptions and is suitable for zk deduction proofs based on the same public key under the same system; while the proof process of STARK contains redundant information and requires high computing resources.
The zkSync main chain will still use SNARK as the main proof system, and STARK is just an expansion capability of its multi-chain strategy. This is different from the strategic dimension of Starknet, but it may bring some competitive pressure to other L2 solutions such as Op Stark, Arbitrum Orbit and Polygon 2.0.
In general, zkSync transitioned to the STARK proof system through Boojum’s upgrade option, which shows that they recognize that SNARK has technical limitations in some aspects, and use the advantages of competitors to break through their own technical ceiling. This upgrade may have a certain impact on the L2 market, but the specific impact will be affected by the reaction and adoption of the market and developers.
View Original
This page may contain third-party content, which is provided for information purposes only (not representations/warranties) and should not be considered as an endorsement of its views by Gate, nor as financial or professional advice. See Disclaimer for details.
zkSync upgrade: Why did a SNARK player defect to STARK?
A SNARK player actually announced that he was on par with STARK? The STARK era with @zksync is here so soon @Starknet shivering!
So, what is the new version Boojum upgraded by zkSync? Why did zkSync announce the upgrade of Stark so quickly? What is the essential difference between snark and stark? What impact will this upgrade have on the L2 market?
From the perspective of technical discussion, let’s quickly review and discuss.
Boojum is the transition version of zkSync from SNARK to STARK proof system. This means that zkSync’s Prover proof system will have the interface capability of STARK, but will still use the SNARK proof system to meet most mainstream needs.
Boojum is an option for zkSync to implement the zk Stack multi-chain strategy. Compared with SNARK, the STARK proof method has the ability of non-interactive verification and is suitable for complex non-recursive verification in a cross-chain environment.
The core difference between SNARK and STARK lies in the verification method. SNARK is based on mathematical assumptions and is suitable for zk deduction proofs based on the same public key under the same system; while the proof process of STARK contains redundant information and requires high computing resources.
The zkSync main chain will still use SNARK as the main proof system, and STARK is just an expansion capability of its multi-chain strategy. This is different from the strategic dimension of Starknet, but it may bring some competitive pressure to other L2 solutions such as Op Stark, Arbitrum Orbit and Polygon 2.0.
In general, zkSync transitioned to the STARK proof system through Boojum’s upgrade option, which shows that they recognize that SNARK has technical limitations in some aspects, and use the advantages of competitors to break through their own technical ceiling. This upgrade may have a certain impact on the L2 market, but the specific impact will be affected by the reaction and adoption of the market and developers.