Smart Contract Audit Report
SharkCoin is a new BEP-20 token on the Binance Smart Chain.
For this audit, we reviewed the project team's Coin contract at 0x756c1a6135786a86dbdcee4897256992180675b2 on the Binance Smart Chain Mainnet.
No findings were identified.
Date: April 19th, 2023.
Updated: April 20th, 2023 to reflect updates made to the contract from commit 093f705928efbbbd5f1c2ebd0bae24f341b67be5 to commit 65bab907f31498f9031349d76b34638934548fd6.
Updated: April 21st, 2023 to reflect the token's Mainnet address.
- The initial supply of the token is set to 1 billion [1,000,000,000] $SHRK.
- No mint functions are accessible beyond deployment.
- Any user can burn their own tokens to reduce the total supply at any time.
- Any user can burn tokens on another user's behalf if an allowance has been granted.
- At the time of writing this report, 97.65% of the total supply belongs to the deployer.
- The remaining 2.35% of the total supply belongs to an unverified contract.
- The Default Admin can pause/unpause the contract at any time which disables all transfers and burning from being able to occur.
- As the contract is deployed with Solidity v0.8.17, it is protected from overflows/underflows.
- The contract complies with the BEP-20 token standard.
|Arbitrary Jump/Storage Write||N/A||PASS|
|Centralization of Control||The team can pause all transfers at any time.||PASS|
|Delegate Call to Untrusted Contract||N/A||PASS|
|Dependence on Predictable Variables||N/A||PASS|
|Improper Authorization Scheme||N/A||PASS|
|Outdated Compiler Version||N/A||PASS|
|Overall Contract Safety||PASS|
($) = payable function # = non-constant function Int = Internal Ext = External Pub = Public + [Int] IAccessControl - [Ext] hasRole - [Ext] getRoleAdmin - [Ext] grantRole # - [Ext] revokeRole # - [Ext] renounceRole # + [Int] IAccessControlEnumerable (IAccessControl) - [Ext] getRoleMember - [Ext] getRoleMemberCount + Context - [Int] _msgSender - [Int] _msgData + [Lib] Math - [Int] max - [Int] min - [Int] average - [Int] ceilDiv - [Int] mulDiv - [Int] mulDiv - [Int] sqrt - [Int] sqrt - [Int] log2 - [Int] log2 - [Int] log10 - [Int] log10 - [Int] log256 - [Int] log256 + [Lib] SignedMath - [Int] max - [Int] min - [Int] average - [Int] abs + [Lib] Strings - [Int] toString - [Int] toString - [Int] toHexString - [Int] toHexString - [Int] toHexString - [Int] equal + [Int] IERC165 - [Ext] supportsInterface + ERC165 (IERC165) - [Pub] supportsInterface + AccessControl (Context, IAccessControl, ERC165) - [Pub] supportsInterface - [Pub] hasRole - [Int] _checkRole - [Int] _checkRole - [Pub] getRoleAdmin - [Pub] grantRole # - modifiers: onlyRole - [Pub] revokeRole # - modifiers: onlyRole - [Pub] renounceRole # - [Int] _setupRole # - [Int] _setRoleAdmin # - [Int] _grantRole # - [Int] _revokeRole # + [Lib] EnumerableSet - [Prv] _add # - [Prv] _remove # - [Prv] _contains - [Prv] _length - [Prv] _at - [Prv] _values - [Int] add # - [Int] remove # - [Int] contains - [Int] length - [Int] at - [Int] values - [Int] add # - [Int] remove # - [Int] contains - [Int] length - [Int] at - [Int] values - [Int] add # - [Int] remove # - [Int] contains - [Int] length - [Int] at - [Int] values + AccessControlEnumerable (IAccessControlEnumerable, AccessControl) - [Pub] supportsInterface - [Pub] getRoleMember - [Pub] getRoleMemberCount - [Int] _grantRole # - [Int] _revokeRole # + Pausable (Context) - [Pub]
# - [Pub] paused - [Int] _requireNotPaused - [Int] _requirePaused - [Int] _pause # - modifiers: whenNotPaused - [Int] _unpause # - modifiers: whenPaused + [Lib] StorageSlot - [Int] getAddressSlot - [Int] getBooleanSlot - [Int] getBytes32Slot - [Int] getUint256Slot - [Int] getStringSlot - [Int] getStringSlot - [Int] getBytesSlot - [Int] getBytesSlot + [Int] IERC20 - [Ext] totalSupply - [Ext] balanceOf - [Ext] transfer # - [Ext] allowance - [Ext] approve # - [Ext] transferFrom # + [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 # + ERC20Burnable (Context, ERC20) - [Pub] burn # - [Pub] burnFrom # + Coin (AccessControlEnumerable, Pausable, ERC20Burnable) - [Pub] # - modifiers: ERC20 - [Ext] pause # - modifiers: onlyRole - [Ext] unpause # - modifiers: onlyRole - [Int] _beforeTokenTransfer #
SourceHat (formerly Solidity Finance - founded in 2020) has quickly grown to have one of the most experienced and well-equipped smart contract auditing teams in the industry. Our team has conducted 1700+ 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 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.