According to @ parithosh_j's response, this issue was caused by some execution layer (EL) clients making errors in configuring deposit contract addresses, especially not correctly adapting to the specific address of the Holesky test network, resulting in most validators incorrectly proving an invalid chain, disrupting the network's consensus mechanism, and ultimately failing to reach finality. However, this issue is limited to the Holesky testing network. For the subsequent handling of Holesky, it is currently recommended that developers update to a bug fixed client version and resynchronize the execution layer (EL) and consensus layer (CL) nodes. If the user has a validator's slash database (to prevent double signing), it needs to be deleted to avoid further issues. The goal is to restore the Holesky network from chaos and achieve finality, which requires cooperation between the community and developers. More detailed solutions will be discussed at the ACD (All Core Devs) conference in the future.