Robora Info
Robora is a decentralized AI orchestration platform for robotics and IoT, designed to unify fragmented data, software, and hardware into a collaborative, blockchain-powered ecosystem. Functioning as a framework and marketplace that empowers users to build, train, deploy, and monetize intelligent Synths/Robots. Think of it as the "Web3-hub for physical AI.
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 cannot mint
It is not possible to mint new tokens.
Contract owner can blacklist addresses
It is 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 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 operations wallet can change the current operations wallet.
- The development wallet can change the current development wallet.
- The owner can launch the token.
- The owner can toggle the limits.
- The owner can toggle the cooldown settings.
- The owner can toggle the tax settings.
- The owner can set the maximum buy amount, initially 0.8% of the total supply.
- The owner can set the maximum sell amount, initially 0.8% of the total supply.
- The owner can set the maximum wallet size, initially 0.8% of the total supply.
- The owner can set the swap tokens threshold.
- The owner can set the buy fee, initially 20%.
- The owner can set the sell fee, initially 30%.
- The owner can set the transfer fee, initially 60%.
- The owner can set the development wallet's share of fees.
- The owner can exclude accounts from fees.
- The owner can exclude accounts from limits.
- The owner can block accounts by marking them as bots.
- The owner can add new automated market maker pairs.
- The owner can withdraw stuck tokens from the contract.
Note - This Audit report consists of a security analysis of the Robora 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 Robora 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
/
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
/
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
/
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
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
low Issues | 3 findings
Pending
#1 low Issue
Owner Can Bypass Fee Distribution and Claim All Collected RBR Fees
The withdrawStuckTokens function creates a backdoor that allows the contract owner to claim all collected transaction fees directly. While intended to recover accidental token transfers, the owner can call it with the RBRToken's own address. This action transfers the entire balance of collected RBR fees from the contract directly to the owner's wallet. This fundamentally breaks the token's economic model by allowing the owner to bypass the automated _swapBack and fee distribution mechanism, preventing any revenue from reaching the operations and development wallets.
Pending
#2 low Issue
The owner can blacklist wallets.
The contract owner possesses the unilateral authority to blacklist any wallet address at any time by using the setBots function. This function effectively freezes all assets within the targeted wallet, preventing the wallet's owner from transferring their tokens. This presents a significant centralization risk, as it grants the contract owner the power to censor users and lock their funds without any oversight or warning.
Pending
#3 low Issue
Missing 'require' check. (Potential honeypot)
The owner can set any address to the operations wallet and development wallet,excluding zero address as this can lead to a potential honeypot if the owner has set the address to a contract address that cannot receive ETH. It is recommended that the address cannot be set to a contract address that cannot receive ETH to avoid these circumstances.