Arbisphere Info
Arbisphere was initially born as a Launchpad for the Cronos Chain, it was one of the most hyped projects on the entire chain with thousand of people looking to purchase its token. We started working on our infrastructure and with an A-1 class Launchpad able to launch both DeFi projects and DAOs we got in touch with the Crypto.org foundation in order to receive a grant to further develop the project and allow also the launch of GameFi and NFT collections. Our plan was to become a full-suite Launchzone and not a simple Launchpad, allowing every kind of project to launch on our platform.
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 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 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
- Deployer can set following state variables without any limitations
- sellFee
- Can only be 0 or 1
- sellFee
- Deployer can enable/disable following state variables
- tradeOpen
- can only be enabled
- buyFee
- can only be called once
- isMarketPair
- isExcludedFromFee
- tradeOpen
- Existing Modifiers
- onlyOwner
- Note
- There exist functions in the contract that were not called
- swapTokensForETH
- transferToAddressForETH
- There exist functions in the contract that were not called
- The owner can also change the router and fee recipient address
We recommend the investors to 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
/
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
low Issues | 6 findings
Pending
#1 low Issue
State Variable Visibility not set
It is best practice to set the visibility of state variables explicitly
Pending
#2 low Issue
Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
We recommend to import all packages from npm directly without flatten the contract. Functions could be modified or can be susceptible to vulnerabilities
Pending
#3 low Issue
Local variables shadowing
Rename the local variables that shadow another component
Pending
#4 low Issue
Contract can receive ETH
The contract can receive ETH but the owner is not able to get it out of the contract and also the swapping was not used in the contract as well
Pending
#5 low Issue
Missing Events Arithmetic
Emit an event for critical parameter changes
Pending
#6 low Issue
Unused Functions
The functions are never called in the contract and should either removed or implemented
informational Issues | 2 findings
Pending
#1 informational Issue
NatSpec documentation missing
If you started to comment your code, also comment all other functions, variables etc.
Pending
#2 informational Issue
State variables that could be declared constant (constable-states)
Add the `constant` attributes to state variables that never change