Repository navigation
Move common submission arguments to the submission configuration - #5110
Conversation
|
Claude finished @jmg-duarte's task in 1m 15s —— View job PR ReviewClean, well-scoped tech-debt cleanup — moving I left one inline comment flagging a silent config-migration hazard: Otherwise LGTM. The loss of per-mempool tip granularity is intentional per the PR description.
|
|
|
||
| /// The mempools to submit settlement transactions to. Can be the public | ||
| /// mempool of a node or the private MEVBlocker mempool. | ||
| #[serde(rename = "mempool", default)] |
There was a problem hiding this comment.
Heads-up on a silent config-migration hazard with this move: unlike SubmissionConfig, the Mempool struct does not have #[serde(deny_unknown_fields)]. So any deployment config that still carries max-additional-tip / additional-tip-percentage under [[submission.mempool]] after this change will not error — the keys are silently ignored, and the values fall back to the defaults (default_max_additional_tip = 3 gwei, default_additional_tip_percentage = 0.05).
Concretely: if a production config currently sets e.g. max-additional-tip = "5000000000" per-mempool and isn't migrated to [submission] in lockstep with this binary, the effective max tip silently drops from 5 gwei to 3 gwei. Worth ensuring all deployment configs are updated alongside this PR (and ideally calling it out in the release notes), since there's no compile- or load-time guard to catch a stale config.
There was a problem hiding this comment.
MartinquaXD
left a comment
There was a problem hiding this comment.
Good change but doesn't address the ugly configuration fully.
86c39bf to
e7e4e6c
Compare
|
Claude finished @jmg-duarte's task in 1m 28s —— View job PR ReviewRe-reviewed after the latest push ( Looks good:
Note (already acknowledged, not blocking): LGTM. ✅
|
Description
Before we move the builder submission further, it's time we take care of some tech debt that we accrued over time by cleaning up the configuration file. To start, we move the
max-additional-tipandadditional-tip-percentagethat we always set to the same values up to the commonsubmissionsection.Changes
max-additional-tipandadditional-tip-percentageto the commonsubmissionsectionHow to test
Existing tests shouldn't break, namely E2E ones