Unnecessary cycle timing restriction on redemptions leads to unfair user experience

The redeemPixels() function incorrectly applies the onlyDuringCycle modifier, which prevents users from redeeming their winning pixels during the 1-hour downtime period before each draw. This restriction serves no technical security purpose since redemptions operate entirely on historical data from previous completed draws, not current cycle state.

The onlyDuringCycle modifier is designed to prevent new pixel purchases during the final hour before a draw to maintain cycle integrity. However, applying this same restriction to redemptions creates artificial barriers for legitimate winners.

The redemption process validates pixel ownership against previousDrawTime and utilizes finalized results from completed draws, ensuring it is entirely independent of current cycle timing.

Unfair user experience where legitimate winners are artificially prevented from claiming rewards, creating opportunities for economic manipulation where informed users redeem early while uninformed users face lockout periods.

Remove Unnecessary Modifier: Remove the onlyDuringCycle modifier from the redeemPixels() function:

function redeemPixels(uint32[] calldata _pixels) external nonReentrant {
    // Remove onlyDuringCycle modifier - redemptions use historical data only
    uint32 length = uint32(_pixels.length);
    // ... rest of function remains unchanged
}

Golden Grid: Confirmed.

Zealynx: Fixed. Asked for clarification on the solution implemented since it differed from the proposed one, and agreed to the reasoning for it.