Archon public report
ReentrancyGuard_Suite__3_contracts_
Mantle Mainnet · scan depth quick · generated 7/3/2026, 10:22:26 AM
Risk Score
24
Archon completed a read-only Mantle Mainnet audit of ReentrancyGuard_Suite__3_contracts_ and found 3 deterministic findings. The highest-priority issue is Review calldata parameter width, with risk score 24/100 based on severity-weighted findings. The function `transfer` uses `uint256` for the `amount` parameter, which is wider than the ERC-20 standard `uint` (uint256) but could be optimized if the token's total supply is significantly less than 2^256-1. However, since this is an interface definition, no optimization is needed, but the finding flags a potential review of calldata parameter width for gas efficiency on Mantle. Review the recommended fixes and run regression tests before deployment.
Models used: Tencent Cloud TokenHub (deepseek-v4-pro) — AI reasoning served on Tencent Cloud TokenHub.
Findings
| Severity | Finding | Location | Confidence |
|---|---|---|---|
| low | Review calldata parameter width The function `transfer` uses `uint256` for the `amount` parameter, which is wider than the ERC-20 standard `uint` (uint256) but could be optimized if the token's total supply is significantly less than 2^256-1. However, since this is an interface definition, no optimization is needed, but the finding flags a potential review of calldata parameter width for gas efficiency on Mantle. | ReentrancyGuard_Suite__3_contracts_.sol:7 | 30% |
| low | Review calldata parameter width The function `approve` uses `uint256` for the `amount` parameter. Similar to the previous finding, this can be optimized if the allowance range is known to be limited. Converting to a smaller type (e.g., `uint128`) reduces calldata size, improving gas efficiency on Mantle. | ReentrancyGuard_Suite__3_contracts_.sol:9 | 30% |
| low | Review calldata parameter width The function `transferFrom` in the interface uses `address` parameters, which occupy 20 bytes each in calldata. On Mantle, using smaller packed types like `uint160` for addresses could reduce calldata size and gas costs, but only if the function's internal logic does not rely on the `address` type's specific properties. | ReentrancyGuard_Suite__3_contracts_.sol:10 | 30% |