Kabana Club Info

kabana.club

A CLOSED CRYPTO CLUB WITH ITS OWN ECOSYSTEM, IN WHICH, AT THE MOMENT, 3 SMART CONTRACTS INTERACT. OUR CLUB IS AN IDEAL PLACE FOR EVERYONE WHO IS INTERESTED IN THE DEVELOPMENT IN THE WORLD OF CRYPTO, NFT AND BLOCKCHAIN IN GENERAL. KABANA CLUB MEMBERS HAVE THE OPPORTUNITY TO CREATE AND LAUNCH THEIR PROJECTS THROUGH OUR PROJECT INCUBATOR.

Overall Score
94.98
Poor Excellent
Kabana Club Logo

Team and KYC Verification

The team has securely submitted their personal information to SolidProof.io for verification.

In the event of any fraudulent activities, this information will be promptly reported to the relevant authorities to ensure accountability and compliance.

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.

On-Chain Insights

Smart Contract Audit

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x8D4d...0F4F
Network
Polygon - Mumbai Testnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2022/10/25
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 can be burned

There is a function to burn tokens in the contract.

Ownership is renounced

Contract cannot 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.


  • Anybody can burn own tokens or tokens from another addresses only with allowance
  • There is no Ownable in the contract

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 1 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
AmberSoulStone.sol
L236
L236
L236
Description

Rename the local variables that shadow another component.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
AmberSoulStone.sol
L52-54
L57-59
L67-69
L72-74
L77-81
L88-92
L95-104
L107-111
L114-123
L224-226
L229-232
Description

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

informational Issues | 1 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
AmberSoulStone.sol
L30-32
Description

Remove unused functions.