STA contract 0x4d1e…f53c on BNB Chain

0x4d1e90ab966ae26c778b2f9f365aa40abb13f53c

As of 21 Nov 2026, Trustblock’s record holds 0x4d1e90ab966ae26c778b2f9f365aa40abb13f53c on BNB Chain as a contract of STA. 1 audit report on Trustblock lists this address: CertiK, 7 Feb 2023. 10 findings in it are recorded as open or acknowledged.

Audit reports that list this address1

Each report’s scope as stored on Trustblock names this address on BNB Chain.

AuditSecurity firmDateCommit named in the reportReport
STA TokenCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports10

2 High, 8 Low. In the firm’s own words; statuses are the firm’s, from each report.

HighCentralization Related RisksSTA Token · CertiKAcknowledged

In the contract `STAToken` the role `_owner` has authority over the following functions: - `renounceOwnership()` - `transferOwnership()` - `mint()` Any compromise to the `_owner` account may allow the hacker to take advantage of this authority and change ownership and mint new tokens.

The audit on Trustblock · Open the report
HighInitial Token DistributionSTA Token · CertiKAcknowledged

Tokens are sent to the deployer address when deploying the contract. This could be a centralization risk as the owner can distribute tokens without obtaining the consensus of the community.

The audit on Trustblock · Open the report
LowERC20 Approval Race ConditionSTA Token · CertiKOpen

The approval function of the ERC20 standard possesses a well-known vulnerability whereby two consecutive approvals can be exploited to instead “reset” the approval by consuming the approval that is meant to be replaced with a new one.

The audit on Trustblock · Open the report
LowFunction Visibility OptimizationSTA Token · CertiKOpen

The following functions are declared as `public`, contain array function arguments, and are not invoked in any of the contracts contained within the project's scope. Functions that are never called internally within the contract should have `external` visibility.

The audit on Trustblock · Open the report
LowOpenZeppelin Library Code Included in Source CodeSTA Token · CertiKOpen

It is highly recommended NOT to include OpenZeppelin library code directly in source code, but import the original library to minimize risk because even slight changes to the library code may lead to critical/major vulnerabilities/bugs. For Solidity version 0.6.x, the latest OpenZeppelin version 3.4.2 should be used.

The audit on Trustblock · Open the report
LowPull-Over-Push PatternSTA Token · CertiKOpen

The change of `_owner` by function `transferOwnership()` overrides the previously set `_owner` with the new one without guaranteeing the new `owner` has the ability to actuate transactions on-chain.

The audit on Trustblock · Open the report
LowRedundant Code ComponentsSTA Token · CertiKOpen

The linked statements do not affect the functionality of the codebase and appear to be either leftovers from test code or older functionality.

The audit on Trustblock · Open the report
LowSolidity Version Not RecommendedSTA Token · CertiKOpen

Solidity frequently releases new compiler versions. Using an old version prevents access to new Solidity security features. Also, recent versions may be too early to be trusted. The Solidity version in use is `0.5.16`.

The audit on Trustblock · Open the report
LowToo Many DigitsSTA Token · CertiKOpen

Literals with many digits are difficult to read and review.

The audit on Trustblock · Open the report
LowVariable could be declared as `constant`STA Token · CertiKOpen

Variables `_decimals`, `_symbol` and `_name` could be declared as `constant` since these state variables are never to be changed.

The audit on Trustblock · Open the report

The STA security record · Every STA address · This address on the explorer