Repository navigation
caps/eth: define the eip-8141 frame transaction receipt encoding - #283
Open
AnkushinDaniil wants to merge 1 commit into
Open
AnkushinDaniil wants to merge 1 commit into
AnkushinDaniil wants to merge 1 commit into
Conversation
3 tasks
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
1 participant
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.
EIP-8141 adds frame transactions (type
0x06). Their receipts have no transaction-level status and no bloom. They carry the payer and one receipt per frame instead. The EIP Networking section says that in the Receipts message a frame receipt is encoded mirroring its consensusReceiptPayload:[tx-type, cumulative-gas, payer, [[status, [execution-gas-used, state-gas-used], logs], ...]]eth.md still says all receipts share the four field encoding, so the spec and the clients that ship frames (geth, Nethermind, reth) disagree with it. This change adds the frame receipt shape to the Receipt Encoding and Validity section, and it explains how to rebuild the consensus encoding for the receipts-root check: drop tx-type from the list and prefix the RLP of the rest with
0x06, with no bloom.The EIP does not name the eth version that carries this shape, so this text uses the EIP wording. If maintainers prefer, the note can be tied to a specific version and added to the change log.