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 #221

Open
code423n4 opened this issue Feb 3, 2023 · 3 comments
Open

QA Report #221

code423n4 opened this issue Feb 3, 2023 · 3 comments
Labels
bug Something isn't working grade-b Q-09 QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax

Comments

@code423n4
Copy link
Contributor

See the markdown file with the details of this report here.

@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 Feb 3, 2023
code423n4 added a commit that referenced this issue Feb 3, 2023
code423n4 added a commit that referenced this issue Feb 3, 2023
@GalloDaSballo
Copy link

GalloDaSballo commented Feb 14, 2023

NC00 driverId offset is hardcoded in the driver contracts
R

NC01 Wrong and confusing naming of variable in AddressDriver.t.sol
Disputing due to test file

NC02 Unit tests are missing comments
Saem

L01 Incomplete/missing NatSpec tags in function comments
NC

L02 Extensive usage of slither-disable, posing a risk, and also causing source code deterioration
Disputing in lack of specific example

L03 DOS condition when registering type(uint32).max number of drivers
R, don't think it's a realistic risk

L04 Wrong and misleading comment in DripsHub.sol
R

L05 DOS condition when adding max amount of tokens to drips balance
L

L06 Wrong and misleading comment, plus possible risk for future code changes
NC

L07 Bad english in comment in DripsHub.sol, can be misleading
NC

L08 Certain ERC20 tokens like UNI and COMP are not compatible with the AddressDriver contract
L

L09 Wrong parameter name used for NatSpec tag in function comment
NC

L10 Wrong NatSpec tag used in function comment
NC

@GalloDaSballo
Copy link

2L 3R 5NC

@c4-judge
Copy link
Contributor

GalloDaSballo marked the issue as grade-b

@C4-Staff C4-Staff added the Q-09 label Mar 2, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working grade-b Q-09 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

4 participants