Encode requests correctly in t8n#1040
Merged
petertdavies merged 4 commits intoethereum:forks/praguefrom Nov 25, 2024
Merged
Conversation
SamWilsn
approved these changes
Nov 22, 2024
Fix up black and mypy in `fix-t8n-requests`
3 tasks
danceratopz
pushed a commit
to danceratopz/execution-specs
that referenced
this pull request
Oct 22, 2025
feat(forks,specs,fixtures): add eip-7840 blob schedule config
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
3 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.
What was wrong?
When hashed, requests consist of an identifier byte followed by arbitrary data. Internally EELS considers the identifier byte to be part of the request, but the
t8ninterface does not.How was it fixed?
Strip the identifier byte when encoding requests in
t8nCute Animal Picture