zkevm-circuits VS requests-for-proposals

They work with Ethereum Foundation for the zk-evm https://github.com/privacy-scaling-explorations/zkevm-circuits and imo nothing beats type 1 zk-evm - even if they are a bit "late".. it will matter on how the type 1 zk-evm will handle decentralization and incentives..

That zkEVM is the ONLY one that's EVM-equivalent. It's the only one supported by the Ethereum Foundation. It's the zkEVM that Scroll.io is helping develop. It's the same zkEVM that Loopring was working on with EF, and that Taiko is going to use. It's also open source.

zkEVM circuit auditing: The goal here is to find bugs in zkEVM circuits developed by the EF and others. All auditing techniques are fair play (e.g. code inspection, fuzzing, formal verification).

After The Merge, getting more scale into the system is probably the most pressing issue so much of our resources have been focused on 4844 and extensions of 4844 to "full sharding". Extensions of 4844 require a better `is_data_available()` function that instead of downloading everything performs Data Availability Sampling which is a hard problem to do in a decentralized/distributed yet reliable way. We just put out an [RFP](https://github.com/ethereum/requests-for-proposals/blob/master/open-rfps/das.md) to get more teams in this and are excited by the number of submissions. Reach out if this is the first time you've seen it and are interested in performing some work/research in this domain!