Uncheck Arithmetic where overflow/underflow impossible

Use of magic numbers

Named parameter mappings

Use assembly to check for `address(0)`

Don't use draft versions in production

Large multiples of ten should use scientific notation

Use if + custom errors instead of using require + string

Mixed usage of `int`/`uint` with `int256`/`uint256`

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

All interfaces must be in one folder

Test Coverage Improvements

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

`++i`/`i++` should be `unchecked{++i}`/`unchecked{i++}` when it is not possible for them to overflow, as is the case when used in `for`- and `while`-loops

The nonReentrant modifier should occur before all other modifiers

Use `assembly` to check for `address(0)`

Use assembly to check for `address(0)`

The `nonReentrant` `modifier` should occur before all other modifiers

Use safeTransferFrom() instead of transferFrom()