Pongo Inu
Smart Contract Audit Report
Audit Summary
Pongo Inu is a new ERC-20 token on Ethereum that pays out static rewards to holders.
For this audit, we reviewed the project team's PONGO contract at 0x73e14D83f0F107e0Ac02131567AdE0BedB55A10E on the Ethereum Mainnet.
Audit Findings
Date: March 9th, 2022.
Finding #1 - PONGO - Informational
Description: Several functions are declared public, but are never called internally.Recommendation: These functions should be declared external for additional gas savings on each call.name, symbol, decimals, totalSupply, transfer, allowance, approve, transferFrom, setSwapAndLiquifyEnabled, setMaxTxAmount, setMaxWalletAmount, addBot, delBotFinding #2 - PONGO - Informational
Description: The_swapTokensAtAmountstate variable can never be modified but is not declared constant
Recommendation: This state variable can be declared constant for additional gas savings on each reference and to reduce deployment costs.Finding #3 - PONGO - Informational
Description: Although the SafeMath library is utilized, the contract is deployed with Solidity v0.8.9 which has built-in overflow checks.
Recommendation: SafeMath could be safely removed to reduce contract size and deployment costs.
Contract Overview
Ownership Controls:
- The total supply of the token is set to 100 trillion $PONGO [100,000,000,000,000].
- No mint or burn functions exist, though the circulating supply can be decreased by sending tokens to the 0x..dead address.
- At the time of writing this report, there are 706 total token holders. The token allocation is as follows:
- 11.02% of the total supply is in Uniswap liquidity.
- Of that liquidity, 100% of the LP tokens are stored in the SNAP! Liquidity Pools contract and will vest to the team on August 15th, 2022.
- 5.56% of the total supply belongs to the team's Treasury wallet.
- The next five holders own a cumulative 15.93% of the total supply.
- There is a 4% Tax fee and an 8% Team fee on all transfers (not involving the owner) where the sender is not the contract address.
- The tokens collected through the Tax fee are removed from the circulating supply; This serves as a frictionless fee redistribution which automatically benefits all token holders at the time of each transaction.
- The tokens collected through the Team fee are stored in the contract address. The tokens are swapped for ETH when the following conditions are met:
- The automatic token swapping functionality is enabled by the team.
- The threshold number of 100 billion tokens in the contract address has been reached.
- The contract is not currently swapping tokens for ETH.
- The sender is not the Uniswap Pair address.
- The ETH received through this process is split between two Fee wallets controlled by the team.
- The contract enforces a maximum transaction amount which imposes a limit to the number of tokens that can be bought via Uniswap during any given transaction.
- The contract enforces a maximum wallet amount that prevents a transfer from occurring if the recipient's token balance will exceed the limit number of tokens after the transfer occurs.
- The contract utilizes a Cooldown mechanism that prevents accounts from buying tokens more than once every 30 seconds.
- The contract features an Antisniper mechanism that is triggered when a user attempts to buy tokens within 3 blocks of trading being enabled. The account initiating the transfer will be taxed at a 100% rate.
- As the contract is deployed with Solidity v0.8.12, it is protected from overflows/underflows.
- The contract complies with the ERC-20 token standard.
- Ownership has been renounced.
- The owner was previously able to add/remove accounts from a blacklist which prevents them from being able to participate in transfers.
- The owner was previously able to update the maximum transaction amount to any value at any time.
- The owner was previously able to update the maximum wallet amount to any value at any time.
- The owner was previously able to enable/disable the automatic token swapping functionality at any time.
- The owner was previously able to enable/disable the Cooldown mechanism at any time.
- The team's Fee wallet can manually swap the tokens in the contract address for ETH and send it to their own wallet at any time.
Audit Results
| Vulnerability Category | Notes | Result |
|---|---|---|
| Arbitrary Jump/Storage Write | N/A | PASS |
| Centralization of Control | N/A | PASS |
| Compiler Issues | N/A | PASS |
| Delegate Call to Untrusted Contract | N/A | PASS |
| Dependence on Predictable Variables | N/A | PASS |
| Ether/Token Theft | N/A | PASS |
| Flash Loans | N/A | PASS |
| Front Running | N/A | PASS |
| Improper Events | N/A | PASS |
| Improper Authorization Scheme | N/A | PASS |
| Integer Over/Underflow | N/A | PASS |
| Logical Issues | N/A | PASS |
| Oracle Issues | N/A | PASS |
| Outdated Compiler Version | N/A | PASS |
| Race Conditions | N/A | PASS |
| Reentrancy | N/A | PASS |
| Signature Issues | N/A | PASS |
| Unbounded Loops | N/A | PASS |
| Unused Code | N/A | PASS |
| Overall Contract Safety | PASS |
Inheritance Chart
Function Graph

Functions Overview
($) = payable function
# = non-constant function
Int = Internal
Ext = External
Pub = Public
+ Context
- [Int] _msgSender
+ [Int] IERC20
- [Ext] totalSupply
- [Ext] balanceOf
- [Ext] transfer #
- [Ext] allowance
- [Ext] approve #
- [Ext] transferFrom #
+ [Lib] SafeMath
- [Int] add
- [Int] sub
- [Int] sub
- [Int] mul
- [Int] div
- [Int] div
+ Ownable (Context)
- [Pub] #
- [Pub] owner
- [Pub] renounceOwnership #
- modifiers: onlyOwner
+ [Int] IUniswapV2Factory
- [Ext] createPair #
+ [Int] IUniswapV2Router02
- [Ext] swapExactTokensForETHSupportingFeeOnTransferTokens #
- [Ext] factory
- [Ext] WETH
- [Ext] addLiquidityETH ($)
+ PONGO (Context, IERC20, Ownable)
- [Pub] #
- [Pub] name
- [Pub] symbol
- [Pub] decimals
- [Pub] totalSupply
- [Pub] balanceOf
- [Pub] transfer #
- [Pub] allowance
- [Pub] approve #
- [Pub] transferFrom #
- [Ext] setCooldownEnabled #
- modifiers: onlyOwner
- [Prv] tokenFromReflection
- [Prv] _approve #
- [Prv] _transfer #
- [Pub] swapAndLiquifyEnabled #
- modifiers: onlyOwner
- [Prv] swapTokensForEth #
- modifiers: lockTheSwap
- [Prv] sendETHToFee #
- [Pub] setMaxTxAmount #
- modifiers: onlyOwner
- [Pub] setMaxWalletAmount #
- modifiers: onlyOwner
- [Ext] openTrading #
- modifiers: onlyOwner
- [Pub] addBot #
- modifiers: onlyOwner
- [Pub] delBot #
- modifiers: onlyOwner
- [Prv] _tokenTransfer #
- [Prv] _transferStandard #
- [Prv] _takeTeam #
- [Prv] _reflectFee #
- [Ext] ($)
- [Ext] manualSwap #
- [Ext] manualSend #
- [Prv] _getValues
- [Prv] _getTValues
- [Prv] _getRValues
- [Prv] _getRate
- [Prv] _getCurrentSupply About SourceHat
SourceHat has quickly grown to have one of the most experienced and well-equipped smart contract auditing teams in the industry. Our team has conducted 1800+ solidity smart contract audits covering all major project types and protocols, securing a total of over $50 billion U.S. dollars in on-chain value!
Our firm is well-reputed in the community and is trusted as a top smart contract auditing company for the review of solidity code, no matter how complex. Our team of experienced solidity smart contract auditors performs audits for tokens, NFTs, crowdsales, marketplaces, gambling games, financial protocols, and more!
Contact us today to get a free quote for a smart contract audit of your project!
What is a SourceHat Audit?
Typically, a smart contract audit is a comprehensive review process designed to discover logical errors, security vulnerabilities, and optimization opportunities within code. A SourceHat Audit takes this a step further by verifying economic logic to ensure the stability of smart contracts and highlighting privileged functionality to create a report that is easy to understand for developers and community members alike.
How Do I Interpret the Findings?
Each of our Findings will be labeled with a Severity level. We always recommend the team resolve High, Medium, and Low severity findings prior to deploying the code to the mainnet. Here is a breakdown on what each Severity level means for the project:
- High severity indicates that the issue puts a large number of users' funds at risk and has a high probability of exploitation, or the smart contract contains serious logical issues which can prevent the code from operating as intended.
- Medium severity issues are those which place at least some users' funds at risk and has a medium to high probability of exploitation.
- Low severity issues have a relatively minor risk association; these issues have a low probability of occurring or may have a minimal impact.
- Informational issues pose no immediate risk, but inform the project team of opportunities for gas optimizations and following smart contract security best practices.