ARBISHIBA Info

ARBISHIBA's solutions are always aiming for investors to hold the tokens in the long term and benefit greatly from not selling these tokens but store it as a form of property. Liquidity and profits of investors should be drawn to the third tokens to avoid price impact. With the operating mechanism of ARBISHIBA, its total supply will continuously be reduced through the burn on each transaction as well as monthly burn, and the long-term holders can draw their profits by receiving the Shiba Inu token ($Shib) through Airdrop.

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

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

TrustNet DataPulse

Security Assessments

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x8a12...3A3B
Network
Arbitrum - Testnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/03/21
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.

Token transfer can be locked

Owner can lock user funds with owner functions.

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/Authorisation Privileges:

The contracts have 3 modifiers with privileges - onlyOwner, authorised (can be set by the owner), onlyToken

onlyOwner Privileges:

  • Authorize/Unauthorize other addresses to make certain changes in the contract
  • Set the distribution criteria for dividends; minimum period, and minimum distribution value

onlyToken Privileges:

  • Set share of dividend for users
  • Deposit tokens and process dividends

authorized Privileges:

  • Trigger buyback, and clear buyback multiplier
  • Set buyback settings including - buyback status(enable/disable), cap, amount, and period to any value
  •  Set numerator, denominator, and length of buyback multiplier
  • Include/Exclude wallets from fees, and dividends
  • Set buyBacker status for a particular account
  • Set fees to any arbitrary value including 100% or more because it is also possible to set denominator
  • Set fee receiver address
  • Swap Back status and amount
  • Set target liquidity, and distributor settings

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 2 findings

Pending

#1 low Issue
Missing Events Arithmetic (events-maths)
BuybackBabyToken.sol
L967-973
L1601-1614
L1616-1626
L1701-1711
L1713-1720
Description

Emit an event for critical parameter changes.

Pending

#2 low Issue
Missing Zero Address Validation (missing-zero-check)
BuybackBabyToken.sol
L883
L1242
L1245
Description

Check that the address is not zero.

informational Issues | 1 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
BuybackBabyToken.sol
L396-398
L406-412
L425-431
L439-450
L485-487
L495-504
L458-460
L468-477
L371-376
L512-532
L255-264
L273-282
L307-313
L287-302
L192-201
L152-154
L218-227
L23-29
L65-70
L77-82
L48-58
L36-41
Description

Remove unused functions.