Hamster swap Info

In the bustling realm of decentralized finance (DeFi), HamsterSwap emerges as a beacon of innovation and community-driven ethos. Symbolized by the playful yet resilient moniker "Hamster" this crypto project thrives within the dynamic landscape of blockchain technology.

Hamster swap Logo

TrustNet Score

The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.

71.06
Poor Excellent

Real-Time Threat Detection

Real-time threat detection, powered by Cyvers.io, is currently not activated for this project.

This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks. For more information, click here.

TrustNet DataPulse

Security Assessments

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0xB28b...8474
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2024/06/12
Revision date In progress

Summary and Final Words

No crucial issues found

The contract does not contain issues of high or medium criticality. This means that no known vulnerabilities were found in the source code.

Contract owner cannot mint

It is not possible to mint new tokens.

Contract owner cannot blacklist addresses.

It is not possible to lock user funds by blacklisting addresses.

Contract owner cannot set high fees

The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.

Contract cannot be locked

Owner cannot lock any user funds.

Token cannot be burned

There is no burn function within the contract.

Ownership is not renounced

Contract can be manipulated by owner functions.

Scope of Work

This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.

The auditing process consists of the following systematic steps:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.

A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.

Final Words

The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.


Ownership Privileges:
  • The owner can deploy a new version of the contract, which can change any limit and give the owner new privileges
  • The ERC20 Token is an upgradeable contract in the dividend tracker
  • Deployer can set the following state variables without any limitations
    • swapTokensAtAmount
    • minimumTokenBalanceForDividends
  • Deployer can enable/disable the following state variables
    • _isExcludedFromFees
    • excludedFromDividends
  • Deployer can set the following addresses
    • _marketingWalletAddress
  • Existing Modifiers
    • onlyOwner.
    • initializer.

Note - This Audit report consists of a security analysis of the Hamster Swap Token smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the Hamster Swap team, other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing. Also, we cannot verify if the contract is deployed using a proxy.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 4 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
BABYTOKEN.sol
L2458
L2459
L2519
L2526
L2538
L2552
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
BABYTOKEN.sol
L3069-3075
L3106-3110
L3112-3116
L3118-3122
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
BABYTOKEN.sol
L3040-3041
L3006
Description

Check that the address is not zero.

Pending

#4 low Issue
Local variables used prior their declaration (variable-scope)
BABYTOKEN.sol
L3344
L3343
L3345
Description

Move all variable declarations prior to any usage of the variable, and ensure that reaching a variable declaration does not depend on some conditional if it is used unconditionally.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
BABYTOKEN.sol
L203-205
L211-213
L228-230
L254-257
L262-264
L273-276
L291-305
L319-322
L338-346
L873-875
L881-884
L1748-1750
L1756-1758
L1773-1775
L1799-1802
L1807-1809
L1818-1821
L1836-1850
L1864-1867
L1883-1891
L2105-2107
L2113-2116
L2280-2282
L2284-2293
L2295-2301
L2303-2305
L2466-2477
L2670-2675
L2519-2521
L2538-2545
L2687-2693
L2772-2793
L2820-2872
L3138-3149
L3177-3179
L3181-3185
L3187-3191
L3197-3201
Description

Use the `external` attribute for functions never called from the contract.

informational Issues | 2 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
BABYTOKEN.sol
L579-581
L608-614
L668-670
L678-687
L641-643
L651-660
L554-559
L1165-1174
L1199-1205
L1179-1194
L136-138
L1664-1666
L1674-1676
L2571-2586
L416-431
L1907-1927
L763-776
L787-798
L778-785
L747-754
L1084-1093
L1044-1046
L1110-1119
L1061-1070
L915-921
L957-962
L969-974
L940-950
L928-933
L2238-2241
L2209-2215
L2197-2204
Description

Remove unused functions.

Pending

#2 informational Issue
Unused state variables (unused-state)
BABYTOKEN.sol
L2192
L2123
Description

Remove unused state variables.