-
Notifications
You must be signed in to change notification settings - Fork 0
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 #3
Comments
All comments are contained in inherited interface with Natspec |
|
|
|
We are not concerned with the approval front running attack during migration. |
Hmm I'm not sure I understand what this means actually. |
We can look into this further but I don't think this is needed. The getters are pure functions, the refinance functions intentionally do not validate since they have to be agreed on by two parties so they should have flexibiltiy, and the establishment fee values are not rates so they cannot be validated |
|
We're not going to add any of these |
|
The constructors aren't supposed to match |
Will remove these, this is not an issue though |
This is intended functionality |
Disagree with all of these findings |
Title: Missing commenting
Severity: Low Risk
Title: Mult instead div in compares
Severity: Low Risk
Title: Not verified owner
Severity: Low Risk
Title: Two Steps Verification before Transferring Ownership
Severity: Low Risk
The following contracts have a function that allows them an admin to change it to a different address. If the admin accidentally uses an invalid address for which they do not have the private key, then the system gets locked.
It is important to have two steps admin change where the first is announcing a pending new admin and the new address should then claim its ownership.
A similar issue was reported in a previous contest and was assigned a severity of medium: code-423n4/2021-06-realitycards-findings#105
Title: safeApprove of openZeppelin is deprecated
Severity: Low Risk
Deprecated safeApprove in xMPL.sol line 62: require(ERC20(oldAsset).approve(migrator, oldAssetBalanceBeforeMigration), "xMPL:PM:APPROVAL_FAILED");
Title: Named return issue
Severity: Low Risk
Users can mistakenly think that the return value is the named return, but it is actually the actualreturn statement that comes after. To know that the user needs to read the code and is confusing.
Furthermore, removing either the actual return or the named return will save gas.
Title: Does not validate the input fee parameter
Severity: Low Risk
Some fee parameters of functions are not checked for invalid values. Validate the parameters:
Title: Missing non reentrancy modifier
Severity: Low Risk
The following functions are missing reentrancy modifier although some other pulbic/external functions does use reentrancy modifer.
Even though I did not find a way to exploit it, it seems like those functions should have the nonReentrant modifier as the other functions have it as well..
Title: Not verified input
Severity: Low Risk
Title: Div by 0
Severity: Low/Medium Risk
Division by 0 can lead to accidentally revert,
(An example of a similar issue - code-423n4/2021-10-defiprotocol-findings#84)
Title: Override function but with different argument location
Severity: Low/Med Risk
Title: Open TODOs
Severity: Low Risk
Open TODOs can hint at programming or architectural errors that still need to be fixed.
These files has open TODOs:
Open TODO in RevenueDistributionToken.sol line 275 : // TODO: investigate whether leave this
require()
in for clarity from error message, or let the safe math check incallerAllowance - shares_
handle the underflow.Open TODO in RevenueDistributionToken.sol line 77 : // TODO: Revisit returns
Title: Anyone can withdraw others
Severity: Low Risk
Anyone can withdraw users shares. Although we think that they are sent to the right address, it is still
1) not the desired behavior
2) can be dangerous if the receiver is a smart contract
3) the receiver may not know someone withdraw him
The text was updated successfully, but these errors were encountered: