Scan to download
BTC $71,139.41 -4.27%
ETH $2,193.34 -5.80%
BNB $651.53 -2.92%
XRP $1.42 -4.56%
SOL $81.67 -4.53%
TRX $0.2795 -0.47%
DOGE $0.0974 -3.83%
ADA $0.2735 -4.22%
BCH $455.26 -3.86%
LINK $8.64 -2.97%
HYPE $28.98 -1.81%
AAVE $122.61 -3.42%
SUI $0.9851 -4.98%
XLM $0.1605 -4.62%
ZEC $260.31 -8.86%
BTC $71,139.41 -4.27%
ETH $2,193.34 -5.80%
BNB $651.53 -2.92%
XRP $1.42 -4.56%
SOL $81.67 -4.53%
TRX $0.2795 -0.47%
DOGE $0.0974 -3.83%
ADA $0.2735 -4.22%
BCH $455.26 -3.86%
LINK $8.64 -2.97%
HYPE $28.98 -1.81%
AAVE $122.61 -3.42%
SUI $0.9851 -4.98%
XLM $0.1605 -4.62%
ZEC $260.31 -8.86%

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

2025-12-04 21:07:05
Collection

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.