Difference between revisions of "Lighthouse beacon node --execution-jwt"
Jump to navigation
Jump to search
↑ https://github.com/sigp/lighthouse/blob/stable/book/src/merge-migration.md#connecting-to-an-execution-engine
| Line 15: | Line 15: | ||
* INFO [07-12|11:50:10.104] [[Loaded JWT secret file path]]=/Users/user/Library/Ethereum/geth/jwtsecret crc32=0x743c3389 | * INFO [07-12|11:50:10.104] [[Loaded JWT secret file path]]=/Users/user/Library/Ethereum/geth/jwtsecret crc32=0x743c3389 | ||
* [[Beacon node]] | * [[Beacon node]] | ||
| − | * [[geth]] | + | * [[geth]]: <code>[[~/Library/Ethereum/geth/jwtsecret]]</code> |
== See also == | == See also == | ||
Revision as of 10:17, 31 May 2024
--execution-endpoint [1]
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
Related
lighthouse beacon node --execution-endpoint- JWT
- INFO [07-12|11:50:10.104] Loaded JWT secret file path=/Users/user/Library/Ethereum/geth/jwtsecret crc32=0x743c3389
- Beacon node
- geth:
~/Library/Ethereum/geth/jwtsecret
See also
lighthouse beacon_node, --execution-endpoint, --execution-jwt, --allow-insecure-genesis-sync, logs,--checkpoint-sync-url, --help, checkpoint sync,beacon.log- JWT,
openssl rand, Bearer token, HMAC,JWT_SECRET_KEY, JWT signatures, HS256, RS256
Advertising:
