Core Contracts
Regnum Aurum Acquisition Corp
HardhatReal World AssetsNFT
77,280 USDC
View results
Previous Next
Submission Details
Severity: low
Valid

The mint function returns incorrect values ​​in the correct order

wttt

Summary

The mint function returns incorrect values ​​in the correct order

Vulnerability Details

* @return A tuple containing:
* - bool: True if this is the first mint for the recipient, false otherwise
* - uint256: The amount of scaled tokens minted
* - uint256: The new total supply after minting
* - uint256: The amount of underlying tokens minted
❌ return (isFirstMint, amountToMint, totalSupply(), amountScaled);
​
(bool isFirstMint, uint256 amountScaled, uint256 newTotalSupply, uint256 amountUnderlying) = IRToken(reserve.reserveRTokenAddress).mint(
​

In the RToken.sol contract, the return value order of the mint function is wrong. The problem occurs in the position of the second and fourth parameters.

Impact

The values ​​of amountScaled and amountToMint are incorrect.

Tools Used

Manual review

Recommendations

The second parameter is amountScaled, and the fourth parameter is amountToMint.

✅ return (isFirstMint, amountScaled, totalSupply(), amountToMint);
​
Updates

Lead Judging Commences

inallhonesty Lead Judge 5 months ago
Submission Judgement Published
Validated
Assigned finding tags:

RToken::mint doesn't return data in the right order, making the protocol emit wrong events

inallhonesty Lead Judge 5 months ago
Submission Judgement Published
Validated
Assigned finding tags:

RToken::mint doesn't return data in the right order, making the protocol emit wrong events

Support

FAQs

Can't find an answer? Chat with us on Discord, Twitter or Linkedin.