Pige Inu contract 0x1fdb…49e2 on BNB Chain

0x1fdb2c3851d067502ce2122be80a41ea212949e2

As of 21 Nov 2026, Trustblock’s record holds 0x1fdb2c3851d067502ce2122be80a41ea212949e2 on BNB Chain as a contract of Pige Inu. 1 audit report on Trustblock lists this address: CertiK, 26 Aug 2022. 13 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
Pige InuCertiKNot recorded (see the report)Open

Open and acknowledged findings in these reports13

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

HighCentralized risk in `swapAndLiquify`Pige Inu · CertiKAcknowledged

The `swapAndLiquify` function calls the `sendToWallet` function to transfer BNB to `Wallet_Marketing/Wallet_Dev`. As a result, over time these two addresses will accumulate a significant portion of BNB. And they are EOA (Externally Owned Account), mishandling its private key can have devastating consequences for the project as a whole.

The audit on Trustblock · Open the report
HighInitial Token DistributionPige Inu · CertiKAcknowledged

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

The audit on Trustblock · Open the report
MediumContract gains non-withdrawable BNB via the `swapPige Inu · CertiKAcknowledged

The `swapAndLiquify` function converts half of the `Percent_AutoLP` PINU tokens to BNB. The other half of PINU tokens and part of the converted BNB are deposited into the PINU-BNB pool on Pancakeswap as liquidity. For every `swapAndLiquify` function call, a small amount of BNB is leftover in the contract. This is because the price of PINU drops after swapping the first half of PINU tokens into BNBs, and the other half of PINU tokens require less than the converted BNB to be paired with it when adding liquidity. The contract doesn't appear to provide a way to withdraw those BNB, and they will be locked in the contract forever.

The audit on Trustblock · Open the report
MediumLogical issue in the `_tokenTransfer()`Pige Inu · CertiKAcknowledged

In the function `_tokenTransfer()`, if the user buys tokens from DEX, a buyFEE will be taken. Otherwise, a sellFEE will be taken. However, if the user transfers tokens to another user, it's not a buy or a sell. The contract should not charge buy/sell fee in this case.

The audit on Trustblock · Open the report
LowImproper Usage of `public` and `external` TypePige Inu · CertiKOpen

`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
LowPotential Sandwich AttacksPige Inu · CertiKOpen

A sandwich attack might happen when an attacker observes a transaction swapping tokens or adding liquidity without setting restrictions on slippage or minimum output amount. The attacker can manipulate the exchange rate by front-running (before the transaction is attacked) a transaction to purchase one of the assets and make profits by back-running (after the transaction is 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: - `uniswapV2Router.swapExactTokensForETHSupportingFeeOnTransferTokens()` - `uniswapV2Router.addLiquidityETH()`

The audit on Trustblock · Open the report
LowRedundant Code ComponentsPige Inu · CertiKOpen

The `PIGEINU` contract will set the EOA `0xA4b0588Df297921eF93fDa96979Bf0Db97E2F0df` as `_owner` in its constructor. However, the owner role has no privileges on any specific functions. The `onlyOwner` modifier is never used. Additionally, anyone can call the `renounceOwnership` function. This function is supposed to be restricted, only used by the owner. It seems all these related codes are redundant. ```solidity function owner() public view virtual returns (address) { return _owner; } modifier onlyOwner() { require(owner() == _msgSender(), "Ownable: caller is not the owner"); _; } function renounceOwnership() public virtual { emit OwnershipTransferred(_owner, address(0)); _owner = address(0); } constructor () { _owner = 0xA4b0588Df297921eF93fDa96979Bf0Db97E2F0df; emit OwnershipTransferred(address(0), _owner); ... } ``` Another redundant code in the contract: ```solidity function _getCurrentSupply() private view returns(uint256) { return (_tTotal); } ``` Another redundant code in the contract: ```solidity uint256 public Percent_Burn = 0; uint256 tokens_to_Burn = contractTokenBalance * Percent_Burn / 100; _tTotal = _tTotal - tokens_to_Burn; _tOwned[Wallet_Burn] = _tOwned[Wallet_Burn] + tokens_to_Burn; _tOwned[address(this)] = _tOwned[address(this)] - tokens_to_Burn; ```

The audit on Trustblock · Open the report
LowThird Party DependencyPige Inu · CertiKOpen

The contract is serving as the underlying entity to interact with one or more third-party protocols. The scope of the audit treats third-party entities as black boxes and assumes their functional correctness. However, in the real world, third parties can be compromised and this may lead to lost or stolen assets. In addition, upgrades of third parties can possibly create severe impacts, such as increasing fees of third parties, migrating to new LP pools, etc. ```solidity=381 IUniswapV2Router02 public uniswapV2Router; ``` - The contract `PIGEINU` interacts with third-party contract with `IUniswapV2Router02` interface via `uniswapV2Router`.

The audit on Trustblock · Open the report
LowUnnecessary Use of SafeMathPige Inu · CertiKOpen

The `SafeMath` library is used unnecessarily. With Solidity compiler versions 0.8.0 or newer, arithmetic operations will automatically revert in case of integer overflow or underflow. ```solidity=17 library SafeMath { ``` - An implementation of `SafeMath` library is found. --- ```solidity=327 using SafeMath for uint256; ``` - `SafeMath` library is used for `uint256` type in `PIGEINU` contract. ```solidity=459 _approve(sender, _msgSender(), _allowances[sender][_msgSender()].sub(amount, "ERC20: transfer amount exceeds allowance")); ``` - `SafeMath.sub` is called in `transferFrom` function of `PIGEINU` contract. *Note: Only a sample of 2 `SafeMath` library usage in this contract (out of 4) are shown above.*

The audit on Trustblock · Open the report
LowUnused State VariablePige Inu · CertiKOpen

One or more state variables are never used in the codebase. Variable `MAX` in `PIGEINU` is never used in `PIGEINU`. ```solidity=357 uint256 private constant MAX = ~uint256(0); ``` ```solidity=326 contract PIGEINU is Context, IERC20 { ``` --- Variable `_previousMaxWalletToken` in `PIGEINU` is never used in `PIGEINU`. ```solidity=375 uint256 private _previousMaxWalletToken = _maxWalletToken; ``` ```solidity=326 contract PIGEINU is Context, IERC20 { ``` --- Variable `_previousMaxTxAmount` in `PIGEINU` is never used in `PIGEINU`. ```solidity=378 uint256 private _previousMaxTxAmount = _maxTxAmount; ``` ```solidity=326 contract PIGEINU is Context, IERC20 { ```

The audit on Trustblock · Open the report
LowUsage of `transfer`/`send` for sending EtherPige Inu · CertiKOpen

It is not recommended to use Solidity's `transfer()` and `send()` functions for transferring Ether, since some contracts may not be able to receive the funds. Those functions forward only a fixed amount of gas (2300 specifically) and the receiving contracts may run out of gas before finishing the transfer. Also, EVM instructions' gas costs may increase in the future. Thus, some contracts that can receive now may stop working in the future due to the gas limitation. ```solidity=543 wallet.transfer(amount); ``` - `PIGEINU.sendToWallet` uses `transfer()`.

The audit on Trustblock · Open the report
LowVariables That Could Be Declared as `constant`Pige Inu · CertiKOpen

The linked variables could be declared as `constant` since these state variables are never modified.

The audit on Trustblock · Open the report
LowVariables That Could Be Declared as ImmutablePige Inu · 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 Pige Inu security record · Every Pige Inu address · This address on the explorer