QA Report

[code423n4]

. Bad coding practices:

• One file per class or one file per contract, is always a good practice that facilitates readability and auditability. example: BentoBoxFlat

2. Lack of input checks:
   • asset not checked at NFTPair.sol#L177
   • asset not checked at NFTPairWithOracle.sol#L194

[cryptolyndon]

• The BentoBox is not only out of scope, it is not part of the project. That file serves as a reference only, and as a base for the mock BentoBox we use for testing.
• The zero check on collateral is not to somehow check that parameter; it is to ensure init() cannot be called twice.