Add VIP: Interstellar Part 1 - EVM Upgrades - #104
Draft
otherview wants to merge 1 commit into
Draft
Conversation
This file contains hidden or 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
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.
This PR introduces the Interstellar EVM Upgrade Specification, which aligns the VeChainThor EVM with the Ethereum Cancun, Prague and Osaka releases. VeChainThor's EVM currently targets Shanghai, adopted as part of Galactica (VIP-242); this proposal advances it by three Ethereum releases in a single fork.
This is Part 1 of the Interstellar upgrade. Ethereum transaction equivalence will be specified in a separate follow-up VIP.
Opcodes
TLOAD/TSTOREtransient storage, 100 gas eachMCOPYmemory copying instructionSELFDESTRUCTrestricted to contracts created in the same executionCLZcount-leading-zeros opcodePrecompiled contracts
0x0bthrough0x11P256VERIFYat address0x0100MODEXPinputsMODEXPgas cost increaseOther
All gas constants and precompile addresses are adopted unchanged from the referenced EIPs. With these changes VeChainThor adopts the complete set of execution layer EIPs from the Osaka upgrade; the Osaka EIPs not adopted concern blobs and the beacon chain.
Deviations from Ethereum. The VIP documents each point where observable behaviour differs, so that contract authors porting code between the two networks are not caught out:
MODEXPgas cost increaseOther
All gas constants and precompile addresses are adopted unchanged from the referenced EIPs. With these changes VeChainThor adopts the complete set of execution layer EIPs from the Osaka upgrade; the Osaka EIPs not adopted concern blobs and the beacon chain.