Repository navigation
Support FOCIL and Frames interaction - #5772
Draft
jihoonsong wants to merge 1 commit into
Draft
jihoonsong wants to merge 1 commit into
jihoonsong wants to merge 1 commit into
Conversation
This was referenced Oct 27, 2026
This branch has not been deployed
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
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.
Inspired by #5698 by @Marchhill, this PR proposes another approach to support FOCIL and Frames interaction. The main difference is that this approach let the CL to pass ILs instead of IL transactions, achieving a better design abstraction. It makes the CL ignorant to the logic related to transactions and Profile 2 transactions validation, isolating it to the EL.
As a trade-off, the ILs parameter of newPayload and FCU can contain duplicate transactions. This could consume more engine APIs bandwidth on average, but the maximum size is still 128KiB. Assuming the size of payload at 200M gas limit is 3MB, 128KiB / 3MB ~= 4.4%. Given that payload size will grow over time, perhaps this trade-off is worth to make.
Related: ethereum/execution-apis#960