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

Upgraded Q -> M from 184 [1656338701670] #492

Closed
code423n4 opened this issue Jun 27, 2022 · 1 comment
Closed

Upgraded Q -> M from 184 [1656338701670] #492

code423n4 opened this issue Jun 27, 2022 · 1 comment
Labels
2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value bug Something isn't working duplicate This issue or pull request already exists upgraded by judge

Comments

@code423n4
Copy link
Contributor

Judge has assessed an item in Issue #184 as Medium risk. The relevant finding follows:

@code423n4 code423n4 added 2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value bug Something isn't working upgraded by judge labels Jun 27, 2022
code423n4 added a commit that referenced this issue Jun 27, 2022
@HickupHH3
Copy link
Collaborator

  1. Use safeTransfer/safeTransferFrom consistently instead of transfer/transferFrom
    dup of Use safeTransfer()/safeTransferFrom() instead of transfer()/transferFrom() #316

@HickupHH3 HickupHH3 added the duplicate This issue or pull request already exists label Jun 30, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
2 (Med Risk) Assets not at direct risk, but function/availability of the protocol could be impacted or leak value bug Something isn't working duplicate This issue or pull request already exists upgraded by judge
Projects
None yet
Development

No branches or pull requests

2 participants