Submitted by GreyArt
A user that mistakenly calls either create() or addToken() with WETH (or another ERC20) as the input token, but includes native ETH with the function call will have his native ETH permanently locked in the contract.
It is best to ensure that msg.value = 0 in _transferInputTokens() for the scenario mentioned above.
adrien-supizet (Nested) confirmed
