0x4ecfb318e6a0ecb81a6f82a269e40487b14a2dbe
As of 21 Nov 2026, Trustblock’s record holds 0x4ecfb318e6a0ecb81a6f82a269e40487b14a2dbe on BNB Chain as a contract of W3binfinity. 1 audit report on Trustblock lists this address: CertiK, 9 Sep 2022. 15 findings in it are recorded as open or acknowledged.
Each report’s scope as stored on Trustblock names this address on BNB Chain.
2 High, 1 Medium, 12 Low. In the firm’s own words; statuses are the firm’s, from each report.
In the contract `WBYToken` the role `owner` has authority over the functions shown in the diagram below. - `setFee()`: Set fees for each transfer. - `setExcludeFee()`: Exclude an address from the fees. - `setMarketingAddress()`: Set the `marketAddress` to receive the fees from transfer. - `multiBlacklist()`: Add multiple addresses to the blacklist of the WBY contract. - `multiRemoveFromBlacklist()`: Remove multiple addresses to the blacklist of the WBY contract. - `wiToken()`: Withdraw all tokens from the contract. - `wiBNB()`: Withdraw all the BNB of the contract `WBYToken`. - `wiAmountBNB()`: Withdraw a certain amount of BNB from the `WBYToken` contract. - `wiAmountToken()` Withdraw any tokens from the contract. - `renounceOwnership()`: Set the owner to the address null. - `transferOwnership()`: Transfer the owner to another address. Any compromise to the `owner` account may allow a hacker to take advantage of this authority and these functions. The attacker will be capable of modifying the **fees functions** or withdrawing all the tokens inside the `WBYToken` contract.
The audit on Trustblock · Open the reportUpon contract deployment, all of the tokens are sent to the contract deployer when deploying the contract. This could be a **centralization risk** as the deployer can distribute the tokens without obtaining the consensus of the community. ```solidity=1257 ERC20._mint(_msgSender(), maxSupply); ```
The audit on Trustblock · Open the reportThe `fee` is set to 100% by default. This could lead to unexpected behavior. ```solidity=1247 uint256 fee = 100; ``` In this case, the action will disable the `transfer` function and thus **freeze** the contract until the `owner` decreases the value of the `fee`. Otherwise, there is no explicit restriction on the upper limit of the fee. Therefore, mistakenly setting the fee to 100 might lead to a Denial-of-Service situation. The auditors would like to know if this is the intended schema of the fee mechanism.
The audit on Trustblock · Open the reportThere following code is *unused* inside the contract, and this could impact the readability of the contract. Additionally, the unused functions might introduce vulnerabilities in the future upgrade of the contract if the code is forgotten. - `_mint(address,uint256)`
The audit on Trustblock · Open the reportThe functions which are never called internally within the contract should have external visibility for gas optimization. The following functions are declared as `public`: - `renounceOwnership()` - `transferOwnership()` - `name()` - `symbol()` - `decimals()` - `transfer()` - `approve()` - `transferFrom()` - `increaseAllowance()` - `decreaseAllowance()` - `burn()` - `burnFrom()`
The audit on Trustblock · Open the reportThe function that affects the status of sensitive variables should be able to emit events as notifications. - `function setFee(uint256 _fee)`
The audit on Trustblock · Open the reportThere is no `receive()` or `fallback()` function in the `WBYToken.sol`,then this contract cannot receive any native token(BNB). However, the contract has the following functions that are designed to withdraw native tokens to the owner: - `wiBNB()` - `WiAmountBNB()` In this case, without a valid fallback function, these functions will not be capable to send any native token(BNB) because the **balance** of the native tokens will be **empty** forever.
The audit on Trustblock · Open the reportAddresses should be checked before assignment or external call to make sure they are not zero addresses. The following functions are concerned : - `setMarketingAddress()`
The audit on Trustblock · Open the reportState variables that never change should be declared as `constant` to save gas. ```solidity=1245 uint256 maxSupply = 1000000000*10 ** 18; ``` - `maxSupply` should be declared `constant`.
The audit on Trustblock · Open the reportThe return value of the transfer()/transferFrom() call is not checked. ```solidity=1315 IERC20(token).transfer(msg.sender, IERC20(token).balanceOf(address(this))); ``` --- ```solidity=1327 IERC20(token).transfer(msg.sender, amount); ```
The audit on Trustblock · Open the reportContracts should be deployed using the same compiler version/flags with which they have been tested. Locking the pragma (e.g. by not using ^ in pragma solidity 0.8.4) ensures that contracts do not accidentally get deployed using a compiler version with unfixed bugs. Reference: [SWC-103] https://swcregistry.io/docs/SWC-103
The audit on Trustblock · Open the report```solidity=335 library Address { ``` - The library `Address` is declared but never used.
The audit on Trustblock · Open the reportThe variables `lpAddresses` & `router` are declared but the current code logic **don't use** these variables. Moreover removing *unused variables* will **improve** gas consumption. ```solidity=1244 mapping(address => bool) lpAddresses; ``` ```solidity=1237 IPancakeSwapRouter public router; ```
The audit on Trustblock · Open the report`block.timestamp` is used for comparison, which can be risky since timestamp can be influenced by miners. That means the miner creating the block can manipulate the `block.timestamp`, to some degree, and change the outcome of the transaction. ```solidity=1300 require(block.timestamp <= blacklistTime, "blacklistTime: invalid"); ```
The audit on Trustblock · Open the reportThe 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. ```solidity=1239 uint public blacklistTime; ```
The audit on Trustblock · Open the reportThe W3binfinity security record · Every W3binfinity address · This address on the explorer