Quantstamp reviewed Multis on 13 Dec 2019: 3 findings, 0 critical; 1 acknowledged, 2 open.
Report hosted on certificate.quantstamp.com.
Trustblock does not review code.
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 2 | 1 | 0 |
Integer overflow/underflow occur when an integer hits its bit-size limit. Every integer has a set range; when that range is passed, the value loops back around. A clock is a good analogy: at 11:59, the minute hand goes to 0, not 60, because 59 is the largest possible minute. Integer overflow and underflow may cause many unexpected kinds of behavior. Specifically, integer underflow may occur in line 401 in the statement `to - from`.
Current implementation requires trusting that the multisig owners behave well. A malicious co-owner (or when their account gets hacked) could: 1) repeatedly call `submitTransaction()` for random stuff; or 2) just alternate between calling `confirmTransaction()` and `revokeConfirmation()` repeatedly. Consequently, the multisig creator’s balance used for GSN payments could get depleted. It is possible because the function `acceptRelayedCall()` accepts all requests regardless of the cost.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (4)
240 projects reviewed · 338 reports · latest Nov 2026
See Quantstamp’s auditsSomething wrong on this page? A missing report, a wrong date, a finding that was fixed since. Tell us and we check it against its source.
Tell us