DevAI Token Info
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.
Overall Score
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
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
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
- 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.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
high Issues | 2 findings
Pending
#1 high Issue
The owner can lock funds.
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 high Issue
Any arbitrary address can end pool
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 | 2 findings
Pending
#1 medium Issue
Missing Threshold.
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 medium Issue
The contract can lock ether.
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 | 3 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#3 low Issue
Floating pragma solidity version.
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.
optimization Issues | 1 findings
Pending
#1 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
informational Issues | 1 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
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:
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.