Submitted by Chom, also found by Lambda and Trust
HolographOperator.sol#L354
Since you have designed a mechanism to prevent other operators to slash the operator due to the selected missed the time slot due to a gas spike. It can induce that operators wont perform their job if a gas price spike happens due to negative profit.
But your designed mechanism has a vulnerability. Other operators can submit their transaction to the mempool and queue it using gasPrice in bridgeInRequestPayload. It may get executed before the selected operator as the selected operator is waiting for the gas price to drop but doesnt submit any transaction yet. If it doesnt, these operators lose a little gas fee. But a slashed reward may be greater than the risk of losing a little gas fee.
Once 1 epoch has passed, selected operator is vulnerable to slashing and frontrunning.
Modify your operator node software to queue transactions immediately with gasPrice in bridgeInRequestPayload if a gas price spike happened. Or allow gas fee loss tradeoff to prevent being slashed.
alexanderattar (Holograph) confirmed and commented:
gzeon (judge) increased severity to High and commented:
