Update EIP-4844: do not allow creation txs#6386
Closed
lightclient wants to merge 1 commit intoethereum:masterfrom
Closed
Update EIP-4844: do not allow creation txs#6386lightclient wants to merge 1 commit intoethereum:masterfrom
lightclient wants to merge 1 commit intoethereum:masterfrom
Conversation
github-actions
bot
added
c-update
Collaborator
|
🛑 Auto merge failed. Please see logs for more details, and report this issue at the |
lightclient
force-pushed
the
4844-no-create
branch
from
c4ff390 to
0cecc84
Compare
github-actions
bot
added
s-review
eth-bot
changed the title
lightclient
force-pushed
the
4844-no-create
branch
from
0cecc84 to
9edebc4
Compare
Merged
5 tasks
Member
Author
|
closed via #7038 |
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
2 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.
this builds on #6985, so that PR should be merged first
--
Allowing contract creation from 4844 transactions is unnecessary. If in the unlikely event that there is a use case for creating a contract while also sending blobs to the chain, the transaction should simple do it via
CREATEorCREATE2.