0xa4b68d48d7bc6f04420e8077e6f74bdef809dea3
As of 21 Nov 2026, Trustblock’s record holds 0xa4b68d48d7bc6f04420e8077e6f74bdef809dea3 on BNB Chain as a contract of Bugscoin. 1 audit report on Trustblock lists this address: CertiK, 29 Oct 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 |
|---|---|---|---|---|
| BugsCoin - Audit | CertiK | Not recorded (see the report) | Open |
2 High. In the firm’s own words; statuses are the firm’s, from each report.
In the contract `BugsCoin` 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 burn tokens.  In the contract `Ownable` 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 transfer/renounce ownership. 
The audit on Trustblock · Open the reportAll of the BGSC 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 Trustblock · Open the reportThe Bugscoin security record · Every Bugscoin address · This address on the explorer