0xadc3f2c3d728202658930860158c726d8180a38f
As of 21 Nov 2026, Trustblock’s record holds 0xadc3f2c3d728202658930860158c726d8180a38f on Ethereum as a contract of Starkmeta. 1 audit report on Trustblock lists this address: CertiK, 30 Nov 2022. 3 findings in it are recorded as open or acknowledged.
Each report’s scope as stored on Trustblock names this address on Ethereum.
| Audit | Security firm | Date | Commit named in the report | Report |
|---|---|---|---|---|
| starkmeta - 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 `SMETA` 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 - Lock the token transfer - Mint/Burn tokens for arbitrary addresses - Blacklist arbitrary addresses - Set new contract owner
The audit on Trustblock · Open the reportAll SMETA tokens are sent to the contract deployer when deploying the contract. This is a potential centralization risk as the deployer can distribute SMETA tokens without the consensus of the community.
The audit on Trustblock · Open the reportState variables that never change should be declared as `constant` to save gas. ```solidity=437 string Name = "StarkMeta Token"; ``` - `Name` should be declared `constant`. --- ```solidity=438 string Symbol = "SMETA"; ``` - `Symbol` should be declared `constant`.
The audit on Trustblock · Open the reportThe Starkmeta security record · Every Starkmeta address · This address on the explorer