0xebdba914eb214fbf7ab1acd02563da43831ad0a4
As of 21 Nov 2026, Trustblock’s record holds 0xebdba914eb214fbf7ab1acd02563da43831ad0a4 on BNB Chain as a contract of POP Coin. 1 audit report on Trustblock lists this address: CertiK, 7 Jun 2023. 15 findings in it are recorded as open or acknowledged.
Each report’s scope as stored on Trustblock names this address on BNB Chain.
| Audit | Security firm | Date | Commit named in the report | Report |
|---|---|---|---|---|
| POP Coin - Audit | CertiK | Not recorded (see the report) | Open |
1 High, 2 Medium, 12 Low. In the firm’s own words; statuses are the firm’s, from each report.
All `POP` tokens are sent to the contract deployer when deploying the contract. This is a potential centralization risk as the deployer can distribute `POP` tokens without the consensus of the community. The detailed holder list can be found at: [https://bscscan.com/token/0xebdba914eb214fbf7ab1acd02563da43831ad0a4#balances](https://bscscan.com/token/0xebdba914eb214fbf7ab1acd02563da43831ad0a4#balances). As of 06/05/2023, the addresses of major holders are listed below: - 7.6% of the total supplied tokens are in the liquidity pool address [PancakeSwap V2: POP 163](https://bscscan.com/address/0x33d028ed46f615e233751809afee5f8600238494) - 3.31% of the tokens are in the address [0xd6A07b8065f9e8386A9a5bBA6A754a10A9CD1074](https://bscscan.com/address/0xd6a07b8065f9e8386a9a5bba6a754a10a9cd1074) - 1.88% of the tokens are in the address [0xaADe82Bcf5711e92a76C8a8c2f8efd5E7E1CeD6b](https://bscscan.com/address/0xaade82bcf5711e92a76c8a8c2f8efd5e7e1ced6b)
The audit on Trustblock · Open the reportThe `PopCoin` contract relies on `POP-WBNB` trading pair for swapping. In the function `swapAndLiquify()`, the `POP` balance of this contract is swapped for `BNB` which then will be transferred to `marketingWallet` address. ```solidity=494 function swapAndLiquify() private lockTheSwap { uint256 contractBalance = balanceOf(address(this)); swapTokensForBNB(contractBalance); uint256 deltaBalance = address(this).balance; if (deltaBalance > 0) { payable(marketingWallet).sendValue(deltaBalance); } } ``` The `swapAndLiquidify()` function only makes a call to `swapTokensForBNB()` to exchange tokens for native tokens through the router. ```solidity=506 function swapTokensForBNB(uint256 tokenAmount) private { // generate the pair path of token -> weth address[] memory path = new address[](2); path[0] = address(this); path[1] = router.WETH(); _approve(address(this), address(router), tokenAmount); // make the swap router.swapExactTokensForETHSupportingFeeOnTransferTokens( tokenAmount, 0, // accept any amount of ETH path, address(this), block.timestamp ); } ``` However, there is no logic to liquify tokens in this function `swapAndLiquify()`. This can lead to risks related to price instability and price manipulation when there is insufficient liquidity in the pair liquidity pool. The only way of adding liquidity is to manually inject liquidity into the DEX liquidity pool. Once the liquidity is removed, the trading of `POP` will be blocked.
The audit on Trustblock · Open the reportVariable `_rOwned[account]` is not updated in the function `includeInReward()`, which will make the accounts included in the token amount distributions made to all eligible token holders based on proportional ownership. ```solidity=301 function includeInReward(address account) external onlyOwner { require(_isExcluded[account], "Account is not excluded"); for (uint256 i = 0; i < _excluded.length; i++) { if (_excluded[i] == account) { _excluded[i] = _excluded[_excluded.length - 1]; _tOwned[account] = 0; _isExcluded[account] = false; _excluded.pop(); break; } } } ``` In the case that the rate was higher at the moment of the `excludeFromReward(account)` call, the `_rOwned[account] / _tOwned[account]` ratio will be unintentionally increased for all accounts included in rewards when excluded accounts are included back in rewards. As of 06/05/2023, the ownership has been renounced in the transaction [0x9bf98a3a30ade327bad5054fa5d678599925caa191aab55375c811fa762c0f6a](https://bscscan.com/tx/0x9bf98a3a30ade327bad5054fa5d678599925caa191aab55375c811fa762c0f6a). The `includeInReward()` function is no longer executable, but the issue is still present in the code.
The audit on Trustblock · Open the reportIn function `transferFrom()`, the `_transfer()` function is executed before checks and updates to the allowance are processed. ```solidity=230 function transferFrom( address sender, address recipient, uint256 amount ) public override returns (bool) { _transfer(sender, recipient, amount); uint256 currentAllowance = _allowances[sender][_msgSender()]; require(currentAllowance >= amount, "BEP20: transfer amount exceeds allowance"); _approve(sender, _msgSender(), currentAllowance - amount); return true; } ``` This violates the check-effect-interaction pattern and should follow the checks and updates of the allowances. An added benefit is that having the allowance check `require(currentAllowance >= amount, "BEP20: transfer amount exceeds allowance")` before the execution of the `_transfer()` function (or any checks in general before such external function calls) will save gas since all remaining gas will be returned after the function reverts immediately due to insufficient gas.
The audit on Trustblock · Open the reportCurrently the `owner()` and `marketingWallet` are excluded from fees but there is no mechanism in place to handle these privileges when ownership is transferred or renounced. ```solidity constructor(address routerAddress) { IRouter _router = IRouter(routerAddress); address _pair = IFactory(_router.factory()).createPair(address(this), _router.WETH()); router = _router; pair = _pair; excludeFromReward(pair); excludeFromReward(deadWallet); _rOwned[owner()] = _rTotal; _isExcludedFromFee[address(this)] = true; _isExcludedFromFee[owner()] = true; // Issue: Owner account is excluded from fees _isExcludedFromFee[marketingWallet] = true; // Issue: Marketing wallet is excluded from fees _isExcludedFromFee[deadWallet] = true; emit Transfer(address(0), owner(), _tTotal); } ``` Proper changes to the exclusion of fees can still be managed when ownership is transferred, however an issue arises especially in the case of the renouncing of ownership. There is no way to remove the privilege of exclusion from fees for the previous owner if he/she does not remove the exclusion prior to renouncing of ownership.
The audit on Trustblock · Open the reportOne or more parameters with `memory` data location are never modified in their functions and those functions are never called internally within the contract. Thus, their data location can be changed to `calldata` to avoid the gas consumption copying from calldata to memory. ```solidity=530 function changeFee(Taxes memory _taxes) public onlyOwner { ``` `changeFee` has memory location parameters: `_taxes`.
The audit on Trustblock · Open the reportThere should always be events emitted in the sensitive functions that are controlled by centralized roles.
The audit on Trustblock · Open the reportAddresses 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=536 marketingWallet = _marketWallet; ``` - `_marketWallet` is not zero-checked before being used.
The audit on Trustblock · Open the reportThere is a potential `out-of-gas` issue in function `includeInReward()` since it uses a loop to iterate over `_excluded`, which could potentially result in a high amount of gas consumption. If `_excluded` contains a large number of elements, the loop may consume more gas than is available in a single block. This would cause the transaction to fail with the "out-of-gas" error. ```solidity=303 for (uint256 i = 0; i < _excluded.length; i++) { if (_excluded[i] == account) { _excluded[i] = _excluded[_excluded.length - 1]; _tOwned[account] = 0; _isExcluded[account] = false; _excluded.pop(); break; } } ```
The audit on Trustblock · Open the reportIn a reflection mechanism, users are charged a fee every time they make a trade. This fee is used to reward users who hold tokens, but it does not trigger a transfer of tokens. Instead, it only modifies a coefficient. In this mechanism, the user possesses two types of token amounts: `tAmount` and `rAmount`. `tAmount` represents the actual amount of tokens, while `rAmount` denotes the number of tokens after reflection. The rate between the two is calculated as $$$\frac{rTotal}{tTotal}$$$. The `balanceOf()` function returns the `tAmount` or `rAmount` depending on whether the address is participating in the reflection. ```solidity=216 function balanceOf(address account) public view override returns (uint256) { if (_isExcluded[account]) return _tOwned[account]; return tokenFromReflection(_rOwned[account]); } ``` The function `tokenFromReflection()` returns the token amount after the rate of reflection is taken into account. ```solidity=285 function tokenFromReflection(uint256 rAmount) public view returns (uint256) { require(rAmount <= _rTotal, "Amount must be less than total reflections"); uint256 currentRate = _getRate(); return rAmount / currentRate; } ``` In the `PopCoin` contract, the `rfi` fee is used for the reflection mechanism, which is utilized to decrease the `_rTotal` and subsequently reduce the `rate`. This results in the inflation of the holders' balances through the distribution of rewards. ```solidity=326 function _reflectRfi(uint256 rRfi, uint256 tRfi) private { _rTotal -= rRfi; totFeesPaid.rfi += tRfi; } ``` However, the `rfi` fee can be updated by the owner and set to any value less than 15%. If it is set to zero, then `_rTotal` will not be decreased anymore, and in this case, there will be no reflection mechanism. ```solidity=530 function changeFee(Taxes memory _taxes) public onlyOwner { require((_taxes.rfi + _taxes.marketing) <= 15, "Tax must lower than 15%"); taxes = _taxes; } ```
The audit on Trustblock · Open the reportA sandwich attack might happen when an attacker observes a transaction swapping tokens or adding liquidity without set restrictions on the slippage or minimum output amount. The attacker can manipulate the exchange rate by frontrunning (executing a transaction before the transaction being attacked) a transaction to purchase one of the assets and make profits by backrunning (executing a transaction after the transaction being attacked) a transaction to sell the asset. The following functions are called without setting restrictions on slippage or minimum output amount, so transactions triggering these functions are vulnerable to sandwich attacks, especially when the input amount is large: * `router.swapExactTokensForETHSupportingFeeOnTransferTokens()` ```solidity=515 router.swapExactTokensForETHSupportingFeeOnTransferTokens( tokenAmount, 0, // accept any amount of ETH path, address(this), block.timestamp ); ```
The audit on Trustblock · Open the reportState variables that never change should be declared as `constant` to save gas. ```solidity=139 uint256 private _tTotal = 210000000000000000 * 10**_decimals; ``` - `_tTotal` should be declared `constant`. --- ```solidity=144 address public deadWallet = 0x000000000000000000000000000000000000dEaD; ``` - `deadWallet` should be declared `constant`.
The audit on Trustblock · Open the reportLiterals with many digits are difficult to read and review. ```solidity=139 uint256 private _tTotal = 210000000000000000 * 10**_decimals; ```
The audit on Trustblock · Open the reportThe contract cited has an 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 differing compiler version numbers. This can lead to 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 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.
The audit on Trustblock · Open the reportThe POP Coin security record · Every POP Coin address · This address on the explorer