Omniscia DUA Audit
Token Implementation Security Audit
Audit Overview
We were tasked with performing an audit of the DUA codebase and in particular their EIP-20 token implementation.
Over the course of the audit, we identified a potential adjustment to the blacklist policy that could render it more stringent and secure, alongside some minor optimizations.
We advise the DUA team to closely evaluate all minor-and-above findings identified in the report and promptly remediate them as well as consider all optimizational exhibits identified in the report.
Post-Audit Conclusion
The DUA team iterated through all findings within the report and provided us with a revised commit hash to evaluate all exhibits on.
We evaluated all alleviations performed by DUA and have identified that all exhibits have been adequately dealt with no outstanding issues remaining in the report.
Contracts Assessed
| Files in Scope | Repository | Commit(s) |
|---|---|---|
| ETH_DUAToken.sol (ETH) | tokenETH | e078656b39, 81a6402a98 |
Audit Synopsis
| Severity | Identified | Alleviated | Partially Alleviated | Acknowledged |
|---|---|---|---|---|
 | 0 | 0 | 0 | 0 |
 | 4 | 4 | 0 | 0 |
 | 1 | 1 | 0 | 0 |
 | 0 | 0 | 0 | 0 |
 | 0 | 0 | 0 | 0 |
During the audit, we filtered and validated a total of 2 findings utilizing static analysis tools as well as identified a total of 3 findings during the manual review of the codebase. We strongly recommend that any minor severity or higher findings are dealt with promptly prior to the project's launch as they can introduce potential misbehaviours of the system as well as exploits.
The list below covers each segment of the audit in depth and links to the respective chapter of the report: