zkSync Era CodeHawks Competitive Audit Overview

The zkSync Era CodeHawks audit offers $500,000 in prizes for auditing a complex layer 2 rollup project.

### zkSync Era CodeHawks Kickoff: Competitive Audit Overview
* 👋 Hello and welcome to the zkSync Era CodeHawks kickoff, hosted by Karen Iingirl, a software engineer at Cypher, who will guide us through the competitive audit currently live on CodeHawks until **December 2nd**, with a total prize pool of **$500,000**.
* 📜 The project involves auditing **15,740 lines of Solidity code** for zkSync Era, an EVM-compatible layer 2 rollup that utilizes **zk proofs to scale Ethereum** while ensuring **security and decentralization**.
* 🔍 Stas and Vlad from Meta Labs provided insights into the Era contracts repository, emphasizing the **importance of the documentation for understanding the system's logic and functionalities**.
* 🔗 The structure of the contracts includes L1 contracts, state transitions, and a **Bridge Hub** that facilitates transactions between layer one and layer two, with **significant updates to the bridging process and data availability**.
* ⚙ New features include support for **custom data availability** and the introduction of a **Gateway settlement layer**, which allows for **more efficient and frequent settlements** between rollups.
* 🛠 Governance has also been upgraded to a **decentralized model**, with multiple governors managing the upgrade process, ensuring that **security and protocol changes are executed safely and effectively**.
* ⚠ Participants are advised to focus on the **bootloader and Gateway code**, as these areas contain **complex logic** that may present **unique challenges** during the audit.
* 💬 For further inquiries or clarifications, attendees are encouraged to utilize the **GitHub repo linked on the CodeHawks landing page** or engage with the **Cypher Discord community**.

zkSync Era | Layer 2 Rollup with Zero-Knowledge Proofs | Live Competition Kick-off

Book a smart contract audit here 👇
https://www.cyfrin.io/


Cyfrin Audits

Introduction to zkSync Era CodeHawks Kickoff and Contest Overview

Introduction of Karen Iingirl and the zkSync Era competitive audit.

Contest duration until December 2nd at noon UTC.

Overview of zkSync Era as an EVM-compatible layer 2 rollup using zk proofs.

Project details available in the GitHub README.

Instructions for asking questions during and after the stream.

Explanation of zkSync Era Contracts Repository by Stas and Vlad from Meta Labs

Introduction to the Era contracts repository and its documentation.

Audit conducted on a version under development, not the mainnet version.

Suggested reading order for the documentation.

Overview of L1 contracts folder and its contents, including state transition and chain initialization.

Explanation of Chain Type Manager and its functions.

Description of Bridge Hub contract and its role in bridging and chain creation.

Explanation of changes in bridging mechanism, introducing asset routers and asset handlers.

Discussion of custom data availability and its implementation.

Explanation of using another L2 as a settlement layer (Gateway).

Discussion of L1 nullifier and other minor contracts.

Explanation of changes to the chain admin contract for modularity.

Explanation of why L1 contracts are compilable for both EVM and RM environments.

Overview of system contracts folder and its contents.

Explanation of bootloader and its role in proof verification.

Discussion of the shift to decentralized governance.

Introduction to the key governance contract and its documentation.

Explanation of the different Governor contracts (ZK Protocol Governor, ZK Token Governor, ZK Ops Governor).

Description of the Key token and its implementation.

Explanation of Layer 1 contracts for accepting upgrades from Layer 2.

Detailed explanation of the protocol upgrade handler contract and its functions.

Discussion of the emergency upgrade process and its requirements.

Explanation of Guardians contract and its multi-sig implementation.

Discussion of the feasibility functions (soft freeze and hard freeze).

Concluding Remarks and Recommendations for the Audit

Recommendation to compare results with previous audits and external audit companies.

Advice to pay attention to specific areas of the code, such as bootloader and Gateway.

Reminder of information availability on GitHub and Discord.