Hello.one - Audit 2
CertiK reviewed HELLO Labs (Hello.one - Audit 2) on 11 Oct 2022: 22 findings, 0 critical; 20 marked fixed, 2 open.
Report hosted on skynet.certik.com.
Trustblock does not review code.
Findings22
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 | 1 |
| Low | 0 | 0 | 18 |
HighCentralization Risks in Main.solOpen
In the contract `Main` 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 recover any tokens or ether for themselves, enable/disable trading between non-authorized users, airdrop `H1T3` from any address to any address, whitelist accounts, and change the max wallet limit. 
HighInitial Token DistributionOpen
All of the `H1T3` tokens are sent to whoever first calls the function `initialize()`. This could be a centralization risk as the initializer can distribute `H1T3` tokens without obtaining 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 (1)
- contracts/Main.sol
Part of HELLO Labs’s security record
HELLO LabsSecurity 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