AlienFi Info

AlienFi is a decentralized exchange (DEX) built on the Arbitrum Chain that provides fast, secure, and low-cost tokens trading with total transparency and full control over your funds.

AlienFi Logo

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.

79.02
PoorExcellent

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

Loading...
Mobula Logo Data provided by mobula.io. Need data? Get your API.
Loading...

We are presently engaged in detailed discussions with our partners to finalize the arrangements. Information regarding presales will be made available on this platform in the near future. We appreciate your patience and look forward to sharing the upcoming opportunities with you soon!

We are currently in discussions with our partners to finalize the details. Information on token locking and vesting schedules will be provided on this platform soon. We appreciate your patience and look forward to sharing these upcoming opportunities with you shortly.

In the meantime, we’ve already integrated the LP lock overview from UNCX.network. Please visit the CEX/DEX tab for more information.

Security Assessments

Static AnalysisDynamic AnalysisSymbolic ExecutionSWC CheckManual Review
Contract address
0x6740...5f8c
Network
Arbitrum - Testnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/02/22
Revision date In progress

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.

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:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. 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.


The owner is able to Mint new tokens without any limitations. Beware of this.

Note for Investors: We only Audited a simple token and Governance contract for AlienFi with only a few functions. However, If the project has other contracts (for example, a Presale contract, etc), and they were not provided to us in the audit scope then we cannot comment on its security. Hence, we are not responsible for it in any way.

We recommend investors/users 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

low Issues | 3 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
AlienFi.sol
L676
L676
L741
L900
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Floating Pragma
AlienFi.sol
-
Description

The current pragma Solidity directive is “^0.6.12". Contracts should be deployed with the same compiler version and flags that they have been tested thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions

Pending

#3 low Issue
Old Compiler Version
AlienFi.sol
-
Description

The contract uses an old compiler version (^0.6.12) and we don't recommend using it because old versions tend to have known vulnerabilities that may get exploited in the future.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
AlienFi.sol
L439-442
L448-452
L700-702
L707-709
L714-716
L733-736
L741-743
L752-755
L769-777
L791-794
L810-813
L823-826
L932-935
Description

Use the `external` attribute for functions never called from the contract.

informational Issues | 1 findings

Pending

#1 informational Issue
Functions that are not used (dead-code)
AlienFi.sol
L172-189
L104-106
L114-116
L129-131
L139-146
L154-156
L164-170
L51-60
L78-84
L879-885
L914-917
L373-376
L515-525
L488-497
L504-507
L499-502
L473-475
L477-479
L294-296
L310-316
L330-332
L346-349
L268-280
Description

Remove unused functions.