Move the 'calldataCost' from the 'callGasLimit' to 'validationGasLimit' #7
Conversation
This file contains 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
It is reasonable to assume the "inner" call is the first piece of data known to the transaction sender. This includes the gas limit needed for the "inner" call to happen. However, the 'calldataCost' also depends on the validation and paymaster data, creating a chicken-or-egg problem. Moving the costs of caldata to validation defers the calculation of expected calldata cost and allows solving the paradox in most cases.
Base automatically changed from
unused_gas_penalty_separator_tx
to
native_account_abstraction
November 14, 2023 15:44
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.
It is reasonable to assume the "inner" call is the first piece of data known to the transaction sender.
This includes the gas limit needed for the "inner" call to happen. However, the 'calldataCost' also depends on the validation and paymaster data, creating a chicken-or-egg problem.
Moving the costs of caldata to validation defers the calculation of expected calldata cost and allows solving the paradox in most cases.
When opening a pull request to submit a new EIP, please use the suggested template: https://github.com/ethereum/EIPs/blob/master/eip-template.md
We have a GitHub bot that automatically merges some PRs. It will merge yours immediately if certain criteria are met: