BTC $62,586.42 -1.84%
ETH $1,865.76 -1.33%
BNB $603.51 -1.13%
XRP $1.00 -0.51%
SOL $75.19 -1.45%
TRX $0.3322 -0.64%
DOGE $0.0693 -1.15%
ADA $0.1791 -2.95%
BCH $202.05 -5.32%
LINK $8.82 +0.06%
HYPE $55.78 -3.59%
AAVE $85.52 -2.62%
SUI $0.6758 -2.19%
XLM $0.1596 -0.63%
ZEC $482.11 -1.66%
BTC $62,586.42 -1.84%
ETH $1,865.76 -1.33%
BNB $603.51 -1.13%
XRP $1.00 -0.51%
SOL $75.19 -1.45%
TRX $0.3322 -0.64%
DOGE $0.0693 -1.15%
ADA $0.1791 -2.95%
BCH $202.05 -5.32%
LINK $8.82 +0.06%
HYPE $55.78 -3.59%
AAVE $85.52 -2.62%
SUI $0.6758 -2.19%
XLM $0.1596 -0.63%
ZEC $482.11 -1.66%

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.