Liquidations will be significantly delayed due to incorrect maths

Wrong variable usage upon withdrawing, resulting in unexpected results

Multi-hop swaps are not properly supported, the code will run OOG

Tick spacing of 1 does not work properly

Setting the secondary position will cause unexpected results

Funds to be withdrawn can be stolen due to incorrect variable usage

Posting results can be blocked in `SedaCoreV1` due to using the push pattern

Creating a vesting account can be perpetually disallowed

Wrong amount of gas will be used in a certain case

Debasing/rebasing periods can be decreased by 50% by a malicious actor

Lenders blacklisted for USDC can disallow borrowers from repaying

`acceptLoanOfferAndFillOrder()` will result in a lower fee for the protocol

Shares of a user will be wrong after a liquidation

Wrong interest rate after a liquidation

`getSupplyBalance()` and `getDebtBalance()` return wrong values

Interest rate will be wrong after a repay

Liquidations will be executed with wrong values

Withdrawals might be DoS in certain cases and funds can get stuck

Repayments using the NFT position manager will revert in a lot of cases

Using a hardcoded value for the Chainlink stale price check is dangerous

Not including Chainlink decimals upon calculations will lead to accounting issues

Users can increase their rewards and dilute rewards for other users

Funds will always be stuck in a pool and unexpected reverts will occur upon reallocations

The `Pool` contract can be DoSed

`Superpool` contract doesn't strictly follow EIP4626

Superpool can not be paused despite the implemented functionality

Not removing a token from the position assets upon an owner removing a token from the known assets will cause huge issues

Liquidations will revert if a position has been blacklisted for USDC

Reallocations will often fail upon using USDT

The Redstone oracle can report stale prices

Partial liquidations are next to impossible to happen despite the code being supposed to allow them