AlienFi
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.
Owner privileges
Comments
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
Audit Scope
This audit covered the following files listed below with a SHA-1 Hash. The above token Team provided us with the files that needs to be tested.
We will verify the following claims:- Correct implementation of Token standard
- Deployer cannot mint any new tokens
- Deployer cannot burn or lock user funds
- Deployer cannot pause the contract
- Overall checkup (Smart Contract Security)
- Review of the specifications, sources, and instructions provided to SolidProof to make sure we understand the size, scope, and functionality of the smart contract.
- Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
- Comparison to specification, which is the process of checking whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
- Test coverage analysis, which is the process of determining whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
- Symbolic execution, which is analysing a program to determine what inputs causes each part of a program to execute.
- Best practices review, which is a review of the smart contracts to improve efficiency, effectiveness, clarify, maintainability, security, and control based on the established industry and academic practices, recommendations, and research.
- Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.
A file with a different Hash has been modified, intentionally or otherwise, after the security review. A different Hash could be (but not necessarily) an indication of a changed condition or potential vulnerability that was not within the scope of this review.
Functions
public
33
State variables
public
5
Total lines
of code
1166
Capabilities
Hover on items
Audit Details
Throughout the review process, care was taken to evaluate the repository for security-related issues, code quality, and adherence to speciïŹcation and best practices. To do so, reviewed line-by-line by our team of expert pentesters and smart contract developers, documenting any issues as there were discovered.
Risk represents the probability that a certain source-threat will exploit vulnerability, and the impact of that event on the organization or system. Risk Level is computed based on CVSS version 3.0.
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L676
L676
L741
L900
Rename the local variables that shadow another component.
Pending
#2 Issue
Floating Pragma
-
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 Issue
Old Compiler Version
-
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.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
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
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
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
Use the `external` attribute for functions never called from the contract.
Diagrams
Disclaimer
SolidProof.io reports are not, nor should be considered, an âendorsementâ or âdisapprovalâ of any particular project or team. These reports are not, nor should be considered, an indication of the economics or value of any âproductâ or âassetâ created by any team. SolidProof.io do not cover testing or auditing the integration with external contract or services (such as Unicrypt, Uniswap, PancakeSwap etcâ...)
SolidProof.io Audits do not provide any warranty or guarantee regarding the absolute bug- free nature of the technology analyzed, nor do they provide any indication of the technology proprietors. SolidProof Audits should not be used in any way to make decisions around investment or involvement with any particular project. These reports in no way provide investment advice, nor should be leveraged as investment advice of any sort.
SolidProof.io Reports represent an extensive auditing process intending to help our customers increase the quality of their code while reducing the high level of risk presented by cryptographic tokens and blockchain technology. Blockchain technology and cryptographic assets present a high level of ongoing risk. SolidProofâs position is that each company and individual are responsible for their own due diligence and continuous security. SolidProof in no way claims any guarantee of security or functionality of the technology we agree to analyze.