Hunter Token
Smart Contract Audit Report
Audit Summary
The Digital Arms Team is building a new staking contract for their Hunter Token.
For this audit, we reviewed the Digital Arms' Staking contract at 0xe383e08915bb6A60922b4aaD9bdCf0D53c095484 on the Binance Blockchain.
Audit Findings
Please ensure trust in the team prior to investing as they have some control in the ecosystem.
Date: March 28th, 2022.Finding #1 - Staking - 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.testHF.addPool(), testHF.editPool(), testHF.deposit(), testHF.withdraw(), testHF.emergencyWithdraw(), testHF.depositRewards(), testHF.withdrawRewards()
Contracts Overview
ERC20Token Contract:
- As the contracts are implemented with Solidity v0.8.0, they are safe from any possible overflows/underflows.
Staking Contract:
- The total supply of tokens is 1 billion $htnr (1,000,000,000).
- At the time of writing this report, there are 26 total token holders. The token allocation is as follows:
- 77% of the total supply belongs to the Owner
- 10% of the total supply belongs to a staking contract
- 10% of the total supply belongs to a staking contract
- 1% of the total supply belongs to a staking contract
- 1% of the total supply belongs to an ERC-721 contract
- The next 21 holders own a cumulative 1% of the total supply.
- There is no mint functionality present beyond deployment.
- Token holders can transfer tokens to the 0x..dead address, which will only reduce the circulating supply; the total supply is unaffected.
- There are no fees associated with transferring tokens.
- This contract complies with the ERC20 Token standard.
- This contract allows users to stake various tokens into pools to earn rewards over time.
- Users receive rewards per block based on the token stake time, multiplier bonus, and points allocated to the pool.
- Users may stake additional LP tokens to recieve pending rewards. Pending rewards are claimed even on deposits of 0 amount.
- Users may withdraw their staked funds at any time; rewards are then automatically claimed.
- Users may trigger an emergency withdraw, which will transfer all of the user's deposited tokens for a specified pool to their wallet address without calculating rewards.
- Reward tokens are supplied to the contract by the Owner.
- The Owner can withdraw any amount of the reward token at any time.
- The Owner can add a new pool or update a pool's share of rewards at any time.
- The Owner can update the bonus multiplier to any value at any time, including 0.
- The Owner can update the rate of rewards generated at any time.
- The staking contract should not be used with fee-on-transfer or ERC-777 tokens. If a fee-on-transfer token is added as a staking asset, then the contract must be exempt from transfer fees.
- The team must be careful not to add the same token twice for staking.
Audit Results
Vulnerability Category | Notes | Result |
---|---|---|
Arbitrary Jump/Storage Write | N/A | PASS |
Centralization of Control |
| 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 |
ERC20Token Contract
($) = payable function
# = non-constant function
Int = Internal
Ext = External
Pub = Public
+ [Int] IERC20
- [Ext] totalSupply
- [Ext] balanceOf
- [Ext] transfer #
- [Ext] allowance
- [Ext] approve #
- [Ext] transferFrom #
+ [Int] IERC20Metadata (IERC20)
- [Ext] name
- [Ext] symbol
- [Ext] decimals
+ Context
- [Int] _msgSender
- [Int] _msgData
+ ERC20 (Context, IERC20, IERC20Metadata)
- [Pub] #
- [Pub] name
- [Pub] symbol
- [Pub] decimals
- [Pub] totalSupply
- [Pub] balanceOf
- [Pub] transfer #
- [Pub] allowance
- [Pub] approve #
- [Pub] transferFrom #
- [Pub] increaseAllowance #
- [Pub] decreaseAllowance #
- [Int] _transfer #
- [Int] _mint #
- [Int] _burn #
- [Int] _approve #
- [Int] _spendAllowance #
- [Int] _beforeTokenTransfer #
- [Int] _afterTokenTransfer #
+ ERC20Token (ERC20)
- [Pub] #
- modifiers: ERC20
Staking Contract
($) = payable function
# = non-constant function
Int = Internal
Ext = External
Pub = Public
+ [Int] IERC20
- [Ext] totalSupply
- [Ext] balanceOf
- [Ext] transfer #
- [Ext] allowance
- [Ext] approve #
- [Ext] transferFrom #
+ Context
- [Int] _msgSender
- [Int] _msgData
+ Ownable (Context)
- [Pub] #
- [Pub] owner
- [Pub] renounceOwnership #
- modifiers: onlyOwner
- [Pub] transferOwnership #
- modifiers: onlyOwner
- [Int] _transferOwnership #
+ [Lib] SafeMath
- [Int] tryAdd
- [Int] trySub
- [Int] tryMul
- [Int] tryDiv
- [Int] tryMod
- [Int] add
- [Int] sub
- [Int] mul
- [Int] div
- [Int] mod
- [Int] sub
- [Int] div
- [Int] mod
+ [Lib] Address
- [Int] isContract
- [Int] sendValue #
- [Int] functionCall #
- [Int] functionCall #
- [Int] functionCallWithValue #
- [Int] functionCallWithValue #
- [Int] functionStaticCall
- [Int] functionStaticCall
- [Int] functionDelegateCall #
- [Int] functionDelegateCall #
- [Int] verifyCallResult
+ [Lib] SafeERC20
- [Int] safeTransfer #
- [Int] safeTransferFrom #
- [Int] safeApprove #
- [Int] safeIncreaseAllowance #
- [Int] safeDecreaseAllowance #
- [Prv] _callOptionalReturn #
+ [Int] IERC20Metadata (IERC20)
- [Ext] name
- [Ext] symbol
- [Ext] decimals
+ ERC20 (Context, IERC20, IERC20Metadata)
- [Pub] #
- [Pub] name
- [Pub] symbol
- [Pub] decimals
- [Pub] totalSupply
- [Pub] balanceOf
- [Pub] transfer #
- [Pub] allowance
- [Pub] approve #
- [Pub] transferFrom #
- [Pub] increaseAllowance #
- [Pub] decreaseAllowance #
- [Int] _transfer #
- [Int] _mint #
- [Int] _burn #
- [Int] _approve #
- [Int] _spendAllowance #
- [Int] _beforeTokenTransfer #
- [Int] _afterTokenTransfer #
+ ERC20Token (ERC20)
- [Pub] #
- modifiers: ERC20
+ testHF (Ownable)
- [Pub] #
- [Ext] poolLength
- [Pub] addPool #
- modifiers: onlyOwner
- [Pub] editPool #
- modifiers: onlyOwner
- [Pub] getMultiplier
- [Ext] pendingTOKEN
- [Pub] massUpdatePools #
- [Pub] updatePool #
- [Pub] deposit #
- [Pub] withdraw #
- [Pub] emergencyWithdraw #
- [Pub] depositRewards #
- modifiers: onlyOwner
- [Pub] withdrawRewards #
- modifiers: onlyOwner
- [Int] rewardTransfer #
- [Ext] setBonusMultiplier #
- modifiers: onlyOwner
- [Ext] setTokenPerBlock #
- modifiers: onlyOwner
About Solidity Finance
Solidity Finance was founded in 2020 and quickly grew to have one of the most experienced and well-equipped smart contract auditing teams in the industry. Our team has conducted 1000+ solidity smart contract audits covering all major project types and protocols, securing a total of over $10 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 Solidity Audit?
Typically, a smart contract audit is a comprehensive review process designed to discover logical errors, security vulnerabilities, and optimization opportunities within code. A Solidity 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.