AI Odessey Info
The AI Odyssey is a social experiment involving AI and blockchain technology. Starting from a simple idea and evolving into a grand narrative, the entire process is jointly accomplished by AI and blockchain, ultimately abstracting into a single NFT. This NFT contains a piece of artwork, a short story, and a chatbot, which then continuously evolve into a song, a film, and an independent game.
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.
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.
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 can mint
It is 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 burning within the contract without any allowances
Ownership is not renounced
The owner retains significant control, which could potentially be used to modify key contract parameters.
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:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- 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 Privileges
- The owner can grant Minter Role to wallets and those addresses can mint unlimited AINFT tokens.
- Withdraw any type of tokens from the NFT contract balance
- Update signer address, that can batch mint NFTs
- Configure Token Distribution values
- Set base URI
- Pause/Unpause the contract and stop the transfer of tokens. This may result in the lock of user funds
Note - This Audit report consists of a security analysis of the AiOdessey smart contracts. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one ERC20 token and one NFT contract for the AiOdessey team, other contracts associated with the project were not audited by our team. We recommend investors to 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
medium Issues | 1 findings
Pending
#1 medium Issue
Owner/Authority can Mint
The Minter Role addresses, that are controlled by the deployer/owner address can mint unlimited tokens which is not recommended, as this can be used to manipulate the price of the tokens.
low Issues | 2 findings
Pending
#1 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Pending
#2 low Issue
Local variables used prior their declaration (variable-scope)
Move all variable declarations prior to any usage of the variable, and ensure that reaching a variable declaration does not depend on some conditional if it is used unconditionally.
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 | 3 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
Pending
#2 informational Issue
Unused state variables (unused-state)
Remove unused state variables.
Pending
#3 informational Issue
Unused return values (unused-return)
Ensure that all the return values of the function calls are used.