Current implementation doesn't take into account how much tokens were sent to pool back, which is okay for current underlying tokens. However, if someone will decide a pool with fee token (for example USDT), it could be a problem, because pool will get less money amountToPool * (1 -fee).
Suggestion: add functionality to CreditManager to be able to work with fee tokens.
Current implementation doesn't take into account how much tokens were sent to pool back, which is okay for current underlying tokens. However, if someone will decide a pool with fee token (for example USDT), it could be a problem, because pool will get less money amountToPool * (1 -fee).
Suggestion: add functionality to CreditManager to be able to work with fee tokens.