BTC $79,000.96 -0.88%
ETH $2,481.10 -0.09%
BNB $739.63 -1.05%
XRP $1.39 -1.31%
SOL $103.72 -2.33%
TRX $0.3340 -0.39%
DOGE $0.0900 +0.93%
ADA $0.2207 +0.96%
BCH $266.93 +4.06%
LINK $12.93 +4.71%
HYPE $85.47 -3.19%
AAVE $131.96 -0.92%
SUI $0.8133 +1.52%
XLM $0.1920 +3.98%
ZEC $1,161.45 -1.44%
BTC $79,000.96 -0.88%
ETH $2,481.10 -0.09%
BNB $739.63 -1.05%
XRP $1.39 -1.31%
SOL $103.72 -2.33%
TRX $0.3340 -0.39%
DOGE $0.0900 +0.93%
ADA $0.2207 +0.96%
BCH $266.93 +4.06%
LINK $12.93 +4.71%
HYPE $85.47 -3.19%
AAVE $131.96 -0.92%
SUI $0.8133 +1.52%
XLM $0.1920 +3.98%
ZEC $1,161.45 -1.44%

Ethereum client Prysm: Identified the system issue and provided a temporary solution

2025-12-04 21:07:05

The Ethereum client Prysm has indicated that it has identified the issue and provided a quick temporary solution. All nodes should disable the unnecessary generation of old states in Prysm to handle expired proofs. Simply add the flag "--disable-last-epoch-targets" in the beacon node. This parameter is applicable to version v7.0, so there is no need to further upgrade the beacon node; just add this parameter. The validator client does not require any changes.

app_icon
ChainCatcher Building the Web3 world with innovations.