ToDing contract 0x1592…12c0 on BNB Chain

0x1592c5704f9e8c20bf7707c5d42626cecda912c0

As of 21 Nov 2026, Trustblock’s record holds 0x1592c5704f9e8c20bf7707c5d42626cecda912c0 on BNB Chain as a contract of ToDing. 1 audit report on Trustblock lists this address: CertiK, 1 Aug 2024. 6 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
ToDingCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports6

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

HighInitial Token DistributionToDing · CertiKOpen

70% of the `ToDing` tokens are sent to the contract deployer, 30% of the `ToDing` tokens are provided to the DEX pair for liquidity, and all liquidity tokens are subsequently 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 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
LowApproved to send excess tokens to routersToDing · CertiKOpen

In the `startTrade()` function, the contract grants the `_swapRouter` an unlimited allowance: ```solidity=410 function startTrade() external payable onlyOwner { require(0 == startTradeBlock, "trading"); _approve(address(this), address(_swapRouter), ~uint256(0)); ``` Additionally, the `swapToEth()` function explicitly approves the `amount` of tokens to `_swapRouter` each time a token swap is executed: ```solidity=632 function swapToEth(address token, uint256 amount, address to) private { IERC20(token).approve(address(_swapRouter), amount); ``` Since an unlimited approval has already been granted in the `startTrade()` function, this additional approval in `swapToEth()` is redundant.

The audit on Trustblock · Open the report
LowFunction `approve` of Contract `ToDing` Does NotToDing · CertiKOpen

It is expected that calls of the form `approve(spender, amount)` fail if the address in `spender` is the zero address.

The audit on Trustblock · Open the report
LowLack of Error Handling in `_safeTransferETH()` FuToDing · CertiKOpen

The `_safeTransferETH()` function transfers BNB to a `to` address. It uses a low-level `call` to send the specified amount of BNB (`value`). However, the function does not properly handle cases where the `call` operation fails. This lack of error handling can lead to undetected failed transfers. ```solidity=331 function _safeTransferETH(address to, uint value) internal { (bool success, ) = to.call{value: value}(new bytes(0)); if (success) {} } ```

The audit on Trustblock · Open the report
LowUse `.call()` Instead Of `.transfer()`ToDing · CertiKOpen

The `.transfer()` function intends to transfer an ETH amount with a fixed amount of 2300 gas. This function is not equipped to handle changes in the underlying `.transfer()` function which may supply different amounts of gas in the future. Additionally, if the recipient implements a fallback function containing some sort of logic, this may inevitably revert, meaning the vault and owner of the contract will never be able to call certain sensitive functions.

The audit on Trustblock · Open the report
LowVariables That Could Be Declared as ImmutableToDing · CertiKOpen

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 ToDing security record · Every ToDing address · This address on the explorer