🚀 Feature
When a validator upgrades, it can currently take 15+ minutes for it to re-participate in consensus, even dropping out occasionally (see the orange line below). Perhaps we can do targeted profiling, or re-architect how this works. A validator switching from block syncing to BFT currently has to process twice the load because it performs both for 100 rounds (the gc limit).
Maybe there's a way to only "kickstart" the certificate syncing once it reached tip-5 blocks via blocksync at least once. We'll have to comprehensively analyse liveness and security for this adjustment.
🚀 Feature
When a validator upgrades, it can currently take 15+ minutes for it to re-participate in consensus, even dropping out occasionally (see the orange line below). Perhaps we can do targeted profiling, or re-architect how this works. A validator switching from block syncing to BFT currently has to process twice the load because it performs both for 100 rounds (the gc limit).
Maybe there's a way to only "kickstart" the certificate syncing once it reached tip-5 blocks via blocksync at least once. We'll have to comprehensively analyse liveness and security for this adjustment.