0xa0995d43901551601060447f9abf93ebc277cec2
As of 21 Nov 2026, Trustblock’s record holds 0xa0995d43901551601060447f9abf93ebc277cec2 on Arbitrum as a contract of hypeboy. 1 audit report on Trustblock lists this address: CertiK, 24 Jan 2024. 3 findings in it are recorded as open or acknowledged.
Each report’s scope as stored on Trustblock names this address on Arbitrum.
| Audit | Security firm | Date | Commit named in the report | Report |
|---|---|---|---|---|
| hypelab-Audit | CertiK | Not recorded (see the report) | Open |
2 High, 1 Low. In the firm’s own words; statuses are the firm’s, from each report.
In the contract `ERC20Token` 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 unlock the locked tokens. 
The audit on Trustblock · Open the reportAll of the HIPPOP tokens 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 audit on Trustblock · Open the reportVariables are written but never read and subsequently written again, suggesting potential inefficiencies or logic errors in the code. This may lead to confusion when analyzing the code or impact the performance of the smart contract during execution. `success` is written twice, but not used in-between. ```solidity=11 success = _burn(msg.sender, amount); ``` ```solidity=13 success = true; ```
The audit on Trustblock · Open the reportThe hypeboy security record · Every hypeboy address · This address on the explorer