Proposed a block with a null fee recipient

The upgrade of Geth node, without an appropriate resync from scratch, along with wrong PK into my Mev’s config, may have been caused the production of the block 22514318 with a null fee recipient unlike the previous blocks proposed by the same node.
Now I restarted the db from scratch, while the configurations have been checked in depth and everything is running smoothly.

2 Likes

Thank you for reporting @blockside

As this was caused by client related issues, which the operator has been very responsive in addressing (including reimbursing the protocol), as a member of the CSM committee, I recommend that no additional penalty should be applied.

2 Likes

Following-up on this, I can now confirm that the CSM committee has reviewed the situation and agreed that no additional penalty will be applied. Thank you!

For reference, committee info: Community Staking Module Committee

1 Like