Spy-Token.io contract 0x17fd…aba1 on BNB Chain

0x17fd3caa66502c6f1cbd5600d8448f3af8f2aba1

As of 21 Nov 2026, Trustblock’s record holds 0x17fd3caa66502c6f1cbd5600d8448f3af8f2aba1 on BNB Chain as a contract of Spy-Token.io. 1 audit report on Trustblock lists this address: CertiK, 29 Mar 2022. 12 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
Smarty Pay TokenCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports12

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

HighCentralization Risk in SmartyPay.solSmarty Pay Token · CertiKAcknowledged

In the contract `Owned` the role `owner`/`newOwner` has authority over the following functions. - transferOwnership() - acceptOwnership() In the contract `SmartyPay` the role `owner` has authority over the following functions. - startAirdrop() - startSale() - clearETH() Any compromise to these accounts may allow the hacker to take advantage of this authority.

The audit on Trustblock · Open the report
HighInitial Token DistributionSmarty Pay Token · CertiKAcknowledged

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

The audit on Trustblock · Open the report
HighLack of Purchase Amount ValidationSmarty Pay Token · CertiKAcknowledged

If purchaser calls the function `tokenSale` with sending BNB less than the token price, the purchaser will get nothing but lose his BNB.

The audit on Trustblock · Open the report
HighLack of Whitelist ValidationSmarty Pay Token · CertiKAcknowledged

Anyone can call the function `getAirdrop()` multiple times to get `SPY`. Is it necessary to add a whitelist where only the users in it can get airdrops?

The audit on Trustblock · Open the report
HighNo Limitation for `_refer`Smarty Pay Token · CertiKAcknowledged

According to the logic of functions `getAirdrop()`/`tokenSale()`, the input value `_refer` can be set to any accounts. Users can set up different addresses to arbitrage. For example, by setting `_refer` to their different account, they can get several times the `SPY`. Does this fit your design?

The audit on Trustblock · Open the report
LowImproper Usage of `public` and `external` TypeSmarty Pay Token · CertiKAcknowledged

`public` functions that are never called by the contract could be declared as `external`. `external` functions are more efficient than `public` functions.

The audit on Trustblock · Open the report
LowMissing Emit EventsSmarty Pay Token · CertiKAcknowledged

There should always be events emitted in the sensitive functions that are controlled by centralization roles.

The audit on Trustblock · Open the report
LowMissing Error MessagesSmarty Pay Token · CertiKAcknowledged

The **require** can be used to check for conditions and throw an exception if the condition is not met. It is better to provide a string message containing details about the error that will be passed back to the caller.

The audit on Trustblock · Open the report
LowNo Chance To Change AllowanceSmarty Pay Token · CertiKAcknowledged

The linked function, which is implemented inside the `spender` contract, is called when one spender has been approved to spend the `msg.sender`'s tokens. If the `transferFrom()` function is called within the `receiveApproval()` function, there is no chance for `msg.sender` to increase or decrease the allowance.

The audit on Trustblock · Open the report
LowPotential Risk On `approve()`/`transferFrom()` MeSmarty Pay Token · CertiKAcknowledged

Current Token implementation is vulnerable to [a known ERC20 race condition issue](https://github.com/ethereum/EIPs/issues/20#issuecomment-263524729), which could lead to token theft. When a user calls `approve()` for a second time on a spender that has already been allowed, the spender could call `transferFrom()` to transfer the previous value and still receive the authorization to transfer the new value. Exploit scenario: 1. Alice calls `approve(Bob, 100)` to allow Bob to spend 100 tokens. 2. Alice changes her mind and calls `approve(Bob, 50)`. 3. Bob observes the second `approve(Bob, 50)` function call and calls `transferFrom(Alice, Bob, 100)` before the second `approve(Bob, 50)` call. 4. The above scenario can be achieved by front-running. In this case, Bob can transfer another 50 tokens from Alice and in total, he transferred 150 tokens from Alice.

The audit on Trustblock · Open the report
LowUnlocked Compiler VersionSmarty Pay Token · CertiKAcknowledged

The contract has unlocked compiler version. An unlocked compiler version in the source code of the contract permits the user to compile it at or above a particular version. This, in turn, leads to differences in the generated bytecode between compilations due to different compiler versions. This can lead to an ambiguity when debugging as compiler specific bugs may occur in the codebase that would be hard to identify over a span of multiple compiler versions rather than a specific one.

The audit on Trustblock · Open the report
LowVariables That Could Be Declared as ImmutableSmarty Pay Token · CertiKAcknowledged

The linked variables assigned in the constructor can be declared as `immutable`. Immutable state variables can be assigned during contract creation but will remain constant throughout the lifetime of a deployed contract. A big advantage of immutable variables is that reading them is significantly cheaper than reading from regular state variables since they will not be stored in storage.

The audit on Trustblock · Open the report

The Spy-Token.io security record · Every Spy-Token.io address · This address on the explorer