Adjust MEV-Boost

Bid cutoff is timeout_get_header_ms: the last moment a getHeader bid is accepted, in milliseconds into the slot. A later cutoff can take a higher bid. Set late enough, the proposal misses the slot.

The late-in-slot deadline is late_in_slot_time_ms. The cutoff cannot sit on or past it. Console keeps the cutoff at least 1 ms earlier.

From the recommendation, I am ready to adjust opens Record your change. The line under the heading is Set them on your own infrastructure, then tell us what you set.

Type Cutoff you have set and Late in slot you have set, then Confirm change. That records what you deployed. It does not deploy it.

Recap of the params on file is the values currently recorded, not the recommendation. Download config saves that recorded file as mev-boost-config.yaml. The note under the recap says late_in_slot_time_ms is on file but is not a mev-boost flag, so it is not in the file. --min-bid and --relay-check are not stored, and they are unchanged.

Deploy that file on your MEV-Boost the way you already deploy config. Optimum has no write access to it.

Review cutoff, on the banner after a cutoff is recorded, opens the editor instead of the typed form. I have adjusted my cutoff records the sliders. Back to results leaves the editor. In that editor, Configuration matches the file you uploaded means you have not moved the cutoff since the upload. Unsaved changes to the cutoff means the editor and the file you uploaded differ. The editor says Export the new config and deploy it — nothing here reaches your infrastructure.

What changed after you deployed is under MEV outcome on this screen, not on the upload panel. See Where results show.