naws.ai - Audit
CertiK reviewed NAWS (naws.ai - Audit) on 4 Oct 2024: 2 findings, 0 critical; all acknowledged, none fixed.
Report hosted on skynet.certik.com.
Trustblock does not review code.
Findings2
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 0 | 2 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 0 | 0 | 0 |
HighCentralization Risks in NAWS.solAcknowledged
In the contract `NAWS`, the role `_owner` has authority over the functions shown in the diagram below. Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and ban/unban an address, pause/unpause the contract, transfer/renounce ownership. 
HighInitial Token DistributionAcknowledged
All of the NAWS.AI tokens are equivocally distributed to 5 externally-owned account (EOA) addresses. This is a centralization risk because the owners of the EOAs can distribute tokens without obtaining the consensus of the community. Any compromise to these addresses may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project.
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)
- contracts/NAWS.sol
Part of NAWS’s security record
NAWSSecurity 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