IDegen Info
iDEGEN is a sentient degenerate AI memelord. It learns, evolves, and adapts based on what the community feeds it on X. It’s powered by AI, raised by degens. iDEGEN has no knowledge prior to it being birthed. iDEGEN reads and responds to every single X post tagging it. iDEGEN can read links. iDEGEN absorbs that post and adds it to its knowledge base, it’s how it learns. Everything iDEGEN posts is driven by its AI and what it learns from its community, no human intervention.
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.
TrustNet DataPulse
There are currently no DeFi contracts accessible at this time.
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.
Contract cannot be locked
Owner cannot lock any user funds.
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
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
BuyWithFiat.sol
- The admin address can recover records.
BuyWithToken.sol
- The owner can withdraw the tokens from the contract.
Note - This Audit report consists of a security analysis of the IDegen 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 IDegen 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
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
high Issues | 1 findings
Resolved
#1 high Issue
Missing access control.
The contract contains the functionality in which any arbitrary address can withdraw the tokens from the contract to the receiver address which can lead to unintended or malicious usage (e.g., DoS attacks by spamming calls). This is not recommended as the critical functions should only be called through the restricted wallets to ignore the unwanted transactions in the contract.
medium Issues | 2 findings
Resolved
#1 medium Issue
Missing Non-reentrant check
The contract contains the functionality in which the buyWithFait function (and similar functions like withdraw), making an external call to transfer ERC20 tokens using the transfer function. Since the contract hasn't yet marked the claim as completed (i.e., updated the claimed variable), the attacker can exploit this to re-enter the buyWithFait function, repeatedly withdrawing tokens. The transfer happens rst (interaction with an external contract) before the internal state is updated. The nonReentrant modier ensures that any attempts to call the claim function again during execution are blocked, providing an additional safeguard. Therefore, It is recommended to do the check-effect-transaction method or use the non-reentrant modier to prevent the code from this issue.
Pending
#2 medium Issue
The contract can lock Ether
The contract contains the functionality in which the contract can lock etc if the contract receives Ether unintentionally or for specific purposes, without a withdrawal mechanism, it risks funds being locked permanently. Add a withdrawal function restricted to the owner, ensuring access control and secure retrieval of Ether. For specific use cases, include mechanisms to allocate Ether to designated addresses (e.g., feeReceiver) or handle accidental deposits through automatic refunds via the fallback function. If Ether is part of the business logic, track contributions using mappings. These measures prevent Ether from being lost, allow proper utilization, and improve the contract's usability and security while ensuring funds are not stuck indefinitely.
low Issues | 1 findings
Pending
#1 low Issue
Floating pragma solidity version
The contracts should be deployed with the same compiler version and ag that they have been tested thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions.