feat: add FMA for operator fee #186
Conversation
| - [Spec](https://github.com/ethereum-optimism/specs/pull/382) | ||
|
|
||
| ## Failure Modes and Recovery Paths | ||
|
|
There was a problem hiding this comment.
Database growth increase results in need for 4444 faster or other history expiry solution
There was a problem hiding this comment.
What are the other potential history expiry solutions? Just state pruning?
Also, the operator fee won't result in significant database growth on it's own right?
There was a problem hiding this comment.
This is a question for you to answer :)
Basically whatever the extra data to the L1 attributes txs is, that is stored to the db every 2s for OPM and Base, every 1s for Unichain/Ink/Soneium, so that adds up to be a lot over time. Its just a consideration and not a blocker. Eventually we need to use a diff based L1 attributes tx to not repeat data being sent over and over again
|
Any other failure modes that come to mind @tynes? Are there other external parties beyond wallets that may fail to update their fee estimation logic that we should be aware of? |
|
we have some considerations for generic hardforks here: could be useful to look at this too |
Description
This PR introduces the FMA for the operator fee feature, set to be included in Isthmus.
Additional context