DevAI Token
0xF7498c98789957F4eE53B3E37fF5B7Ef8A6CFC7b 0xF749...6CFC7b

Static analysis Dynamic analysis Symbolic Execution SWC check

In today’s digital age, blockchain technology has emerged as a powerful tool for creating secure and transparent decentralized applications. However, developing smart contracts using Solidity, the most widely used programming language for Ethereum blockchain, can be a complex and time-consuming process, requiring specialized knowledge and expertise. To address this challenge, we have developed an AI bot that writes Solidity contracts, providing a fast, reliable, and cost-effective solution for companies looking to develop blockchain-based applications. Our bot uses advanced machine learning algorithms to generate Solidity code automatically, simplifying the process and reducing the risk of errors.

Contract address
0xF749...6CFC7b
Network Ethereum Mainnet
License MIT
Compiler v0.8.19 v0.8.19+commit.7dd6d404
Type N/A
Language Solidity
Request date 2023/12/04
Revision date 2024/06/25
Critical
Passed
High
Passed
Medium
Passed

Owner privileges

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

Ownership Privileges

  • Once the swapping is completed, the marketing receiver will receive the ETH from the contract.
  • Once the swapping is completed, the dev receiver will receive the ETH from the contract.

The ownership of the token is renounced, which means that the owner cannot modify any existing value present in the contract.

Note - This Audit report consists of a security analysis of the DevAI 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 DevAI team. Other contracts associated with the project were not audited by our team. We recommend investors to do their own research before investing.

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

62

State variables
public

2

Total lines
of code

1659

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 speciïŹcation 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)

DEVAI.sol

L1004

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Zero Address Validation (missing-zero-check)

DEVAI.sol

L1411

L1422

L1433

Description

Check that the address is not zero.

Pending

#3 Issue

Remove safemath library

DEVAI.sol

L13-239

Description

Compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow. It is recommended to remove the unwanted code in order to avoid high gas fees.

Pending

#4 Issue

Dangerous usage of `tx.origin` (tx-origin)

DEVAI.sol

L1438-1571

Description

Do not use `tx.origin` for authorization.

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

DEVAI.sol

L348-350

L623-638

L105-107

L203-212

L163-165

L229-238

L180-189

L19-28

L70-78

L85-93

L50-63

L35-43

Description

Remove unused functions.

optimization Issues

Pending

#1 Issue

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

DEVAI.sol

L876

L857

Description

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

Pending

#2 Issue

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

DEVAI.sol

L380-382

L388-390

L433-439

L444-449

L458-464

L479-496

L510-520

L536-550

L738-740

L1387-1397

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.