Beacon client

geth
INFO [05-31|12:51:05.069] Consensus: Beacon (proof-of-stake), merged from Ethash (proof-of-work)

WARN Post-merge network, but no beacon client seen. Please launch one to follow the chain!

geth (no options) 
geth --authrpc.addr localhost --authrpc.port 8551 --authrpc.vhosts localhost

• The L1 beacon client in the op-node now better detects missing blobs and falls back to the l1.beacon-archiver endpoint, if configured

• Consensus clients
• Beacon Chain
• lighthouse beacon_node
• prysm.sh beacon-chain
• op-node

See also

• Beacon Chain, Ethereum Beacon Chain, Ropsten Beacon Chain, Bellatrix beacon chain, The Merge, BeaconChainRpcEndpoints, lighthouse beacon_node, 5052, prysm.sh beacon-chain --deposit-contract, Beacon client
• Consensus, Proof of Stake (PoS), Consensus clients, Execution clients, Prysm, Lighthouse, Lodestar, Teku, Nimbus, Consensus Layer (CL), Beacon client