DRX Token
CertiK reviewed DRX Token on 19 Feb 2025: 26 findings, 0 critical; 11 marked fixed, 2 acknowledged, 13 open.
Report hosted on skynet.certik.com.
Trustblock does not review code.
Findings26
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 5 | 0 | 1 |
| Medium | 0 | 2 | 0 |
| Low | 8 | 0 | 10 |
MediumNo Cap on FeesAcknowledged
The function `SetFees()` allows fees to be potentially set to as high as 99%. If this occurs, users would receive a minimal part of tokens from the contract, resulting in a big loss of their investment.
MediumPossible To Regain Ownership After RenouncingAcknowledged
In the contract `DRX_TOKEN`, the `ownership` can be regained after renouncing it. This is because when calling `transferOwnership()`, the address of the next owner is stored in the state variable `potentialOwner` until this address calls `acceptOwnership()`, while the `owner` address does not change. If the `owner` calls `renounceOwnership()` then the `owner` address is updated but not the variable `potentialOwner`, meaning that if this address calls `acceptOwnership()` after the ownership has been renounced, the `potentialOwner` address will be set as the new `owner`.
Contracts in scope
No deployed address is recorded for this audit.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (1)
- https://github.com/ipds13/drxtoken/smart_contract/DRX_TOKEN.sol at commit bf95c815c6d43a5118ca6e7a9d9ca36e97c97326
Part of DRX Token’s security record
DRX TokenSecurity firm
CertiK1,044 projects reviewed · 1,375 reports · latest May 2025
See CertiK’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