Question Regarding Stake Locking in Lookahead Updates

[swarna1101]

In the forcePushLookahead function, which handles cases where lookahead lags due to missed proposals, the stake of the sender is locked for the dispute window:

preconfServiceManager.lockStakeUntil(msg.sender, block.timestamp + PreconfConstants.DISPUTE_PERIOD);

Could there be a case where an unexpected number of lookahead lags or force pushes impacts certain preconfers by repeatedly locking their stakes? If so, locking with a weighted lock duration based on lookahead health should reduce the likelihood of penalizing participants for frequent calls to forcePushLookahead?

[AnshuJalan]

The stake lock logic is very provisional at the moment, and will likely be very different when Eigenlayer and/or unified staking registry is finalised. If you see my comment here (#19 (comment)), we will potentially not have any kind of stake locking. It will simply be a "withdrawal delay" at the registry level.