ArbiBabySpace Info

ArbiBabySpace is a community-driven, decentralized Meme token that supports charity causes, for the people who needs , Charity Causes, Hospitals, Senior Centers, Schools, Orphanages Etc... The team will also implement a community governance system, allowing $ARBI holders to propose and vote on "Charity Foundation" where the money from funds to go. Built on the Arbitrum One Network, ArbiBabySpace leverages the speed and low transaction fees of the exchanges to enable efficient and cost-effective.

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

79.84
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
0x7Fd5...bF65
Network
Arbitrum - Testnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/03/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
  • Include/Exclude wallets from fee, max wallet, and maximum transaction limit.
  • Set/Update max wallet, and maximum transaction limit values but within a safe range
  • Set new LP pair address
  • Update marketing, staking, and charity wallet addresses
  • Set fees, but cannot be set more than 15%
  • Set/Update the number of tokens to sell in order to get reward to any arbitrary value including zero
  • Enable/Disable swap and liquify

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
Owner can drain liquidity
ArbiBabySpace.sol
L1021
Description

The liquidity of the contract automatically gets credited into the owner's wallet whenever the 'addLiquidity' function is called inside the contract. Note that it cannot be called manually but it will be done automatically every time the swap and liquify function is called. Moreover, even after the renouncement of the ownership, this liquidity will still be credited to the owner's wallet.

low Issues | 2 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
ArbiBabySpace.sol
L546
L556
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing Zero Address Validation (missing-zero-check)
ArbiBabySpace.sol
L680
L679
Description

Check that the address is not zero.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
ArbiBabySpace.sol
L439
L441
L442
L465
Description

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

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
ArbiBabySpace.sol
L75-78
L80-87
L535-543
L556-564
L566-577
L579-591
L768-776
L778-790
Description

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

informational Issues | 4 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
ArbiBabySpace.sol
L48-51
Description

Remove unused functions.

Pending

#2 informational Issue
Function initializing state variables (function-init-state)
ArbiBabySpace.sol
L440
L473
L474
L475
Description

Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.

Pending

#3 informational Issue
Unused return values (unused-return)
ArbiBabySpace.sol
L1011-1024
Description

Ensure that all the return values of the function calls are used.

Pending

#4 informational Issue
Uninitialized local variables (uninitialized-local)
ArbiBabySpace.sol
L888
L869
Description

Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.