Bribe.sol is not meant to handle fee-on-transfer tokens

USDT is not supported because of approval mechanism

Inconsistent Order Book Accounting When Working With Transfer-On-Fee or Deflationary Tokens

Use `safeTransfer()`/`safeTransferFrom()` instead of `transfer()`/`transferFrom()`

`RubiconMarket.sol#isClosed()` always returns false, making the market can not be stopped as designed

The check for value transfer success is made after the return statement in _withdrawFromYieldPool of LidoVault

Possible lost msg.value

Users may lose rewards to other users if rewards are given as fee-on-transfer tokens

Vault is Not Compatible with Fee Tokens and Vaults with Such Tokens Could Be Exploited

safeTransferFrom is recommended instead of transfer (1)

amount requires to be updated to contract balance increase (1)

IERC20.transfer does not support all ERC20 token

_depositAmount requires to be updated to contract balance increase

Non-standard ERC20 Tokens are Not Supported

`call()` should be used instead of `transfer()` on an `address payable`

Funding.deposit() doesn't work if there is no discount set