CertiK reviewed IOST on 10 Mar 2025: 4 findings, 0 critical; 2 marked fixed, 2 open.
Report hosted on skynet.certik.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 | 2 | 0 | 0 |
| Medium | 0 | 0 | 0 |
| Low | 0 | 0 | 2 |
### IOSToken In the contract `IOSToken`, 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 mint arbitrage tokens to a specific account, provided that the total supply remains within the configured cap (90,000,000,000).** ### Vesting In the contract `Vesting`, 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 revoke a vesting schedule, create a vesting schedule for a beneficiary, and withdraw a specified amount safely.
All initial IOSToken tokens (21,320,000,000) are sent to the contract deployer or one or several externally-owned account (EOA) addresses. This is a centralization risk because the deployer or the owner(s) 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.
The report names a repository or files. Open the report to see its scope.
Repository and files the report names (4)
1,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