0xbfc119ab99fe3e931df7eb67f40c40fa58ccf05e
As of 21 Nov 2026, Trustblock’s record holds 0xbfc119ab99fe3e931df7eb67f40c40fa58ccf05e on BNB Chain as a contract of ::IndustrySonic OFFICIAL::. 1 audit report on Trustblock lists this address: CertiK, 15 Aug 2024. 2 findings in it are recorded as open or acknowledged.
Each report’s scope as stored on Trustblock names this address on BNB Chain.
| Audit | Security firm | Date | Commit named in the report | Report |
|---|---|---|---|---|
| Industry Sonic - Audit | CertiK | Not recorded (see the report) | On Trustblock |
1 High, 1 Low. In the firm’s own words; statuses are the firm’s, from each report.
All of the tokens are sent to the contract deployer . This is a centralization risk because the deployer can distribute tokens without obtaining the consensus of the community. Any compromise to the deployer address may allow a hacker to steal and sell tokens on the market, resulting in severe damage to the project.
The audit on TrustblockThe contract is serving as the underlying entity to interact with one or more third party protocols. The scope of the audit treats third party entities as black boxes and assumes their functional correctness. However, in the real world, third parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of third parties can possibly create severe impacts, such as increasing fees of third parties, migrating to new LP pools, etc. ```solidity=776 constructor(address payable receiver, string memory serviceName, bytes memory signature, address wallet) payable { ``` - The function `ServicePayer.constructor` interacts with third party contract with `IPayable` interface via `receiver`.
The audit on TrustblockThe ::IndustrySonic OFFICIAL:: security record · Every ::IndustrySonic OFFICIAL:: address · This address on the explorer