Cyclops97 Info

Welcome to CYCLOPS97! Here, at the epicenter of the crypto revolution, we draw inspiration from the bold leadership of Cyclops97 and his team from the latest reboot. Prepared to push boundaries and conquer new territories, our community is forged in determination, innovation, and a spirit of adventure.

Cyclops97 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.

25.28
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.

Security Assessments

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0xc37B...830C
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2024/05/04
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 burning within the contract without any allowances

Ownership is not renounced

The owner retains significant control, which could potentially be used to modify key contract parameters.

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 update any arbitrary amount in the balance of the minimum tokens for dividends.
  • The owner can exclude wallets from dividends.
  • The owner can update the claim wait between 1 to 24 hours.
  • The owner can update the router address.
  • The owner can exclude multiple wallets from fees.
  • The owner can set any arbitrary address as the marketing wallet address.
  • The owner can update the automated market maker pair address.
  • The owner can update the processing gas between 200,000 to 500,000.
  • The owner can manually swap tokens.
  • The owner can set any arbitrary amount in the minimum swap threshold amount including zero.
  • The owner can set any arbitrary address as the dead address.
  • The owner can set the buy and sell fees of not more than 25%.

Note - This Audit report consists of a security analysis of the Cyclops97 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 Cyclops97 team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

medium Issues | 2 findings

Pending

#1 medium Issue
Liquidity is added to externally owned address.
CYCLOPS97.sol
L1704-1717
Description

The contract's liquidity is automatically added to the 'marketing wallet' address, which is not recommended because, in an extreme scenario, this can be used to drain liquidity from the contract.

Pending

#2 medium Issue
Missing 'require' check.
CYCLOPS97.sol
L1386-1388
Description

The owner can set any arbitrary address as the marketing wallet address, including zero and dead address which is not recommended as this can lock the funds of the address is set to any contract address that cannot receive BNB. It is recommended that there must be a check so that the value cannot be set to zero or dead and to any contract address.

low Issues | 5 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
CYCLOPS97.sol
L825
L825
L873
L880
L887
L897
L1322
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Events Arithmetic (events-maths)
CYCLOPS97.sol
L1508-1510
L1516-1523
L1525-1531
Description

Emit an event for critical parameter changes.

Pending

#3 low Issue
Missing Zero Address Validation (missing-zero-check)
CYCLOPS97.sol
L825
L1332-1333
L1366-1367
L1386
L1512
Description

Check that the address is not zero.

Pending

#4 low Issue
Remove safemath library
CYCLOPS97.sol
L88-209
Description

The compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow. It is recommended to remove the unwanted code in order to avoid high gas fees.

Pending

#5 low Issue
Missing threshold.
CYCLOPS97.sol
L989-991
L1508-1510
Description

The owner can update any arbitrary value in the minimum balance for dividend and minimum swap threshold value, which is not recommended as there must be a certain limit. If the value is set to a very excessive amount, then the functionality will not work.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
CYCLOPS97.sol
L1253
Description

Add the `constant` attributes to state variables that never change.

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
CYCLOPS97.sol
L40-42
L44-47
L309-311
L317-319
L334-336
L360-363
L368-370
L379-382
L397-405
L419-422
L438-441
L830-841
L845-847
L873-875
L887-889
L1018-1020
L1067-1084
L1111-1156
L1170-1172
L1358-1360
L1362-1369
L1378-1384
L1390-1393
L1416-1421
L1435-1437
L1439-1441
L1443-1445
L1451-1453
L1498-1506
L1508-1510
L1512-1514
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)
CYCLOPS97.sol
L217-226
L235-244
L269-275
L249-264
L15-17
L907-913
L133-135
L137-140
L191-194
L162-168
L150-157
Description

Remove unused functions.

Pending

#2 informational Issue
Unused state variables (unused-state)
CYCLOPS97.sol
L145
Description

Remove unused state variables.