Prysm node lagging? Fix performance issues with one parameter

[Bitpush] Attention Ethereum node operators! The Prysm client team has recently identified a performance-impacting bug, but the good news is that the fix is very simple.

The issue lies in the generation logic of old states—when processing expired attestations, the system unnecessarily generates historical states, which drags down node efficiency. The team’s temporary solution is super straightforward: just add a parameter to your beacon node startup command.

Here’s what to do: add the --disable-last-epoch-targets flag. If you’re using version v7.0.0, you don’t even need to upgrade—just add this parameter to your existing configuration and restart your node. No changes are needed on the validator client side.

This is a pretty practical optimization patch, so if you’re running Prysm, add it as soon as possible. In theory, it can significantly improve your node’s response speed.