Difference between revisions of "Beacon client"
Jump to navigation
Jump to search
| Line 8: | Line 8: | ||
WARN Post-merge network, but no [[beacon]] client seen. Please launch one to follow the chain! | WARN Post-merge network, but no [[beacon]] client seen. Please launch one to follow the chain! | ||
| + | |||
| + | * The L1 [[beacon client]] in the [[op-node]] now better detects [[missing blobs]] and falls back to the <code>[[l1.beacon-archiver]]</code> endpoint, if configured | ||
* [[Consensus clients]] | * [[Consensus clients]] | ||
* [[Beacon Chain]] | * [[Beacon Chain]] | ||
* <code>[[lighthouse beacon_node]]</code> | * <code>[[lighthouse beacon_node]]</code> | ||
| + | * <code>[[op-node]]</code> | ||
== See also == | == See also == | ||
* {{Consensus}} | * {{Consensus}} | ||
Revision as of 07:29, 26 July 2024
geth INFO [05-31|12:51:05.069] Consensus: Beacon (proof-of-stake), merged from Ethash (proof-of-work)
geth (no options) WARN Post-merge network, but no beacon client seen. Please launch one to follow the chain!
- The L1 beacon client in the op-node now better detects missing blobs and falls back to the
l1.beacon-archiverendpoint, if configured
See also
Advertising:
