zkEVM Code Contribution
You're interested in Scroll's open source vision. Now what?
zkEVM development requires a solid understanding of Halo2, the API/proof system our circuits uses. In order to get the most value contributing to this repo, please visit our research sections.
For developers who want to write ZK circuits in Halo2, you need to learn Rust. The Rust book is a great introductory read.
Once you've learned Rust, try to get your hands dirty by developing your first halo2 circuit! Here are a few resources we recommend:
- 1.First take a look at our specs, auditing videos, and zkevm docs, it’s very important that you understand at a high-level how the ZK-EVM architecture and all of its components work.
- 2.Read our contributors guide. These highlight important development practices that enables contributors to contribute efficiently and effectively.
- 3.Get started with a list of basic "first good issues"! These are meant as introductory issues for external contributors.
Scroll is building a Type 2.5 zkEVM (Fully EVM-Equivalent, with minor differences) whereas PSE is building a Type 1 zkEVM. See Vitalik's article for more details.
Scroll is a fork of PSE, so any fundamental changes that go to Scroll should start at PSE. If you have further questions, please reach out to us in our discord.
Last modified 1mo ago