PANews reported on January 23 that in response to the previous Nethermind execution client problem, Figment, a staking infrastructure service platform, said on its official website that Figment does not run Nethermind as an execution client, but runs Geth as its main execution client. Nethermind's vulnerability has led some to question what would happen if the same problem appeared on most clients like Geth. In this case, any validator connected to Geth may not be able to verify and Ethereum will enter an inactive leak state; these penalties are small but increase over time. If Geth encounters a similar error, Figment is able to switch execution clients within a few hours, and if the losses associated with such events result in negative days of gains, i.e. the penalties imposed are greater than the rewards earned, Figment will pay those losses (Figment will pay up to 6 months of negative days of earnings earnings).
It is reported that on January 21, the execution client Nethermind began to encounter some problems in the Block19056922. Nethermind versions 1.23 to 1.25 seem to start rejecting invalid blocks. Between the 257,908 and 257,923 periods inclusive, the participation rate is less than 95%, which is about 2 hours). Previously, yesterday's news, Nethermindv released experimental version v1.26.0-exp.2 to fix the Consensus issue introduced in v1.23.0.