Update PROVER_INPUT opcode value
#42
Merged
Conversation
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
Nashtare
added
the
crate: evm_arithmetization
muursh
approved these changes
Feb 16, 2024
Nashtare
added a commit
that referenced
this pull request
Feb 18, 2024
* Implement EIP-4788 * Cleanup test suite * Fix tests * Apply comments * Update PROVER_INPUT opcode value (#42)
BGluth
pushed a commit
that referenced
this pull request
Jun 17, 2024
Ran `cargo update` & `cargo upgrades`
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PROVER_INPUTcustom opcode is currently set to0x49, which would conflict with the new BLOBHASH opcode introduced in EIP-4844 for Cancun (see #41).The new value is set to
0xEE, to still easily distinguish it from all thePUSHvariants it is combined with on the CPU side.