DevAI Token
0x647707F14C3136b69f571b0d70EE9Fea9FEC8Fa2 0x6477...EC8Fa2

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
0x6477...EC8Fa2
Network Binance Testnet
License None
Compiler v0.8.26 v0.8.26+commit.8a97fa7a
Type N/A
Language Solidity
Request date 2023/12/04
Revision date 2024/06/25
Critical
Passed

Owner privileges

Crucial issues found The contract does contain issues of high or medium criticality. In some circumstances, the Contract may not function as intended and may pose a safety risk.
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.
Comments

Ownership Privileges

  • The owner can pause and un-pause the claim and un-stake functionality in the contract.
  • The owner can update the Legendary NFT token ID.
  • The owner can withdraw the reward tokens from the contract.
  • The owner can update any arbitrary amount in the pool reward supply.
  • The owner can update any arbitrary amount in the max stake amount limit.
  • The owner can update any arbitrary amount in the rewards per day amount, including zero.
  •  The owner can update any arbitrary amount in the stake amount per NFT, including zero.
  • Any arbitrary address can update the user's claim time period.
  • Any arbitrary address can update the pool end time period.

Note - This Audit report consists of a security analysis of the DEV AI Staking 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 DEV AI team. Other contracts associated with the project were not audited by our team. We recommend investors 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

32

State variables
public

20

Total lines
of code

491

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.

high Issues

Pending

#1 Issue

The owner can lock funds.

StakeContract.sol

L355-375

L404-434

Description

The owner can pause the un-staking of the tokens for an indefinite period of time, but this is not recommended. If the owner has set the paused status to true, no claim can be possible, and the tokens will be stuck forever in the contract. It is recommended that the tokens claiming and un-stake functionality should not be locked permanently.

Pending

#2 Issue

Any arbitrary address can end pool

StakeContract.sol

L484-486

Description

Any arbitrary address can update the pool end time period in the contract. Through this, the staking time period will be ended, and this is not recommended. There must be a certain address so that the ending period cannot be changed by any arbitrary user in the contract.

medium Issues

Pending

#1 Issue

Missing Threshold.

StakeContract.sol

L460-462

L464-466

L468-470

L472-474

Description

The owner can set any arbitrary value in the reward, such as the max staking limit, which is not recommended if it is set to zero. The functionality will fail in the contract. It is recommended that there must be a threshold value so that the amount can not be less than that particular value in t he contract.

Pending

#2 Issue

The contract can lock ether.

StakeContract.sol

L490

Description

The contract does not contain any functionality to withdraw ETH from the contract as this contract can accept ETH, so if any user has sent ETH accidentally to the contract. The ETH will be locked forever. It is recommended to add the functionality so that the ETH cannot be tucked into the contract permanently.

low Issues

Pending

#1 Issue

Local variables shadowing (shadowing-local)

StakeContract.sol

L440

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Events Arithmetic (events-maths)

StakeContract.sol

L468-470

L472-474

Description

Emit an event for critical parameter changes.

Pending

#3 Issue

Floating pragma solidity version.

StakeContract.sol

L7

Description

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

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

StakeContract.sol

L90-92

Description

Remove unused functions.

optimization Issues

Pending

#1 Issue

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

StakeContract.sol

L156-158

L164-167

L355-375

L404-434

L436-438

L440-442

L444-451

L453-458

L460-462

L464-466

L468-470

L472-474

L478-482

L484-486

Description

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

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.