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

Open
c4-bot-5 opened this issue Mar 12, 2024 · 9 comments
Open

QA Report #128

c4-bot-5 opened this issue Mar 12, 2024 · 9 comments
Labels
bug Something isn't working grade-a high quality report This report is of especially high quality Q-36 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 sponsor acknowledged Technically the issue is correct, but we're not going to resolve it for XYZ reasons

Comments

@c4-bot-5
Copy link
Contributor

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

@c4-bot-5 c4-bot-5 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 Mar 12, 2024
c4-bot-5 added a commit that referenced this issue Mar 12, 2024
c4-bot-5 added a commit that referenced this issue Mar 12, 2024
@c4-pre-sort c4-pre-sort added the sufficient quality report This report is of sufficient quality label Mar 24, 2024
@c4-pre-sort
Copy link

0xEVom marked the issue as sufficient quality report

@c4-pre-sort
Copy link

0xEVom marked the issue as high quality report

@c4-pre-sort c4-pre-sort added high quality report This report is of especially high quality and removed sufficient quality report This report is of sufficient quality labels Mar 25, 2024
@0xEVom
Copy link

0xEVom commented Mar 25, 2024

GA-05: reckless admin mistake, invalid
QA-09: invalid

@kalinbas
Copy link

kalinbas commented Mar 27, 2024

QA-01 Depending on the network 1 minute may be enough, also TWAP is only used to verify prices in the standard scenario where Chainlink prices are used mainly. 30 minutes is way to much when prices move fast.
QA-02 If chainlink is down, only liquidiate, decreaseLiquidity and borrow functionality would be down. Thats why there is the emergency mode to disable chainlink completely if needed.
QA-03 This will never reach 0 for a normal token (and this code is already deployed) - so we will leave it
QA-04 Only called by admin so not that important
QA-05: Invalid
QA-06 Will be part of adding new tokens taking care that pools have enough history. If there is a problem with it, the history size may be increased by anyone.
QA-07 Ok agree
QA-08 No, its ok that ETH is sent to any address.
QA-09: Invalid

@c4-sponsor
Copy link

kalinbas (sponsor) acknowledged

@c4-sponsor c4-sponsor added the sponsor acknowledged Technically the issue is correct, but we're not going to resolve it for XYZ reasons label Mar 27, 2024
@c4-judge
Copy link

jhsagd76 marked the issue as grade-a

@c4-judge c4-judge added grade-a selected for report This submission will be included/highlighted in the audit report labels Mar 31, 2024
@c4-judge
Copy link

c4-judge commented Apr 1, 2024

jhsagd76 marked the issue as selected for report

@jhsagd76
Copy link

Invalid

  • QA-01: Depending on the network 1 minute may be enough, also TWAP is only used to verify prices in the standard scenario where Chainlink prices are used mainly. 30 minutes is way to much when prices move fast.
  • QA-02: If chainlink is down, only liquidiate, decreaseLiquidity and borrow functionality would be down. Thats why there is the emergency mode to disable chainlink completely if needed.
  • QA-05: The current condition is correct.
  • QA-06: Will be part of adding new tokens taking care that pools have enough history. If there is a problem with it, the history size may be increased by anyone.
  • QA-08: No, its ok that ETH is sent to any address.
  • QA-09: Yep, its deprecated. But the use in the code is correct (0 approval is guaranteed each time)

Low

  • QA-03

Downgraded Low

NC

  • QA-04
  • QA-07

Summary

1 Low 2 NC + 3 Downgraded QA Low

@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
bug Something isn't working grade-a high quality report This report is of especially high quality Q-36 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 sponsor acknowledged Technically the issue is correct, but we're not going to resolve it for XYZ reasons
Projects
None yet
Development

No branches or pull requests

9 participants