BTC $79,001.64 -0.87%
ETH $2,480.12 -0.17%
BNB $739.35 -1.10%
XRP $1.39 -1.39%
SOL $103.77 -2.39%
TRX $0.3340 -0.33%
DOGE $0.0900 +0.92%
ADA $0.2207 +0.80%
BCH $267.50 +4.22%
LINK $12.92 +4.63%
HYPE $85.60 -2.83%
AAVE $132.19 -0.94%
SUI $0.8133 +1.57%
XLM $0.1925 +4.18%
ZEC $1,158.07 -1.76%
BTC $79,001.64 -0.87%
ETH $2,480.12 -0.17%
BNB $739.35 -1.10%
XRP $1.39 -1.39%
SOL $103.77 -2.39%
TRX $0.3340 -0.33%
DOGE $0.0900 +0.92%
ADA $0.2207 +0.80%
BCH $267.50 +4.22%
LINK $12.92 +4.63%
HYPE $85.60 -2.83%
AAVE $132.19 -0.94%
SUI $0.8133 +1.57%
XLM $0.1925 +4.18%
ZEC $1,158.07 -1.76%

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.