`addLiquidity()` function is called with lack of working deadline and slippage protection

Claimable gauge distributions are lost when `killGaugeTotally` is called

curator can lead to DOS `purchase()` function

the `woPrice_` bound check will ignored if Chainlink returns zero price

DoS in `MergingPool::claimRewards` function and potential DoS in `RankedBattle::claimNRN` function if called after a significant amount of rounds passed.

Unauthorized Access to setCurves Function

getVestedFraction missed to check If Arbitrum sequencer is down

getGasPrice() doesn't check Arbitrum l2 chainlink feed is active

The deposit - withdraw - trade transaction lack of expiration timestamp check (DeadLine check)

Using unsafe ERC20 methods can revert the transaction for some tokens.

getPrice() function doesn't check If Arbitrum sequencer is down in Chainlink feeds.

There is no slippage control for trading functions at all

_validateAndGetPrice() doesn't check If Arbitrum sequencer is down in Chainlink feeds

Oracle data feed has no check for round fullness

wrong calculation in logic of the Lend function

in cooler.sol.rescind there is risk of funds to be lost

if transfer fails in repaying loan will be deleted

`_handleDeposit` and `_handleWithdraw` do not account for tokens with decimals higher than 18

contract should check the responses from chainlink aggregator

Use of `payable.transfer()` may lock user funds