Shikoku Inu Info

Shikoku Ken are the loyal protectors of the Japanese mountainous island of Shikoku. They are agile and tenacious, and our $SHIKOKU community is the same. $SHIKOKU is a decentralized experiment, launched on the 7th of November 2022, by the founder, Shikoshi, as a fresh opportunity for those who were struggling in the midst of the biggest bear market since. Born out of trials and tribulation, the $SHIKOKU community is the strongest community you'll find, supportive of one another, and pushing each other towards success.

Overall Score
79.02
Poor Excellent
Shikoku Inu Logo

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

Smart Contract Audit

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x24dA...5572
Network
Ethereum - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/02/02
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 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.


No Audit Comments.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 3 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
TokenMintERC20Token.sol
L455
L455
L455
L455
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Zero Address Validation (missing-zero-check)
TokenMintERC20Token.sol
L455
Description

Check that the address is not zero.

Pending

#3 low Issue
Old Compiler Version
TokenMintERC20Token.sol
-
Description

The contract uses very old compiler version which is not recommended because old versions are prone to known vulnerabilities and it is always advised to use the latest compiler version for deployment.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
TokenMintERC20Token.sol
L239-241
L246-248
L258-261
L266-268
L277-280
L294-298
L312-315
L331-334
L471-473
L480-482
L487-489
L494-496
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)
TokenMintERC20Token.sol
L422-425
L172-179
L192-195
L147-159
Description

Remove unused functions.