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

Open
c4-bot-6 opened this issue Aug 27, 2024 · 5 comments
Open

QA Report #6

c4-bot-6 opened this issue Aug 27, 2024 · 5 comments
Labels
1st place bug Something isn't working grade-a Q-01 QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax selected for report This submission will be included/highlighted in the audit report

Comments

@c4-bot-6
Copy link
Contributor

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

@c4-bot-6 c4-bot-6 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 Aug 27, 2024
c4-bot-9 added a commit that referenced this issue Aug 27, 2024
c4-bot-6 added a commit that referenced this issue Aug 27, 2024
@Brean0
Copy link

Brean0 commented Aug 29, 2024

QA-01: While the variable is indeed redundant, modifying __self on the UUPSUpgradeable contract would require us to have a custom implementation of the UUPSUpgradeable contract. The Basin Development Community decided this was preferable at the marginal cost of gas.

QA-02: If a Well is properly bored by an Aquifer (and initNoWellToken is called), the minimal proxy cannot call init as the owner is not set. Thus we believe this to be invalid, unless a test POC is provided.

QA-03: Accepted, the docs will be updated to reflect that the Well Function cannot be used for extremely high or low reserves.

QA-04: This is a design choice and is intentional. Developers can choose an A parameter that suites the need of the protocol by deploying a lookup table with the desired A parameter.

QA-05: Accepted, the parameter will be updated so that it's clearer for developers that the implementation should be the minimal proxy deployed by an Aquifer.

@c4-judge
Copy link

c4-judge commented Sep 2, 2024

alex-ppg marked the issue as grade-a

@alex-ppg
Copy link

alex-ppg commented Sep 5, 2024

I would like to note that submission QA-02 is invalid and should not be included in the final QA report.

@thebrittfactor thebrittfactor added the selected for report This submission will be included/highlighted in the audit report label Sep 5, 2024
@C4-Staff C4-Staff added the Q-01 label Sep 5, 2024
@thebrittfactor
Copy link

For awarding purposes, C4 staff have marked as selected for report and 1st place.

@thebrittfactor
Copy link

Just a note that C4 is excluding the invalid entries from the official report.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
1st place bug Something isn't working grade-a Q-01 QA (Quality Assurance) Assets are not at risk. State handling, function incorrect as to spec, issues with clarity, syntax selected for report This submission will be included/highlighted in the audit report
Projects
None yet
Development

No branches or pull requests

6 participants