BTC $63,003.41 +0.08%
ETH $1,880.68 +0.01%
BNB $606.98 -0.01%
XRP $1.00 +0.27%
SOL $75.31 +0.01%
TRX $0.3309 -0.34%
DOGE $0.0695 -0.57%
ADA $0.1766 -1.74%
BCH $203.13 -0.84%
LINK $9.42 +4.43%
HYPE $56.77 +0.66%
AAVE $86.15 -0.19%
SUI $0.6763 -1.03%
XLM $0.1576 -0.12%
ZEC $486.83 -1.62%
BTC $63,003.41 +0.08%
ETH $1,880.68 +0.01%
BNB $606.98 -0.01%
XRP $1.00 +0.27%
SOL $75.31 +0.01%
TRX $0.3309 -0.34%
DOGE $0.0695 -0.57%
ADA $0.1766 -1.74%
BCH $203.13 -0.84%
LINK $9.42 +4.43%
HYPE $56.77 +0.66%
AAVE $86.15 -0.19%
SUI $0.6763 -1.03%
XLM $0.1576 -0.12%
ZEC $486.83 -1.62%

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.