Description

In commitMove, a player can still call the function even when both players have already committed their moves. For example:

This allows players to waste gas by calling the function when no valid action will be taken, especially if they've already submitted a commit and there's no check preventing further calls.

Impact

• Unnecessary gas consumption

• Potential for spam transactions with no effect

• Increased operational cost without value

Recommended Mitigation:

Add early require checks to ensure a player cannot commit again once they've already submitted a move for the current turn.