Space Alpaca

Smart Contract Audit Report

Audit Summary

Space Alpaca is a new BEP-20 token on the Binance Smart Chain.

For this audit, we reviewed the project team's SPAL contract at 0x80cf46413abb802599cbabc1a509aecbc2696f4c on the Binance Smart Chain Mainnet.

Audit Findings

Informational findings were identified and the team may want to review them. In addition, some centralized aspects are present.
Date: September 20, 2023.

Finding #1 - SPAL - Informational

Description: There are three instances in the sellBurnedTokens() function where multiplication is performed on the result of a division. Division can lead to integer truncation, therefore dividing and subsequently multiplying can cause results to lose precision and become less accurate.
spentAmount = contractTokenBalance / totFee * _marketingFee;
...
spentAmount = contractTokenBalance / totFee * _buybackFee;
...
spentAmount = contractTokenBalance / totFee * _liquidityFee;
Recommendation: We recommend modifying these calculations to perform all multiplication before division.

Finding #2 - SPAL - Informational

Description: The private swapBNBForTokens() function is never called in the contract.
Recommendation: The above function should either be removed to reduce contract size and deployment costs or utilized in a way that fits the project team's intended functionality.

Contract Overview

  • The total supply of the token is set to zero upon deployment.
  • No mint or burn functions are publicly accessible, though the circulating supply can be decreased by sending tokens to the 0x..dead address.
  • Any user can initiate a token migration by specifying a number of their SPAL legacy tokens that will be transferred to the 0x..dead address. The caller must grant the contract a sufficient allowance in order for the transaction to successfully occur. In return, the user is minted an equivalent amount of $SPAL tokens, and the total supply is increased.

  • There is a Liquidity fee, Marketing fee, and Buyback fee on all sells via Pancakeswap.
  • The tokens collected through fees are stored in the contract address. The owner can manually trigger the distribution of fees and execute a liquidity add at any time.
  • Liquidity-adds are performed by selling the tokens collected as fees, pairing the received BNB with the token, and adding it as liquidity to the pair.
  • The LP tokens received through this process are sent to the 0x..dead address.
  • The tokens collected through the Marketing fee are swapped for BNB and sent to the team's Marketing wallet.
  • The tokens collected through the Buyback fee are swapped for BNB and sent to the team's Buyback wallet.
  • As the contract is deployed with Solidity v0.8.18, it is protected from overflows/underflows.
  • The contract complies with the BEP-20 token standard.
  • The owner can set the Liquidity fee, Marketing fee, and Buyback fee to any percentages as long as the total combined fee percentage does not exceed 12% at any time.
  • The owner can set the team's Marketing wallet and Buyback wallet to any addresses 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
Sybil Attack N/A PASS
Unbounded Loops N/A PASS
Unused Code N/A PASS
Overall Contract Safety   PASS

Inheritance Chart

Smart Contract Audit - Inheritance

Function Graph

Smart Contract Audit - Graph

Functions Overview


 ($) = payable function
 # = non-constant function
 
 Int = Internal
 Ext = External
 Pub = Public

 +  Context 
    - [Int] _msgSender
    - [Int] _msgData

 +  Ownable (Context)
    - [Pub]  #
    - [Pub] owner
    - [Pub] transferOwnership #
       - modifiers: onlyOwner
    - [Int] _transferOwnership #

 + [Int] IUniswapV2Router01 
    - [Ext] factory
    - [Ext] WETH
    - [Ext] addLiquidity #
    - [Ext] addLiquidityETH ($)
    - [Ext] removeLiquidity #
    - [Ext] removeLiquidityETH #
    - [Ext] removeLiquidityWithPermit #
    - [Ext] removeLiquidityETHWithPermit #
    - [Ext] swapExactTokensForTokens #
    - [Ext] swapTokensForExactTokens #
    - [Ext] swapExactETHForTokens ($)
    - [Ext] swapTokensForExactETH #
    - [Ext] swapExactTokensForETH #
    - [Ext] swapETHForExactTokens ($)
    - [Ext] quote
    - [Ext] getAmountOut
    - [Ext] getAmountIn
    - [Ext] getAmountsOut
    - [Ext] getAmountsIn

 + [Int] IERC20 
    - [Ext] name
    - [Ext] symbol
    - [Ext] decimals
    - [Ext] totalSupply
    - [Ext] balanceOf
    - [Ext] allowance
    - [Ext] approve #
    - [Ext] transfer #
    - [Ext] transferFrom #

 + [Int] IUniswapV2Factory 
    - [Ext] feeTo
    - [Ext] feeToSetter
    - [Ext] getPair
    - [Ext] allPairs
    - [Ext] allPairsLength
    - [Ext] createPair #
    - [Ext] setFeeTo #
    - [Ext] setFeeToSetter #

 + [Int] IUniswapV2Router02 (IUniswapV2Router01)
    - [Ext] removeLiquidityETHSupportingFeeOnTransferTokens #
    - [Ext] removeLiquidityETHWithPermitSupportingFeeOnTransferTokens #
    - [Ext] swapExactTokensForTokensSupportingFeeOnTransferTokens #
    - [Ext] swapExactETHForTokensSupportingFeeOnTransferTokens ($)
    - [Ext] swapExactTokensForETHSupportingFeeOnTransferTokens #

 +  SPAL (IERC20, Ownable)
    - [Pub]  #
    - [Pub] totalSupply
    - [Pub] balanceOf
    - [Pub] transfer #
    - [Pub] allowance
    - [Pub] approve #
    - [Pub] transferFrom #
    - [Pub] increaseAllowance #
    - [Pub] decreaseAllowance #
    - [Ext] setAllFeePercent #
       - modifiers: onlyOwner
    - [Ext] setFeeWallet #
       - modifiers: onlyOwner
    - [Ext]  ($)
    - [Prv] _takeLiquidity #
    - [Prv] calculateLiquidityFee
    - [Prv] _approve #
    - [Prv] _transfer #
    - [Pub] distributeBurnedTokens #
       - modifiers: onlyOwner
    - [Prv] sellBurnedTokens #
    - [Prv] swapBNBForTokens #
    - [Prv] swapTokensForBNB #
    - [Prv] addLiquidity #
    - [Prv] _tokenTransfer #
    - [Pub] migrateLegacyToken #

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 1300+ 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 across 1500 projects!. 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.