SDAO / Token Migration
Hacken reviewed Singularity DAO (SDAO / Token Migration) on 8 May 2024: 8 findings, 0 critical; 6 marked fixed, 2 open.
No open critical findings
Open the reportOpen Singularity DAO’s security record
Report hosted on hacken.io.
Trustblock does not review code.
Findings8
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 | 0 | 6 |
LowConstructor and initialize() Can Be Marked As PayableFixed
The report gives no description here.
LowIncorrect Check In Burnable Feature InitializationFixed
The report gives no description here.
LowMissing Event EmittingFixed
The report gives no description here.
Lowpublic Functions Not Called By The Contract Should Be Declared External InsteadFixed
The report gives no description here.
LowReturn Values Of transfer()/transferFrom() Not CheckedFixed
The report gives no description here.
LowState Variables That Are Used Multiple Times In a Function Should Be Cached In Stack VariablesFixed
The report gives no description here.
Contracts in scope2
| Address | Chain | Source code |
|---|---|---|
| 0x993864e43caa7f7f12953ad6feb1d1ca635b875f | Chain: Ethereum | Source code: Verified source |
| 0x90ed8f1dc86388f14b64ba8fb4bbd23099f18240 | Chain: BNB Chain | Source code: Verified source |
Part of Singularity DAO’s security record
Singularity DAOAudits5 audits by 3 firmsLast audit Jun 2024, by Hacken.
Critical findingsNo open critical findingsAcross the 5 reports, 1 critical finding was reported. It is marked fixed by the firm that reported it.
Open Singularity DAO’s security recordSecurity firm
Hacken343 projects reviewed · 476 reports · latest Sep 2026
See Hacken’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