forked from privacy-scaling-explorations/zkevm-circuits
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Move chain_id from Tx to Block on mock (privacy-scaling-explorations#439
) * update: Move `chain_id` from Tx to Block on mock When generating a `TestContext` now, users will be able to set the `chain_id` parameter only at block level but not at tx one. Anyway, `MockTransaction` will still have this field. But there's no public API to interact with it. Instead, the values of the `chain_id` for the txs of a block will automatically be set to the value that was set as `chain_id` for the block. This closes the circle on the turn arround that was done in privacy-scaling-explorations/zkevm-specs#168 by adding `CHAINID` as a blockCtx Opcode rather than a Tx one for simplification & optimization purposes. Resolves: privacy-scaling-explorations#437 * update: Update Cargo.lock * fix: Reference MockTransaction instead of MockBlock
- Loading branch information
Showing
4 changed files
with
46 additions
and
40 deletions.
There are no files selected for viewing
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters