Difference between revisions of "Lighthouse validator client --builder-proposals"
Jump to navigation
Jump to search
| (8 intermediate revisions by one other user not shown) | |||
| Line 1: | Line 1: | ||
{{lc}} | {{lc}} | ||
| − | + | ||
| − | <code>[[lighthouse vc]] --builder-proposals</code> | + | * <code>[[lighthouse vc]] --builder-proposals</code> |
| + | |||
| + | |||
| + | <code>[[lighthouse validator client --help]]</code> | ||
| + | :If <code>--builder-proposals</code> is set, Lighthouse will query the [[Beacon Node]] for only [[block headers]] during proposals and will [[sign over headers]]. Useful for outsourcing execution payload [[construction]] during [[proposals]]. | ||
Latest revision as of 13:36, 25 August 2022
lighthouse vc --builder-proposals
lighthouse validator client --help
- If
--builder-proposalsis set, Lighthouse will query the Beacon Node for only block headers during proposals and will sign over headers. Useful for outsourcing execution payload construction during proposals.
Related[edit]
mev-boost: lighthouse bn --builder YOUR_SERVICE_URL
See also[edit]
lighthouse validator client, --help, Lighthouse validator errors, logs, Fee recipientmev-boost:[ -addr string | -genesis-fork-version string | -goerli | -loglevel | -json | -kiln | -mainnet | -relay-check | -sepolia | -ropsten | -request-timeout | -version | mev-boost --help ]lighthouse: [ account | beacon_node | boot node | account manager | database manager | validator client ], --help, --version, Releases, Ligthouse WARN, Paul Hauner, Lighthouse checkpoint sync, Lighthouse logs, Changelog
Advertising:
