The pool managers fee validation logic incorrectly requires the full token factory fee to be paid in a single accepted denomination, even when the user provides the equivalent total amount split across multiple accepted denoms.
In order to validate that fees are paid correctly for the transactions, we use validate_fees_are_paid().
Now in the case where the pool fee denom is one of the token factory fee denoms BUT there are multiple token factory fee options, we get into this window:
/contracts/pool-manager/src/helpers.rs#L575-L597
The issue is that the code uses .any() to check if ANY SINGLE denomination matches the full required fee amount. This means that even if a user provides the equivalent value split across multiple accepted denoms, the validation will fail.
For example, if the required fee is 100 tokens and there are 5 accepted denoms:
This happens even though the user has provided the full required fee value, just split across different denoms, which is counterintuitive to the intended implementation.
Broken implementation of the validation logic, considering that users are forced to pay the entire fee in a single denomination even when they have sufficient funds split across multiple accepted denoms
Modify the validation to accept cumulative payments across accepted denoms.
