Skip to content
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

Add suggested block gas limit parameter #712

Merged
merged 5 commits into from
Dec 6, 2024
Merged

Conversation

0xfornax
Copy link
Member

@0xfornax 0xfornax commented Dec 5, 2024

No description provided.

@jshufro
Copy link
Contributor

jshufro commented Dec 5, 2024

Couple things:

It's a gas limit, not a block limit (see lh docs here)

      --gas-limit <INTEGER>
          The gas limit to be used in all builder proposals for all validators
          managed by this validator client. Note this will not necessarily be
          used if the gas limit set here moves too far from the previous block's
          gas limit. [default: 30,000,000]

And, the beacon-apis spec says this about MEV-boost:

Prepares the beacon node for engaging with external builders. The information must be sent by the beacon node to the builder network. It is expected that the validator client will send this information periodically to ensure the beacon node has correct and timely registration information to provide to builders. The validator client should not sign blinded beacon blocks that do not adhere to their latest fee recipient and gas limit preferences.

Note that only registrations for active or pending validators must be sent to the builder network. Registrations for unknown or exited validators must be filtered out and not sent to the builder network.```

Which implies that the value is not just used for locally built blocks, but part of the registration that is sent to relays, and while it may not be respected, it is still available to builders.

@0xfornax 0xfornax changed the title Add suggested block limit parameter Add suggested block gas limit parameter Dec 5, 2024
@0xfornax
Copy link
Member Author

0xfornax commented Dec 5, 2024

Which implies that the value is not just used for locally built blocks, but part of the registration that is sent to relays, and while it may not be respected, it is still available to builders.

I understand the EC value would be used if producing a block locally and the BN/VC value when externally building it.

@0xfornax 0xfornax merged commit 3e9c68b into master Dec 6, 2024
4 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants