mirror of
https://github.com/ethereum/consensus-specs.git
synced 2026-02-01 13:44:57 -05:00
dd65aa0cb2
When new finality is reached without supermajority sync committee support, trigger another event push on beacon-API and libp2p once the new finality gains supermajority support. Without this, if the first `LightClientFinalityUpdate` that advances finality has low participation, light clients monitoring gossip would likely get stuck until the next time when finality advances (1 epoch). Thanks to @DragonDev1906 for reporting this issue to Nimbus: - https://github.com/status-im/nimbus-eth2/issues/5491