-
Notifications
You must be signed in to change notification settings - Fork 293
feat: Make BUILDER_PROPOSAL_DELAY_TOLERANCE Configurable #7382
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
base: unstable
Are you sure you want to change the base?
Changes from 7 commits
9674c37
279a94d
407a1af
79b9db5
4207f3e
b6672a9
e34f69a
819dd81
ee9fd8c
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,18 @@ | ||
## Builder Proposal Delay Tolerance | ||
meta-duck marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
||
You can now configure the builder proposal delay tolerance (MEV block builder timeout) via the following flag: | ||
|
||
|
||
``` | ||
--builder-proposal-delay-tolerance=<milliseconds> | ||
``` | ||
|
||
- **Default value:** 1500 (milliseconds) | ||
- **Description:** Timeout for builder proposal delay tolerance. Increasing this value may allow the builder extra time to gather more transactions or MEV value, potentially improving block value and network efficiency. Lower values may reduce block proposal latency. | ||
|
||
**Example usage:** | ||
|
||
``` | ||
./nimbus_beacon_node --builder-proposal-delay-tolerance=2000 | ||
``` | ||
|
||
This option is useful for node operators who wish to tune performance for different environments or experiment with MEV builder timing. |
Uh oh!
There was an error while loading. Please reload this page.