fix: ensure DA transaction throttling uses params that are set #616
Conversation
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
danyalprout
force-pushed
the
da-settings-config
branch
from
01cbfc9 to
402caf0
Compare
3 tasks
|
Closing in favor of flashbots/op-rbuilder#8 |
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.
📝 Summary
OpDAConfigthat the RPC endpoint does.💡 Motivation and Context
Prior to this PR, I believe setting throttling via the RPC would not have any impact as an unrelated DAConfig object is created here. Part of the work to fix: #613
✅ I have completed the following steps:
make lintmake test