-
Notifications
You must be signed in to change notification settings - Fork 788
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
isthmus: operator fee #388
Draft
yuwen01
wants to merge
21
commits into
ethereum-optimism:optimism
Choose a base branch
from
yuwen01:yuwen/operator-fee
base: optimism
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Draft
Changes from 12 commits
Commits
Show all changes
21 commits
Select commit
Hold shift + click to select a range
67b54be
added types + tests
yuwen01 35d33ca
added logic to state_transition, passes all existing tests
yuwen01 53a6083
fix small typo, add scaling factor
yuwen01 a91c47b
clean up some comments
yuwen01 c3c8f0b
reset testdata
yuwen01 0e608d3
add HoloceneL1AttributesSelector
yuwen01 f50ef90
reset testdata
yuwen01 86cc3e5
merge main
yuwen01 add6927
fixed test
yuwen01 98335d0
fix to rollup_cost_test
yuwen01 60a5bae
fees go to operatorFeeVault
yuwen01 327135d
moved operator fee scalars into separate slot
yuwen01 4d7990a
start change to isthmus + new design
yuwen01 ebf2bb0
merge optimism
yuwen01 8083162
finish merge
yuwen01 a71c3e2
Update to Isthmus (#2)
leruaa fd574ef
Merge remote-tracking branch 'upstream/optimism' into yuwen/operator-fee
leruaa 0f997c3
include Isthmus in the banner
leruaa b9e6d2d
Revert "include Isthmus in the banner"
leruaa 8461358
fix operator fee params storage ordering
leruaa cb76ebd
fix operator fee params decoding
leruaa File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
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
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
Some generated files are not rendered by default. Learn more about how customized files appear on GitHub.
Oops, something went wrong.
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
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
Oops, something went wrong.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I lean towards not adding a new hook and just making the L1 cost function more generic, a better name for it would be
L2CostFunc
which would imply it does the L2 specific fee calculations. Curious what other people thinkThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I thought about this too. Currently, these are the function signatures for the L1CostFunc and the OperatorCostFunc
I could potentially package up the
gasUsed
andisRefund
together into anOperatorCostData
or something. Then, we'd have this type.which returns the l1 cost and operator cost as a pair.
This pattern seems clunkier to me -- though the L1 fee and Operator fee are conceptually similar, I don't like returning both in a single function. For example, when calculating refunds, we only need the operator fee but not the L1 fee.
I'd definitely be open to unifying the two with a cleaner function design though.