As shown by the following comparisons between the options maturity and the block timestamp in the following TimeswapV2Pool.initialize function and the pools various ParamLibrary.check functions, the pool considers the corresponding option not matured when its maturity and the block timestamp are equal. However, this is inconsistent with the options definition, which considers the option matured when its maturity and the block timestamp are equal as the options various ParamLibrary.check functions below show. The TimeswapV2Pool contracts mint, burn, deleverage, leverage, and rebalance functions all have the can be only called before the maturity comment indicating that these functions are supposed to be callable only when the corresponding option is not matured. Users who checked these comments can believe that these functions are callable when the options maturity and the block timestamp are equal; yet, calling these functions at such timing will revert due to the duration to the options maturity is already 0 and the inconsistency between the pool and options definitions of whether the option is matured. As a result, in this case, the users calls of these TimeswapV2Pool contracts functions will revert unexpectedly with the used gas being wasted, and the user experience becoming degraded.
As a mitigation, the pool and options definitions of whether the option is matured need to be updated to be consistent.
https://github.com/code-423n4/2023-01-timeswap/blob/main/packages/v2-pool/src/TimeswapV2Pool.sol#L175-L181
https://github.com/code-423n4/2023-01-timeswap/blob/main/packages/v2-pool/src/structs/Param.sol#L142-L194
https://github.com/code-423n4/2023-01-timeswap/blob/main/packages/v2-option/src/structs/Param.sol#L103-L151
