Archon public report
MantleComplexVaultLab
Mantle Mainnet · scan depth quick · generated 6/9/2026, 8:14:54 AM
Risk Score
100
Archon completed a read-only Mantle Mainnet audit of with and found 174 deterministic findings. The highest-priority issue is Arbitrary Send Erc20, with risk score 100/100 based on severity-weighted findings. Arbitrary Send Erc20 was detected from deterministic analysis at with.sol:927-953. 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 | Arbitrary Send Erc20 Arbitrary Send Erc20 was detected from deterministic analysis at with.sol:927-953. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:927 | 86% |
| high | Reentrancy Eth Reentrancy Eth was detected from deterministic analysis at with.sol:422-447. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:422 | 86% |
| high | Unchecked Transfer Unchecked Transfer was detected from deterministic analysis at with.sol:554-594. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:554 | 86% |
| high | Unchecked Transfer Unchecked Transfer was detected from deterministic analysis at with.sol:868-897. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:868 | 86% |
| high | Unchecked Transfer Unchecked Transfer was detected from deterministic analysis at with.sol:974-1026. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:974 | 86% |
| high | Unchecked Transfer Unchecked Transfer was detected from deterministic analysis at with.sol:1107-1115. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1107 | 86% |
| high | Unchecked Transfer Unchecked Transfer was detected from deterministic analysis at with.sol:817-835. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:817 | 86% |
| high | Unchecked Transfer Unchecked Transfer was detected from deterministic analysis at with.sol:1064-1085. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1064 | 86% |
| high | Unchecked Transfer Unchecked Transfer was detected from deterministic analysis at with.sol:499-552. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:499 | 86% |
| high | Unchecked Transfer Unchecked Transfer was detected from deterministic analysis at with.sol:718-757. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:718 | 86% |
| high | Unchecked Transfer Unchecked Transfer was detected from deterministic analysis at with.sol:837-855. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:837 | 86% |
| high | Unchecked Transfer Unchecked Transfer was detected from deterministic analysis at with.sol:1034-1058. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1034 | 86% |
| medium | Divide Before Multiply Divide Before Multiply was detected from deterministic analysis at with.sol:554-594. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:554 | 74% |
| medium | Divide Before Multiply Divide Before Multiply was detected from deterministic analysis at with.sol:422-447. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:422 | 74% |
| medium | Incorrect Equality Incorrect Equality was detected from deterministic analysis at with.sol:478-493. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:478 | 74% |
| medium | Incorrect Equality Incorrect Equality was detected from deterministic analysis at with.sol:1158-1164. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1158 | 74% |
| medium | Incorrect Equality Incorrect Equality was detected from deterministic analysis at with.sol:385-420. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:385 | 74% |
| medium | Reentrancy No Eth Reentrancy No Eth was detected from deterministic analysis at with.sol:554-594. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:554 | 74% |
| medium | Reentrancy No Eth Reentrancy No Eth was detected from deterministic analysis at with.sol:621-642. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:621 | 74% |
| medium | Reentrancy No Eth Reentrancy No Eth was detected from deterministic analysis at with.sol:974-1026. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:974 | 74% |
| medium | Reentrancy No Eth Reentrancy No Eth was detected from deterministic analysis at with.sol:718-757. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:718 | 74% |
| medium | Reentrancy No Eth Reentrancy No Eth was detected from deterministic analysis at with.sol:499-552. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:499 | 74% |
| medium | Tx Origin Tx Origin was detected from deterministic analysis at with.sol:296-303. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:296 | 74% |
| medium | Unchecked Lowlevel Unchecked Lowlevel was detected from deterministic analysis at with.sol:837-855. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:837 | 74% |
| medium | Unchecked Lowlevel Unchecked Lowlevel was detected from deterministic analysis at with.sol:868-897. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:868 | 74% |
| medium | Unchecked Lowlevel Unchecked Lowlevel was detected from deterministic analysis at with.sol:422-447. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:422 | 74% |
| medium | Unchecked Lowlevel Unchecked Lowlevel was detected from deterministic analysis at with.sol:460-476. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:460 | 74% |
| medium | Unchecked Lowlevel Unchecked Lowlevel was detected from deterministic analysis at with.sol:817-835. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:817 | 74% |
| medium | Uninitialized Local Uninitialized Local was detected from deterministic analysis at with.sol:767. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:767 | 74% |
| medium | Unused Return Unused Return was detected from deterministic analysis at with.sol:667-689. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:667 | 74% |
| low | Events Maths Events Maths was detected from deterministic analysis at with.sol:305-316. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:305 | 74% |
| low | Calls Loop Calls Loop was detected from deterministic analysis at with.sol:974-1026. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:974 | 74% |
| low | Calls Loop Calls Loop was detected from deterministic analysis at with.sol:1034-1058. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1034 | 74% |
| low | Reentrancy Benign Reentrancy Benign was detected from deterministic analysis at with.sol:499-552. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:499 | 74% |
| low | Reentrancy Benign Reentrancy Benign was detected from deterministic analysis at with.sol:667-689. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:667 | 74% |
| low | Reentrancy Benign Reentrancy Benign was detected from deterministic analysis at with.sol:780-815. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:780 | 74% |
| low | Reentrancy Benign Reentrancy Benign was detected from deterministic analysis at with.sol:974-1026. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:974 | 74% |
| low | Reentrancy Benign Reentrancy Benign was detected from deterministic analysis at with.sol:698-716. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:698 | 74% |
| low | Reentrancy Events Reentrancy Events was detected from deterministic analysis at with.sol:817-835. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:817 | 74% |
| low | Reentrancy Events Reentrancy Events was detected from deterministic analysis at with.sol:621-642. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:621 | 74% |
| low | Reentrancy Events Reentrancy Events was detected from deterministic analysis at with.sol:1064-1085. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1064 | 74% |
| low | Reentrancy Events Reentrancy Events was detected from deterministic analysis at with.sol:780-815. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:780 | 74% |
| low | Reentrancy Events Reentrancy Events was detected from deterministic analysis at with.sol:554-594. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:554 | 74% |
| low | Reentrancy Events Reentrancy Events was detected from deterministic analysis at with.sol:837-855. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:837 | 74% |
| low | Reentrancy Events Reentrancy Events was detected from deterministic analysis at with.sol:698-716. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:698 | 74% |
| low | Reentrancy Events Reentrancy Events was detected from deterministic analysis at with.sol:974-1026. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:974 | 74% |
| low | Reentrancy Events Reentrancy Events was detected from deterministic analysis at with.sol:667-689. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:667 | 74% |
| low | Reentrancy Events Reentrancy Events was detected from deterministic analysis at with.sol:718-757. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:718 | 74% |
| low | Reentrancy Events Reentrancy Events was detected from deterministic analysis at with.sol:460-476. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:460 | 74% |
| low | Reentrancy Events Reentrancy Events was detected from deterministic analysis at with.sol:1034-1058. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1034 | 74% |
| low | Reentrancy Events Reentrancy Events was detected from deterministic analysis at with.sol:422-447. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:422 | 74% |
| low | Reentrancy Events Reentrancy Events was detected from deterministic analysis at with.sol:927-953. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:927 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:1121-1135. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1121 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:927-953. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:927 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:1087-1105. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1087 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:644-661. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:644 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:1064-1085. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1064 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:974-1026. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:974 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:780-815. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:780 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:499-552. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:499 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:857-866. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:857 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:718-757. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:718 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:339-363. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:339 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:422-447. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:422 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:365-379. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:365 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:621-642. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:621 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:667-689. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:667 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:868-897. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:868 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:596-619. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:596 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:554-594. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:554 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:698-716. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:698 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:837-855. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:837 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:817-835. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:817 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:1137-1156. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1137 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:478-493. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:478 | 74% |
| low | Timestamp Timestamp was detected from deterministic analysis at with.sol:460-476. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:460 | 74% |
| info | Solc Version Solc Version was detected from deterministic analysis at with.sol:2. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:2 | 74% |
| info | Low Level Calls Low Level Calls was detected from deterministic analysis at with.sol:422-447. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:422 | 74% |
| info | Low Level Calls Low Level Calls was detected from deterministic analysis at with.sol:837-855. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:837 | 74% |
| info | Low Level Calls Low Level Calls was detected from deterministic analysis at with.sol:460-476. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:460 | 74% |
| info | Low Level Calls Low Level Calls was detected from deterministic analysis at with.sol:868-897. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:868 | 74% |
| info | Low Level Calls Low Level Calls was detected from deterministic analysis at with.sol:817-835. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:817 | 74% |
| info | Naming Convention Naming Convention was detected from deterministic analysis at with.sol:282. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:282 | 74% |
| info | Naming Convention Naming Convention was detected from deterministic analysis at with.sol:307. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:307 | 74% |
| info | Naming Convention Naming Convention was detected from deterministic analysis at with.sol:306. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:306 | 74% |
| info | Naming Convention Naming Convention was detected from deterministic analysis at with.sol:308. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:308 | 74% |
| info | Naming Convention Naming Convention was detected from deterministic analysis at with.sol:289. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:289 | 74% |
| info | Naming Convention Naming Convention was detected from deterministic analysis at with.sol:265. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:265 | 74% |
| info | Naming Convention Naming Convention was detected from deterministic analysis at with.sol:296. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:296 | 74% |
| info | Reentrancy Unlimited Gas Reentrancy Unlimited Gas was detected from deterministic analysis at with.sol:385-420. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:385 | 74% |
| info | Reentrancy Unlimited Gas Reentrancy Unlimited Gas was detected from deterministic analysis at with.sol:1087-1105. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1087 | 74% |
| info | Reentrancy Unlimited Gas Reentrancy Unlimited Gas was detected from deterministic analysis at with.sol:422-447. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:422 | 74% |
| high | Missing slippage enforcement for swap output Missing slippage enforcement for swap output was detected from deterministic analysis at with.sol:142. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:142 | 86% |
| high | tx.origin authorization can be phished through proxy calls tx.origin authorization can be phished through proxy calls was detected from deterministic analysis at with.sol:297. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:297 | 86% |
| medium | Timestamp-sensitive settlement lacks explicit tolerance window Timestamp-sensitive settlement lacks explicit tolerance window was detected from deterministic analysis at with.sol:254. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:254 | 74% |
| low | Review calldata parameter width Review calldata parameter width was detected from deterministic analysis at with.sol:22. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:22 | 74% |
| low | Review calldata parameter width Review calldata parameter width was detected from deterministic analysis at with.sol:29. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:29 | 74% |
| low | Review calldata parameter width Review calldata parameter width was detected from deterministic analysis at with.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. | with.sol:37 | 74% |
| low | Review calldata parameter width Review calldata parameter width was detected from deterministic analysis at with.sol:38. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:38 | 74% |
| low | Review calldata parameter width Review calldata parameter width was detected from deterministic analysis at with.sol:1107. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1107 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:220. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:220 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:225. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:225 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:247. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:247 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:266. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:266 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:273. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:273 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:310. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:310 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:311. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:311 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:345. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:345 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:372. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:372 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:426. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:426 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:507. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:507 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:508. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:508 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:561. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:561 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:562. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:562 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:565. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:565 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:602. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:602 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:616. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:616 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:630. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:630 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:673. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:673 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:677. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:677 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:700. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:700 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:724. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:724 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:794. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:794 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:796. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:796 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:933. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:933 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:938. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:938 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:985. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:985 | 74% |
| info | Replace long revert string with custom error Replace long revert string with custom error was detected from deterministic analysis at with.sol:986. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:986 | 74% |
| info | Mark never-changing value constant or immutable Mark never-changing value constant or immutable was detected from deterministic analysis at with.sol:47. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:47 | 74% |
| info | Cache repeated storage read Cache repeated storage read was detected from deterministic analysis at with.sol:345. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:345 | 74% |
| info | Cache repeated storage read Cache repeated storage read was detected from deterministic analysis at with.sol:402. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:402 | 74% |
| info | Cache repeated storage read Cache repeated storage read was detected from deterministic analysis at with.sol:533. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:533 | 74% |
| info | Cache repeated storage read Cache repeated storage read was detected from deterministic analysis at with.sol:682. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:682 | 74% |
| info | Cache repeated storage read Cache repeated storage read was detected from deterministic analysis at with.sol:803. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:803 | 74% |
| info | Use unchecked loop increment where bounded Use unchecked loop increment where bounded was detected from deterministic analysis at with.sol:969. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:969 | 74% |
| info | Use unchecked loop increment where bounded Use unchecked loop increment where bounded was detected from deterministic analysis at with.sol:1029. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1029 | 74% |
| info | Cache array length before loop Cache array length before loop was detected from deterministic analysis at with.sol:969. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:969 | 74% |
| info | Cache array length before loop Cache array length before loop was detected from deterministic analysis at with.sol:1029. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1029 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:386. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:386 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:404. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:404 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:415. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:415 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:423. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:423 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:442. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:442 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:450. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:450 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:451. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:451 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:468. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:468 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:504. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:504 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:535. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:535 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:547. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:547 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:558. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:558 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:589. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:589 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:611. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:611 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:626. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:626 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:627. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:627 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:675. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:675 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:729. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:729 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:735. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:735 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:740. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:740 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:788. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:788 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:881. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:881 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:885. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:885 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:889. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:889 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:893. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:893 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:932. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:932 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:1009. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1009 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:1021. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1021 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:1068. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1068 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:1091. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1091 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:1126. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1126 | 74% |
| info | Use != 0 for unsigned non-zero checks Use != 0 for unsigned non-zero checks was detected from deterministic analysis at with.sol:1147. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1147 | 74% |
| medium | Bitmap-pack boolean flags Bitmap-pack boolean flags was detected from deterministic analysis at with.sol:148. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:148 | 74% |
| medium | Bitmap-pack boolean flags Bitmap-pack boolean flags was detected from deterministic analysis at with.sol:149. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:149 | 74% |
| info | Remove redundant zero initialization Remove redundant zero initialization was detected from deterministic analysis at with.sol:969. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:969 | 74% |
| info | Remove redundant zero initialization Remove redundant zero initialization was detected from deterministic analysis at with.sol:1029. The issue should be reviewed because it can affect contract correctness, user balances, or operational cost depending on how the function is used. | with.sol:1029 | 74% |