Exyra Info
Exyra is a modular AI-native protocol designed to decode and automate Web3 finance. By leveraging autonomous logic layers called Insight Nodes, Exyra helps users identify, customize and act on blockchain-based financial strategies in real time. These intelligent modules interpret on-chain complexity and translate it into user-tailored actions, aligned with individual behaviors and risk preferences. From scanning yield pathways to executing optimized transactions, Exyra delivers an adaptive flow from opportunity detection to decision execution, all within a unified interface. At its core, Exyra aims to redefine how users interact with decentralized finance. making it fluid, predictive and radically more user-centric, whether you’re a seasoned on-chain builder or just stepping into crypto.
Team and KYC Verification
The team has securely submitted their personal information to SolidProof.io for verification.
In the event of any fraudulent activities, this information will be promptly reported to the relevant authorities to ensure accountability and compliance.
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.
Security Assessments
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 can set high fees
Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.
Contract cannot be locked
Owner cannot lock any user funds.
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.
Contract is not upgradeable
The contract does not use proxy patterns or other mechanisms to allow future upgrades. Its behavior is locked in its current state.
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 enable trading only once.
- The owner can exclude wallets for transferring tokens without enabling trade.
- The owner can remove max transaction and max wallet limits.
- The owner cannot set the buy and sell fees to not more than 30%.
- The owner can withdraw ETH from the contract.
- The owner can withdraw the tokens from the contrac, including exyra tokens.
- The owner can manually swap tokens.
Note - This Audit report consists of a security analysis of the Exyra 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 Exyra 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
Findings and Audit result
medium Issues | 3 findings
Pending
#1 medium Issue
Transfer of tokens without enabling trade.
The trading needs to be enabled by the owner in order for regular users to transfer tokens. On the contrary, the owner can authorize addresses manually and those addresses will be able to trade tokens. This functionality can be exploited in the following way, For example, there is a presale and the wallets used for the presale can be authorized by the owner. All the tokens obtained can be consolidated into a final wallet address and facilitate trading and selling of the acquired tokens, the last wallet address can be authorized.
Pending
#2 medium Issue
Liquidity is added to externally owned address.
The contract's liquidity is automatically added to the 'owner' address, which is not recommended because, in an extreme scenario, this can be used to drain liquidity from the contract.
Pending
#3 medium Issue
Excessively High Initial Transaction Fees
The smart contract initializes the buyFee and sellFee to a fixed rate of 30% on lines 122 and 123. This means that, by default, all buy and sell transactions are subject to a significant 30% tax. While the updateTaxes function on line 240 allows the contract owner to decrease this rate, it cannot be increased. A 30% fee is exceptionally high for a standard token and can be detrimental to traders, creating immediate and substantial losses upon transacting. This can deter potential investors, damage market sentiment, and may be perceived as a "honeypot" characteristic, where users can buy but cannot sell without incurring prohibitive costs, even though the sell function is not technically disabled.
low Issues | 2 findings
Pending
#1 low Issue
Missing events arithmetic
Emit all the critical parameter changes.
Pending
#2 low Issue
Owner's Unilateral Authority to Withdraw All Contract-Held Exyra Tokens
The withdrawTokens() function, located at line 296, is an external function that can only be called by the contract owner. Its purpose is to withdraw the entire balance of Exyra tokens held by the smart contract and transfer them to the owner's wallet. These tokens are accumulated within the contract as a result of the buyFee and sellFee applied to user transactions. While it is standard for contract owners to have a mechanism to access collected fees, this implementation grants the owner the unilateral power to drain all collected Exyra tokens from the contract at any time, without any restrictions, delays, or oversight. This poses a significant centralization risk, as the security of these community-generated funds relies solely on the integrity of the single owner.
informational Issues | 1 findings
Pending
#1 informational Issue
Missing Visibility
It is recommended to add 'public,' 'private,' or 'internal' visibility during the declaring or initialization of a state variable or a mapping.