Hanchain
CertiK reviewed KHANs (Hanchain) on 24 Apr 2024: 6 findings, 0 critical; 4 marked fixed, 2 open.
Report hosted on skynet.certik.com.
Trustblock does not review code.
Findings6
Statuses are the security firm’s own, from its report.
| Severity | Open | Acknowledged | Fixed |
|---|---|---|---|
| Critical | 0 | 0 | 0 |
| High | 2 | 0 | 1 |
| Medium | 0 | 0 | 0 |
| Low | 0 | 0 | 3 |
HighCentralization Risks in TokenTimelock.solOpen
In the contract `TokenTimelock` 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. 
HighInitial Token DistributionOpen
All **HanChain** tokens are sent to the contract deployer when deploying the contract. This is a potential centralization risk as the deployer can distribute **HanChain** tokens without the consensus of the community.
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 (2)
- contracts/TokenTimelock.sol
- contracts/HanChain.sol
Part of KHANs’s security record
KHANsSecurity 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