BTC $71,776.58 +11.38%
ETH $2,277.75 +18.52%
BNB $641.91 +6.52%
XRP $1.19 +18.35%
SOL $86.88 +12.17%
TRX $0.3373 +1.51%
DOGE $0.0767 +9.40%
ADA $0.1918 +9.78%
BCH $215.43 +5.73%
LINK $10.57 +8.58%
HYPE $71.30 +21.33%
AAVE $97.13 +8.82%
SUI $0.7214 +9.99%
XLM $0.1816 +15.62%
ZEC $564.07 +11.14%
BTC $71,776.58 +11.38%
ETH $2,277.75 +18.52%
BNB $641.91 +6.52%
XRP $1.19 +18.35%
SOL $86.88 +12.17%
TRX $0.3373 +1.51%
DOGE $0.0767 +9.40%
ADA $0.1918 +9.78%
BCH $215.43 +5.73%
LINK $10.57 +8.58%
HYPE $71.30 +21.33%
AAVE $97.13 +8.82%
SUI $0.7214 +9.99%
XLM $0.1816 +15.62%
ZEC $564.07 +11.14%

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.