Closed Brechtpd closed 1 month ago
Should we start doing PR in revm main instead of using branches?
The difficulties of having different repos. We should do PRs but not sure what mechanism would be best. Maybe we should do PRs to the main branch on revm side and use specific revs on the raiko side, each revm update also requires a PR in raiko to update the revs which I guess is fine.
Some fixes:
feat/zk-op
revm branch. This is now fixed in thev35_taiko_v2
branch: https://github.com/taikoxyz/revm/commit/ec20417a94bd9b6092c6d5c205c1b68f5851b7e8c-kzg
feature is enabled, so each block containing a call to this precompile would not work correctly. For cancun support in non-native provers we will also have to make sure thatKzgProof::verify_kzg_proof
(https://github.com/taikoxyz/revm/blob/a5c01f345f4362f4d5d8bbddf37e9d8aeb27b0d3/crates/precompile/src/kzg_point_evaluation.rs#L73) works correctly without file IO. I haven't tested it yet, but I think it should be okay because revm also avoids using file io to load in the trusted setup data: https://github.com/taikoxyz/revm/blob/a5c01f345f4362f4d5d8bbddf37e9d8aeb27b0d3/crates/primitives/src/kzg/env_settings.rs#L51. In any case, Taiko doesn't support cancun yet so we don't really need this to work for all provers yet.Issues 1/2 can be triggered in ethereum block
19899808
at tx 65, so that block can be used for testing.