We have produced a forked/orfan block:
https://beaconcha.in/slot/5770016
Validator: 338395
Slot: 5770016
Epoch: 180313
We have a 3-layer configuration with the validator client, the Beacon node and the execution client running separately.
We are using Mev-boost.
The setup is working well before and after the orfand block produced. So the problem is related to something "casual"
node07 | Feb 10 16:30:36.495 INFO Successfully published block slot: 5768551, graffiti: Some("Block by Stakely Lido07"), attestations: 97, deposits: 0, block_type: Blinded, service: block
node07 | Feb 10 19:14:48.068 INFO Successfully published block slot: 5769372, graffiti: Some("Block by Stakely Lido07"), attestations: 128, deposits: 0, block_type: Blinded, service: block
node07 | Feb 10 19:20:35.990 INFO Successfully published block slot: 5769401, graffiti: Some("Block by Stakely Lido07"), attestations: 77, deposits: 0, block_type: Blinded, service: block
node07 | Feb 10 21:23:41.061 INFO Successfully published block slot: 5770016, graffiti: Some("Block by Stakely Lido07"), attestations: 74, deposits: 0, block_type: Blinded, service: block
node07 | Feb 10 22:49:00.007 INFO Successfully published block slot: 5770443, graffiti: Some("Block by Stakely Lido07"), attestations: 105, deposits: 0, block_type: Blinded, service: block
node07 | Feb 11 00:23:35.871 INFO Successfully published block slot: 5770916, graffiti: Some("Block by Stakely Lido07"), attestations: 99, deposits: 0, block_type: Blinded, service: block
Validator setup and version: Lighthouse/v3.4.0-38514c0
lighthouse vc
--beacon-nodes http://LH,http://SERVER_ON_MAINTENANCE,http://ip3
--network mainnet
--metrics
--metrics-allow-origin *
--graffiti "Block by xxxxxxx"
--suggested-fee-recipient 0x388Cxxxxxxxxxxxx
--init-slashing-protection
--metrics-port xxx
--http
--builder-proposals
Beacon setup and version: Lighthouse/v3.4.0-38514c0
lighthouse beacon
--network mainnet
--execution-jwt /xxxxxxxxxxxxxxx
--execution-endpoint http://localhost:xxxxx
--subscribe-all-subnets
--import-all-attestations
--graffiti "Block by Stakely.io - blh01"
--metrics
--metrics-allow-origin xxxxx
--http
--http-address xxxxxxxx
--http-port xxxxx
--port xxxxxxx
--checkpoint-sync-url https://mainnet-checkpoint-sync.stakely.io/
--suggested-fee-recipient 0xxxxxxxxxx
--builder http://xxxxxxx
Execution setup and version: Geth/v1.10.26-stable-e5eb32ac/linux-amd64/go1.18.8
--mainnet
--syncmode=snap
--http
--http.api "eth,net,web3,engine,admin"
--http.corsdomain "*"
--http.addr 127.0.0.1
--http.port xxxx
--cache 16384
--port xxxx
--authrpc.port xxx
--authrpc.jwtsecret "xxxxxx"
--authrpc.vhosts "xxxx"
Lighhouse Beacon logs are relevant because the first lines show the BN loses several seconds because a new block received changes the parent root of the Prepared beacon proposer for slot 5770016.
lh-bn-orfandblock10022023.txt
mev-boost-orfandblock10022023.txt
Important note: VC is connected to several BNs, one of the then is shut down because it is currently undergoing maintenance.This doesnt affect this problem but you'll see warnings in VC logs.
lh-vc-orfandblock10022023.txt
We have produced a forked/orfan block:
https://beaconcha.in/slot/5770016
Validator: 338395
Slot: 5770016
Epoch: 180313
We have a 3-layer configuration with the validator client, the Beacon node and the execution client running separately.
We are using Mev-boost.
The setup is working well before and after the orfand block produced. So the problem is related to something "casual"
Validator setup and version: Lighthouse/v3.4.0-38514c0
Beacon setup and version: Lighthouse/v3.4.0-38514c0
Execution setup and version: Geth/v1.10.26-stable-e5eb32ac/linux-amd64/go1.18.8
Lighhouse Beacon logs are relevant because the first lines show the BN loses several seconds because a new block received changes the parent root of the Prepared beacon proposer for slot 5770016.
lh-bn-orfandblock10022023.txt
mev-boost-orfandblock10022023.txt
Important note: VC is connected to several BNs, one of the then is shut down because it is currently undergoing maintenance.This doesnt affect this problem but you'll see warnings in VC logs.
lh-vc-orfandblock10022023.txt