InterchainProposalExecutor.sol doesn't support non-evm address as caller or sender

`RemoteAddressValidator` can incorrectly convert addresses to lower case

Users can end up buying and paying for a different Tray than the one they were trying to acquire

Liquidity providers may lose funds when adding liquidity

`LPDA` price can underflow the price due to bad settings and potentially brick the contract

selfdestruct() will not be available after EIP-4758

NFTs mintable after Auction deadline expires

When a smart contract calls CrossChainRelayerArbitrum.processCalls, excess submission fees may be lost

Reward can be over- or undercounted in `extendPledge` and `increasePledgeRewardPerVote`

Pledge may be out of reward due to the decay in veCRV balance. targetVotes is never reached.

Oracle assumes token and feed decimals will be limited to 18 decimals

Chainlink oracle data feed is not sufficiently validated and can return stale `price`

Failed job can't be recovered. NFT may be lost.

Gas price spikes cause the selected operator to be vulnerable to frontrunning and be slashed

Bond tokens (HLG) can get permanently stuck in operator

liquidExit may have an unexpected exit penalty if TrueFi adjusts the penalty or some human error

Missing slippage control system. Users may lose a lot of funds due to front-running MEV bots.

Centralization risk: admin have privileges: admin can set address to mint any amount of frxETH, can set any address as validator, and change important state in frxETHMinter and withdraw fund from frcETHMinter

Rewards delay release could cause yields steal and loss

removeValidator() and removeMinter() may fail due to exceeding gas limit

frxETHMinter: Non-conforming ERC20 tokens not recoverable

`recoverEther` not updating `currentWithheldETH` breaks calculation of withheld amount for further deposits

not able to create claim

Using ERC721 unsafe transferFrom will cause some NFT loss if the recipient can't accept ERC721 and won't execute onERC721Received in the recipient contract.

It is possible that receiver and treasury can receive nothing when calling `withdraw` function due to division being performed before multiplication

Different Oracle issues can return outdated prices

Unexpected behavior for UniV2Adapter, UniV3Adapter, and ZeroExAdapter when msgValue is not zero

TradingModule oracle is missing check for stale price in roundID

Hackers can deploy token with respective name as the stable one to impersonate the stable token

Multiple vote checkpoints per block will lead to incorrect vote accounting

A proposal can be cancelled by anyone if the proposal has exactly proposalThreshold votes

`Governor` - Quorum could be less than intended

Delegation should not be allowed to address(0)

Precision is not enough for proposalThreshold and quorum. Collections with at least 20000 NFTs in total supply may have some trouble.

Proposals can be bricked and Auctions stalled by bad settings

Loss of Veto Power can Lead to 51% Attack

If an asset is blocked from the transfer, using that asset as collateral will prevent liquidation

Chainlink’s `latestRoundData` might return stale or incorrect results

Possible to bypass saleConfig.limitPerAccount

Possible DOS in `lendToProject()` and `toggleLendingNeeded()` function because unbounded loop can run out of gas

XC20Wrapper may lost received token forever if LocalAsset(xc20).mint is reverted indefinitely

System will not work anymore after EIP-4758

Delegate call in `Vault#_execute` can alter Vault's ownership

ORACLE DATA FEED CAN BE OUTDATED YET USED ANYWAYS WHICH WILL IMPACT ON PAYMENT LOGIC

Use a safe transfer helper library for ERC20 transfers

Oracle periodSize is very low allowing the TWAP price to be easily manipulated

getBorrowRate returns rate per year instead of per block

Cannot mint to exactly max supply using `_mint` function

Allowance check always true in ERC5095 redeem

Incorrect implementation of APWine and Tempus `redeem`

Able to mint any amount of PT

Funds may be stuck when `redeeming` for Illuminate

Illuminate PT redeeming allows for burning from other accounts

`_harvest` has no slippage protection when swapping `auraBAL` for `AURA`

`lending-market/NoteInterest.sol` Wrong implementation of `getBorrowRate()`

Anyone can set the `baseRatePerYear` after the `updateFrequency` has passed

Oracle may be attacked if an attacker can pump the tokens for the entire block

_handleExecuteTransaction may not working correctly on fee-on-transfer tokens. Moreover, if it is failed, fund may be locked forever.

Current implementation of arbitrary call execute failure handler may break some use case for example NFT bridge.

WeVE (FTM) may be lost forever if redemption process is failed

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

Reward may be locked forever if user doesn't claim reward for a very long time such that too many epochs have been passed

Cross-chain smart contract calls can revert but source chain tokens remain burnt and are not refunded