chore(all): move eof from osaka to speculative #1507
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.
🗒️ Description
As upset as I am with the decision, I am ripping the band-aid off fast. I hope we can include EOF in a future fork.
I've created a new folder within
tests/
calledspeculative
. This will contain tests for features that are not currently CFI'd for future forks. Verkle will sit here in the near future too.I've created a new fork called
EOFv1
for simplicity. This should be the only breaking change for filling and consuming existing EOF fixtures. Thus clients will need to add this fork. Evmone should additionally add this fork to fill the EOF tests.A new label is added to EEST called
fork:eof
. I will relabel all the existing EOF PRs and issues with this.🔗 Related Issues
ethereum/EIPs#9703
ethereum/pm#1499
✅ Checklist