Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

QA Report #292

Open
code423n4 opened this issue May 14, 2022 · 0 comments
Open

QA Report #292

code423n4 opened this issue May 14, 2022 · 0 comments
Labels
bug Something isn't working QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax

Comments

@code423n4
Copy link
Contributor

QA Report

Remarks/Recommendations

  • the test suite was a joy to work with. I learned a lot about Foundry and will use it on my own projects.
  • the documentation was of a very high quality

Low Risk: Don't allow setVaultBeneficiary to be set to address(0)

Yes, getVaultBeneficiary will check for address(0) and return ownerOf[vaultId] but relying on this is a bit dangerous if you change the code in future.

Non-critical: Incorrect error message on check for reserve strike price

There is an incorrect error message in the require at location Cally.sol:169.

It should be:

require(dutchAuctionReserveStrike < strikeOptions[dutchAuctionStartingStrikeIndex], "Reserve strike too large");

In general the error message should always express the opposite of the condition of the require statement.

Non-critical: Several requires with == false in them

The locations are

It is better to use the ! (not) operator. e.g.

require(!vault.isExercised, "Vault already exercised");
@code423n4 code423n4 added bug Something isn't working QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax labels May 14, 2022
code423n4 added a commit that referenced this issue May 14, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax
Projects
None yet
Development

No branches or pull requests

1 participant