Incompatibility with deflationary / fee-on-transfer tokens

If a winner is blacklisted on any of the tokens they can't receive their funds

Lack of checking the existence of the Proxy contract

Centralization Risk for trusted organizers

Sandwich attack to steal all ERC-20 tokens in the Fees contract

Fee on transfer tokens will cause users to lose funds

`Lender` does not handle correctly rebasing, inflationary, deflationary tokens and tokens with fee on transfer

Zero address leads to transaction reverts

Multiple accesses of a mapping/array should use a local variable cache.

Modifier gas optimization for onlyOwner modifier

NatSpec documentation for function is missing

Floating pragma in all contracts

Conformance to Solidity naming conventions

Multiple `address` mappings can be combined into a single mapping of an `address` to a `struct`, where appropriate

[G-01] - Do not add the data which is alreday included in the tx to save users gas cost.

Incorrect Event Emmiting

Function ordering does not follow the Solidity style guide

Custom Errors naming

[I-02] - Unnecessary Inheritance.

Use named imports instead of plain `import file.sol

Liquidation Is Prevented Due To Strict Implementation of Liqudation Bonus

DSC protocol can consume stale price data or cannot operate on some EVM chains

Chainlink oracle will return the wrong price if the aggregator hits `minAnswer`

All of the USD pair price feeds doesn't have 8 decimals

Too many DSC tokens can get minted for fee-on-transfer tokens.

Zero address check for tokens

Pragma isn't specified correctly which can lead to nonfunction/damaged contract when deployed on Arbitrum

Precision loss when calculating the health factor

[G-01] - Use `do-while` loop instead of `for-loop` to save users gas cost.

Prefer array assignment over pushing elements in for-loops

[I-01] - Use `Natspec` comments for smart contracts, interfaces and libraries.