Toshi Tools
0x77a90B04d64189d4D09508612C09219bC6816BdC 0x77a9...816BdC

Static analysis Dynamic analysis Symbolic Execution SWC check

In Japanese, “Toshi” means to invest. A “Tool” is an instrument used to broaden an individual’s abilities. We are Toshi Tools, a group of savvy developers and successful traders that have identified a hole in the market. We have identified here is no platform up to our standard that allows users to view and track past investments, or to help with future decisions. A series of successful databases has allowed us to be in this current situation, of information overload. Starting with the blockchain. The blockchain is an ever-evolving distributed database that stores information in a highly secure and transparent way, making it impossible to alter or tamper with. Although the blockchain was a revolutionary innovation that has brought us far, its technical nature makes it difficult for users without cryptography or computer science knowledge to decipher the information.

Contract address
0x77a9...816BdC
Network Ethereum Mainnet
License None
Compiler v0.8.4 v0.8.4+commit.c7e474f2
Type N/A
Language Solidity
Request date 2023/01/04
Revision date 2023/01/04
Critical
Passed
High
Passed
Medium
Passed

Owner privileges

No critical 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 can blacklist addresses It is possible to lock user funds by blacklisting addresses.
Contract owner can set high fees Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.
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.
Comments

Ownership Privileges:

  • Open Trading but cannot close it
  • Set Whitelist, Include/Exclude accounts from fee
  • Set Max transaction percent
  • Tax can be set up to a maximum of 40%

Developer Address Privileges:

  • Router percent can be set to any arbitrary value which can be used in manipulating the contract's balance because on L347 if the contract balance is more than or equal to the "_routermax" value then the '_routermax' value will be set as the "contractTokenBalance"
  • Set market tax address, dev tax address, and Developer address
  • Set the Buy and Sell tax to zero
  • Manually swap tokens, both for complete balance and a custom percentage
  • Enable/Disable swap by calling the function on L431 which may lead to a lock of funds
  • Manually send contract balance to fee

Audit Scope

This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.

We will verify the following claims:
  • Correct implementation of Token standard
  • Deployer cannot mint any new tokens
  • Deployer cannot burn or lock user funds
  • Deployer cannot pause the contract
  • Overall checkup (Smart Contract Security)
The auditing process follows a routine series of steps:
  • Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
  • Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
  • Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
  • Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
  • Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
  • Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
  • Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.

A file with a different Hash has been modified, intentionally or otherwise, after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.

Functions
public

45

State variables
public

1

Total lines
of code

632

Capabilities
Hover on items

Audit Details

Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to specification and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.

Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.

low Issues

Pending

#1 Issue

Local variables shadowing (shadowing-local)

ToshiTools.sol

L247

L311

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Events Arithmetic (events-maths)

ToshiTools.sol

L595-598

L600-603

Description

Emit an event for critical parameter changes.

Pending

#3 Issue

Missing Zero Address Validation (missing-zero-check)

ToshiTools.sol

L101

L205

L205

L205

L608

L613

L617

Description

Check that the address is not zero.

Pending

#4 Issue

Missing Error Message

ToshiTools.sol

L333,336,341

Description

Make sure to display error messages in every require statement

informational Issues

Pending

#1 Issue

Function initializing state variables (function-init-state)

ToshiTools.sol

L177

L178

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

#2 Issue

Unused state variables (unused-state)

ToshiTools.sol

L94

L166

L185

Description

Remove unused state variables.

Pending

#3 Issue

Unused return values (unused-return)

ToshiTools.sol

L404-429

L404-429

Description

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

optimization Issues

Pending

#1 Issue

State variables that could be declared constant (constable-states)

ToshiTools.sol

L94

L179

Description

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

Pending

#2 Issue

Public function that could be declared external (external-function)

ToshiTools.sol

L115-118

L218-220

L222-224

L226-228

L230-232

L238-245

L247-254

L256-263

L265-280

L371-373

L375-377

L378-380

L454-458

L459-463

L464-466

L605-607

Description

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

Diagrams

Disclaimer

SolidProof.io reports are not, nor should be considered, an “endorsement” or “disapproval” of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any “product” or “asset” created by any team. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etc’...)

SolidProof.io Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort.

SolidProof.io Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProof’s position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.