Gelt Vault V1

The internal function `_getStrategyRedeemFeeBps` contains the following code: ```solidity uint256 redemptionFee = mAsset.data().redemptionFee; require(redemptionFee >= 1e14, "strategy redemption fee must be scaled to 18 decimals"); ``` This assumes that the underlying `mAsset` will never have a fee less than 0.0001. For example, the deployed `mAsset` contract [here](https://polygonscan.com/address/0xe840b73e5287865eec17d250bfb1536704b43b21#readProxyContract) has `redemptionFee = 6e14`. If, for example, `mStable` ever lowered the fee to `6e13`, this would still be "scaled to 18 decimals", but the function `_getStrategyRedeemFeeBps` would revert. This affects critical functions such as `voluntaryExit`.

The function `emergencyExitStrategy` invokes `mAsset.redeem(...)`, using `1` for the `_minOutputQuantity`. If there are issues with the underlying `mAsset` contract, this may cause arbitrarily unfavorable returned quantities of `bAsset` tokens.

The `initialize` function accepts a number of important contract addresses that are permanently assigned to contract members. To avoid costly re-deployments where any of these parameters are accidentally set to `address(0)`, input validation checks should be added.

Public user-facing documentation should detail the actions that can be performed by privileged users. While we don't believe the administrators have unreasonable levels of control, it is especially important to inform users that administrators are able to halt voluntary exits by pausing the contract and thus locking access to the funds.

It is not clear if the `+1` calculation is necessary in the following statement of `_calcStrategyRedeemAmount`: ``` mAssetAmount = mAsset.getRedeemExactBassetsOutput(bAssets, bAssetQuantities) + 1; // Compensate for rounding errors. ``` Note that in the deployed code [here](https://polygonscan.com/address/0xca9cf48ad534f1efa2b0f6923457f2953df86e0b#code) of an `mAsset`, the function `computeRedeemExact` already has a `+1` in the line `grossMasset += 1;` (see L2249).