Closed ThanhNhann closed 1 year ago
Yes. MustRefundWager
exists and should cover all situations, regardless of how it is being used.
The fix I see is that EndBlocker
does not need to make the extra check for == 1
because == 0
is a valid situation.
I will include that in a future revision of the code.
I see that
MustRefundWager
function checks three conditions withMoveCount
but when we use it atEndBlocker
, it just checks the caseMoveCount == 1
and then callsMustRefundWager
here, so it will always point in one case inMustRefundWager
function and will never go to another cases likeMoveCount == 0