Baby Kirito Info

The "Baby Kirito" project has a broad vision and ambition for the future, aiming to make its digital world and game one of the leading platforms in the Blockchain, Metaverse, and NFT Markets.

Baby Kirito 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.

76.80
PoorExcellent

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

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0xD2d2...d72e
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/07/05
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 authorized addresses can set new developer wallet address.
  • The authorized addresses can set new marketing wallet address.
  • The authorized addresses can set fees not more than 10%.
  • The authorized addresses can enable/disable swapping.
  • The owner can exclude multiple addresses from fees. 
  • The authorized addresses can claim foreign tokens. However, it is possible to claim contract's own tokens.

Note - This Audit report consists of a security analysis of the Baby Kirito 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 Baby Kirito team, other contracts associated with the project were not audited by our team. We recommend investors to 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 | 1 findings

Pending

#1 medium Issue
Authorized address can claim contract's own tokens.
BabyKirito.sol
L300-303
Description

In this rescueForeignTokens function, The authorized address can transfer the token to the contract's own address. It is recommended to add a require check to stop claiming the contract's own tokens.

low Issues | 8 findings

Pending

#1 low Issue
Missing Zero Address Validation (missing-zero-check)
BabyKirito.sol
L116
L306
L313
Description

Check that the address is not zero.

Pending

#2 low Issue
Unchecked tokens transfer (unchecked-transfer)
BabyKirito.sol
L300-303
Description

Use `SafeERC20`, or ensure that the transfer/transferFrom return value is checked.

Pending

#3 low Issue
Floating Pragma Solidity Version
BabyKirito.sol
L3
Description

It is recommended to add the constant version of solidity as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.

Pending

#4 low Issue
Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
BabyKirito.sol
L1
Description

We recommend to import all packages from npm directly without flatten the contract. Functions could be modified or can be susceptible to vulnerabilities.

Pending

#5 low Issue
Incorrect emit
BabyKirito.sol
L176
Description

There is no transfer completed of _ttoken to the _msgSender(). Address(0) still owns the balance of _ttoken. It is mentioned to remove the wrong emit from the constructor.

Pending

#6 low Issue
Missing zero check
BabyKirito.sol
L375-379
L381-385
Description

Check that the contractBalance and contractETHBalance is not zero.

Pending

#7 low Issue
Require error message missing
BabyKirito.sol
L387-396
Description

Add the error message on the require check.

Pending

#8 low Issue
Incorrect Token Template
BabyKirito.sol
L123
Description

The reflection token format is not standard, This is not the correct way to use the basic token. It is recommended to follow the correct format of the reflection token. For example, Here _tToken is implemented but not used and the value is still present to the address(0).

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
BabyKirito.sol
L110-113
L116-119
L184-186
L188-190
L192-194
L196-198
L204-207
L209-211
L213-216
L218-222
L300-303
L306-310
L313-317
L387-396
L398-400
L402-406
Description

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

informational Issues | 3 findings

Pending

#1 informational Issue
Conformity to Solidity naming conventions (naming-convention)
BabyKirito.sol
L34
L299
L305
L312
L300
L300
L300
L398
L132
L145
L146
L147
L224
Description

Follow the Solidity [naming convention](https://solidity.readthedocs.io/en/v0.4.25/style-guide.html#naming-conventions).

Pending

#2 informational Issue
Unused state variables (unused-state)
BabyKirito.sol
L93
L127
Description

Remove unused state variables.

Pending

#3 informational Issue
Solidity License
BabyKirito.sol
L1
Description

It is recommended to add a license so it can enable efficient and reliable identification of such licenses and exceptions in an SPDX document, in source files, or elsewhere.