Difference between revisions of "Lighthouse beacon node --execution-endpoint"
Jump to navigation
Jump to search
| (One intermediate revision by the same user not shown) | |||
| Line 13: | Line 13: | ||
Error! Please set either [[--execution-jwt]] file_path or [[--execution-jwt-secret-key]] directly via cli when using --execution-endpoint | Error! Please set either [[--execution-jwt]] file_path or [[--execution-jwt-secret-key]] directly via cli when using --execution-endpoint | ||
| + | |||
| + | lighthouse beacon_node --execution-endpoint http://127.0.0.1:[[8551]] [[--execution-jwt]] XXX [[--checkpoint-sync-url]] XXX | ||
== News == | == News == | ||
| Line 26: | Line 28: | ||
* {{lighthouse bn}} | * {{lighthouse bn}} | ||
* {{lighthouse help}} | * {{lighthouse help}} | ||
| + | * {{lh logs}} | ||
[[Category:Lighthouse]] | [[Category:Lighthouse]] | ||
Latest revision as of 10:20, 31 May 2024
lighthouse beacon_node --execution-endpoint lighthouse beacon_node --staking --execution-endpoint
--execution-endpoint contains an invalid value ParseError(RelativeUrlWithoutBase)
--execution-endpoint Server endpoint for an execution layer jwt authenticated HTTP JSON-RPC connection. Uses the same endpoint to populate the deposit cache. Also enables the --merge flag.If not provided, uses the default value of http://127.0.0.1:8551
Error! Please set either --execution-jwt file_path or --execution-jwt-secret-key directly via cli when using --execution-endpoint
lighthouse beacon_node --execution-endpoint http://127.0.0.1:8551 --execution-jwt XXX --checkpoint-sync-url XXX
News[edit]
- Lighthouse changelog
- Log if no execution endpoint is configured (#3467)
- geth
Related[edit]
See also[edit]
Advertising:
