Repository navigation
Add EIP: Separate Metadata Section for EOF - #9100
Merged
Merged
Conversation
github-actions
Bot
added
c-new
Collaborator
|
✅ All reviewers have approved. |
eth-bot
added
e-consensus
eth-bot
changed the title
abcoathup
reviewed
Dec 6, 2024
abcoathup
reviewed
Dec 6, 2024
| title: Separate Metadata Section for EOF | ||
| description: Introduce a new separate metadata section to the EOF | ||
| author: Kaan Uzdogan (@kuzdogan), Marco Castignoli (@marcocastignoli), Manuel Wedler (@manuelwedler) | ||
| discussions-to: <URL> |
Contributor
There was a problem hiding this comment.
Please create a discussions topic in Eth Magicians using the template: https://ethereum-magicians.org/c/eips/5
Co-authored-by: Andrew B Coathup <28278242+abcoathup@users.noreply.github.com>
manuelwedler
reviewed
Dec 9, 2024
kuzdogan
changed the title
commented
Dec 9, 2024
|
The commit fe8cdb5 (as a parent of bbb3183) contains errors. |
eth-bot
changed the title
|
|
||
| ## Motivation | ||
|
|
||
| It is desirable to include metadata in contract's bytecode for various reasons. For instance, both the Solidity and Vyper compilers by default include the language and compiler version used to compile. Solidity additionally includes the IPFS or the Swarm hash of the Solidity contract metadata.json file, and the experimental Solidity flag. The current (pre-EOF) practice is to append this CBOR encoded metadata section in the contract's runtime bytecode, followed by the 2 bytes length of the CBOR encoded bytes. |
Contributor
There was a problem hiding this comment.
fwiw, in Vyper 0.4.1 (to be released), the integrity hash (using sha256 under to the hood) is now put into the initcode (not runtime code) (vyperlang/vyper#4234) to preserve bytecode space of the runtime code. That's also a smart way to deal with it ;)
added 2 commits
December 16, 2024 14:59
g11tech
approved these changes
Dec 17, 2024
eth-bot
enabled auto-merge (squash)
December 17, 2024 09:20
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
6 participants
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.
No description provided.