Quantstamp reviewed Degens on 6 Sep 2019: 8 findings, 0 critical; 4 marked fixed, 4 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 | 4 | 0 | 4 |
Line 228 compares the block timestamp to the expiry attribute. The timestamps can be manipulated by miners. An analogous issue is present on line 384, and may be present also on line 325. If the value of the trade becomes extremely high shortly before the trade expiry, it might be in miner’s interest to manipulate the timestamp and make the trade happen, despite it being expired already.
The clone-and-own approach involves copying and adjusting open source code at one's own discretion. From the development perspective, it is initially beneficial as it reduces the amount of effort. However, from the security perspective, it involves some risks as the code may not follow the best practices, may contain a security vulnerability, or may include intentionally or unintentionally modified upstream libraries. Rather than the clone-and-own approach, a good industry practice is to use the Truffle framework for managing library dependencies. This eliminates the clone-and-own risks yet allows for following best practices, such as, using libraries. The contract uses interfaces that are part of commonly used libraries. This concerns Line 5 and the interface IERC20Token, and libraries Math and SafeMath for mathematical methods on lines 718 onwards
The Quantstamp team recommends communicating the restriction to the users. The Degens team does not believe this restriction will have any impact on real-world token contracts. As mentioned in the docs, a user would need to have ~340 quintillion DAI in their account before this would come up. Even if they did, the only consequence would be that they could not use the Degens contract because their trades will fail, until they transferred out some of their DAI.
Every Solidity file specifies in the header a version number of the format pragma solidity (^)0.4.*. The caret (^) before the version number implies an unlocked pragma, meaning that the compiler will use the specified version , hence the term "unlocked." For consistency and to prevent unexpected behavior in the future, it is recommended to remove the caret to lock the file onto a specific Solidity version.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (3)
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