Real Smurf Cat contract 0xff83…240c on Ethereum

0xff836a5821e69066c87e268bc51b849fab94240c

As of 21 Nov 2026, Trustblock’s record holds 0xff836a5821e69066c87e268bc51b849fab94240c on Ethereum as a contract of Real Smurf Cat. 1 audit report on Trustblock lists this address: CertiK, 29 Jul 2024. 3 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 Ethereum.

AuditSecurity firmDateCommit named in the reportReport
Real Smurf CatCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports3

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

HighInitial Token DistributionReal Smurf Cat · CertiKOpen

**Important Note**: Certain identification and KYC procedures were attempted to be applied to the project team in order to better understand the centralization situation and potential risks of the project. Based on the collected information and further conducted investigation, the project failed to pass the criteria with a certain amount of negative signals. Thus the case analysis concluded that there is potential high risk to the project. We strongly advise end users to conduct further research and exercise due diligence before engaging with the project. It is crucial for end users to independently verify and assess all available information to make informed decisions. All of the `Real Smurf Cat` tokens are sent to the contract deployer or one or several externally-owned account (EOA) addresses. This is a centralization risk because the deployer or the owner(s) of the EOAs can distribute tokens without obtaining the consensus of the community. Any compromise to these addresses 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 report
LowFunction Fails on Valid InputsReal Smurf Cat · CertiKAcknowledged

It is expected that invocations of `transferFrom(from, dest, amount)` succeed and return `true` if * the value of `amount` does not exceed the balance of address `from`, * the value of `amount` does not exceed the allowance of `msg.sender` for address `from`, * transferring a value of `amount` to the address in `dest` does not lead to an overflow of the recipient's balance, and * the supplied gas suffices to complete the call. Nevertheless, the `transferFrom` function of `SmurfCat` fails in some of those valid cases. It is expected that invocations of the form `transfer(recipient, amount)` succeed and return `true` if * The address in `recipient` is not the zero address, * `amount` does not exceed the balance of address `msg.sender`, * transferring `amount` to the address `recipient` does not lead to an overflow of the recipient's balance, and * the supplied gas suffices to complete the call. Nevertheless, the `transfer` function of `SmurfCat` fails in some of those valid cases.

The audit on Trustblock · Open the report
LowMissing Zero Address ValidationReal Smurf Cat · CertiKAcknowledged

Addresses are not validated before assignment or external calls, potentially allowing the use of zero addresses and leading to unexpected behavior or vulnerabilities. For example, transferring tokens to a zero address can result in a permanent loss of those tokens. ```solidity=611 uniswapV2Pair = _uniswapV2Pair; ``` - `_uniswapV2Pair` is not zero-checked before being used. If `uniswapV2Pair` is reset to 0, then the trading will be stopped unless the transfer is from or to `owner` address.

The audit on Trustblock · Open the report

The Real Smurf Cat security record · Every Real Smurf Cat address · This address on the explorer