

Archon public report
VaultV2
Mantle Mainnet · scan depth quick · generated 7/2/2026, 1:09:50 AM
Risk Score
100
Archon completed a read-only Mantle Mainnet audit of VaultV2 and found 17 deterministic findings. The highest-priority issue is Reentrancy Eth, with risk score 100/100 based on severity-weighted findings. Reentrancy Eth was detected from deterministic analysis at VaultV2.sol:27-35. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. Review the recommended fixes and run regression tests before deployment.
Findings
| Severity | Finding | Location | Confidence |
|---|---|---|---|
| high | Reentrancy Eth Reentrancy Eth was detected from deterministic analysis at VaultV2.sol:27-35. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:27 | 86% |
| low | Reentrancy Events Reentrancy Events was detected from deterministic analysis at VaultV2.sol:27-35. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:27 | 74% |
| info | Low Level Calls Low Level Calls was detected from deterministic analysis at VaultV2.sol:27-35. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:27 | 74% |
| info | Redundant Statements Redundant Statements was detected from deterministic analysis at VaultV2.sol:48. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:48 | 74% |
| low | Cache Array Length Cache Array Length was detected from deterministic analysis at VaultV2.sol:55. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:55 | 74% |
| critical | External value transfer before balance update External value transfer before balance update was detected from deterministic analysis at VaultV2.sol:30. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:30 | 86% |
| high | Missing slippage enforcement for swap output Missing slippage enforcement for swap output was detected from deterministic analysis at VaultV2.sol:37. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:37 | 86% |
| medium | Unbounded storage iteration can create runaway gas cost Unbounded storage iteration can create runaway gas cost was detected from deterministic analysis at VaultV2.sol:55. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:55 | 74% |
| low | Review calldata parameter width Review calldata parameter width was detected from deterministic analysis at VaultV2.sol:27. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:27 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at VaultV2.sol:28. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:28 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at VaultV2.sol:41. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:41 | 74% |
| info | Cache repeated storage read Cache repeated storage read was detected from deterministic analysis at VaultV2.sol:18. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:18 | 74% |
| info | Use unchecked loop increment where bounded Use unchecked loop increment where bounded was detected from deterministic analysis at VaultV2.sol:55. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:55 | 74% |
| info | Cache array length before loop Cache array length before loop was detected from deterministic analysis at VaultV2.sol:55. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:55 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at VaultV2.sol:16. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:16 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at VaultV2.sol:40. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:40 | 74% |
| info | Remove redundant zero initialization Remove redundant zero initialization was detected from deterministic analysis at VaultV2.sol:55. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | VaultV2.sol:55 | 74% |

