Order of parameters in KickReward event

[code423n4]

Handle

pauliax

Vulnerability details

Impact

event KickReward in CvxLocker declares the first parameter as _user and second as _kicked, however, seems that these parameters are actually emitted in the opposite order:
emit KickReward(_rewardAddress, _account, reward);

Recommended Mitigation Steps

I think it should be this:
emit KickReward(_account, _rewardAddress, reward);

[C2tP-C2tP]

Ah yeah i can see how that could be taken either way. should have done _kicker and _kickee maybe to be more clear.