Sugar Kingdom Odyssey
Smart Contract Audit Report
Executive Summary
This report presents the outcomes of our collaborative engagement with the Sugar Kingdom team, focusing on the comprehensive evaluation of the TeamToken contract.
Our team conducted an initial security assessment from March 19th to March 20th, 2024.
Sugar Kingdom Odyssey is a new BEP-20 token deployed on the Binance Smart Chain. $SKO is the native token of Sugar Kingdom's ecosystem.
Audit Scope
Name |
Source Code |
Visualized |
TeamToken |
Name/Source Code |
Visualized |
Audit Findings
No findings were identified, though some centralized aspects are present.
System Overview
MINTS AND BURNSThe total supply of the token is set to 100 million $SKO (100,000,000). No mint or burn functions are accessible though the total supply of the token can be reduced by transferring tokens to the 0x..dead address.
CURRENT TOKEN HOLDERSAt the time of writing this report there are 6 token holders. The token allocation is as follows:
- 93.47% of the total supply belongs to a wallet controlled by the team.
- 2.1% of the total supply belongs to an EOA.
- 2% of the total supply belongs to a Wormhole TokenBridge contract.
- 1.53% of the total supply belongs to an EOA.
- 0.83% of the total supply belongs to a GnosisSafeProxy contract.
- 0.67% of the total supply belongs to an EOA.
The contract utilizes the SafeMath library to prevent overflows/underflows in applicable functions. There are no fees associated with transferring tokens. The contract complies with the BEP-20 standard.
Vulnerability Analysis
| Vulnerability Category | Notes | Result |
|---|---|---|
| Arbitrary Jump/Storage Write | N/A | PASS |
| Centralization of Control | The team currently owns a large portion of the total supply. | 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 |
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.