Fix builder gas limit docs (#3569)
## Issue Addressed Make sure gas limit examples in our docs represent sane values. Thanks @dankrad for raising this in discord. ## Additional Info We could also consider logging warnings about whether the gas limits configured are sane. Prysm has an open issue for this: https://github.com/prysmaticlabs/prysm/issues/10810 Co-authored-by: realbigsean <sean@sigmaprime.io>
This commit is contained in:
parent
88a7e5a2ca
commit
614d74a6d4
@ -45,17 +45,25 @@ relays, run one of the following services and configure lighthouse to use it wit
|
||||
|
||||
## Validator Client Configuration
|
||||
|
||||
In the validator client you can configure gas limit, fee recipient and whether to use the builder API on a
|
||||
per-validator basis or set a configuration for all validators managed by the validator client. CLI flags for each of these
|
||||
will serve as default values for all validators managed by the validator client. In order to manage the values
|
||||
per-validator you can either make updates to the `validator_definitions.yml` file or you can use the HTTP requests
|
||||
In the validator client you can configure gas limit and fee recipient on a per-validator basis. If no gas limit is
|
||||
configured, Lighthouse will use a default gas limit of 30,000,000, which is the current default value used in execution
|
||||
engines. You can also enable or disable use of external builders on a per-validator basis rather than using
|
||||
`--builder-proposals`, which enables external builders for all validators. In order to manage these configurations
|
||||
per-validator, you can either make updates to the `validator_definitions.yml` file or you can use the HTTP requests
|
||||
described below.
|
||||
|
||||
Both the gas limit and fee recipient will be passed along as suggestions to connected builders. If there is a discrepancy
|
||||
in either, it will *not* keep you from proposing a block with the builder. This is because the bounds on gas limit are calculated based
|
||||
on prior execution blocks, so it should be managed by an execution engine, even if it is external. Depending on the
|
||||
connected relay, payment to the proposer might be in the form of a transaction within the block to the fee recipient,
|
||||
so a discrepancy in fee recipient might not indicate that there is something afoot.
|
||||
in either, it will *not* keep you from proposing a block with the builder. This is because the bounds on gas limit are
|
||||
calculated based on prior execution blocks, so an honest external builder will make sure that even if your
|
||||
requested gas limit value is out of the specified range, a valid gas limit in the direction of your request will be
|
||||
used in constructing the block. Depending on the connected relay, payment to the proposer might be in the form of a
|
||||
transaction within the block to the fee recipient, so a discrepancy in fee recipient might not indicate that there
|
||||
is something afoot.
|
||||
|
||||
> Note: The gas limit configured here is effectively a vote on block size, so the configuration should not be taken lightly.
|
||||
> 30,000,000 is currently seen as a value balancing block size with how expensive it is for
|
||||
> the network to validate blocks. So if you don't feel comfortable making an informed "vote", using the default value is
|
||||
> encouraged. We will update the default value if the community reaches a rough consensus on a new value.
|
||||
|
||||
### Set Gas Limit via HTTP
|
||||
|
||||
@ -91,7 +99,7 @@ Each field is optional.
|
||||
```json
|
||||
{
|
||||
"builder_proposals": true,
|
||||
"gas_limit": 3000000001
|
||||
"gas_limit": 30000001
|
||||
}
|
||||
```
|
||||
|
||||
@ -116,14 +124,14 @@ You can also directly configure these fields in the `validator_definitions.yml`
|
||||
voting_keystore_path: /home/paul/.lighthouse/validators/0x87a580d31d7bc69069b55f5a01995a610dd391a26dc9e36e81057a17211983a79266800ab8531f21f1083d7d84085007/voting-keystore.json
|
||||
voting_keystore_password_path: /home/paul/.lighthouse/secrets/0x87a580d31d7bc69069b55f5a01995a610dd391a26dc9e36e81057a17211983a79266800ab8531f21f1083d7d84085007
|
||||
suggested_fee_recipient: "0x6cc8dcbca744a6e4ffedb98e1d0df903b10abd21"
|
||||
gas_limit: 3000000001
|
||||
gas_limit: 30000001
|
||||
builder_proposals: true
|
||||
- enabled: false
|
||||
voting_public_key: "0xa5566f9ec3c6e1fdf362634ebec9ef7aceb0e460e5079714808388e5d48f4ae1e12897fed1bea951c17fa389d511e477"
|
||||
type: local_keystore voting_keystore_path: /home/paul/.lighthouse/validators/0xa5566f9ec3c6e1fdf362634ebec9ef7aceb0e460e5079714808388e5d48f4ae1e12897fed1bea951c17fa389d511e477/voting-keystore.json
|
||||
voting_keystore_password: myStrongpa55word123&$
|
||||
suggested_fee_recipient: "0xa2e334e71511686bcfe38bb3ee1ad8f6babcc03d"
|
||||
gas_limit: 333333333
|
||||
gas_limit: 33333333
|
||||
builder_proposals: true
|
||||
```
|
||||
|
||||
|
Loading…
Reference in New Issue
Block a user