Astro Chain
The objectives of the AstroChain platform are focused on consumers and investors to make the most out of an all-in-one ecosystem. Connecting digital applications that can be used both in our Universe and the Metaverse Our mission is to develop products and applications on the AstroChain blockchain that will enhance the web3 user experience.
Owner privileges
Comments
Ownership Privileges:
The owner of the contract can authorize other addresses to make critical changes in the contract and these wallets may still be authorized to write state variables even after the ownership is renounced. Furthermore, there can be 'n' numbers of wallets that the owner can authorize which means there is no maximum limit on authorized wallets and technically all of them will be able to make the changes described below in section 1.2.
The contract has 3 modifiers - onlyToken, onlyOwner, and authorized.
1.1 The token address/wallet can perform the following actions in the Dividend Distributor contract:
- Set the distribution criteria which will set the minimum period and minimum distribution values.
- Set/Assign shares to other accounts with any arbitrary number
- Deposit tokens in the contract
- Process accounts for dividends
1.2 "authorized" modifier privileges:
- Launch the contract, and Enable/Disable trading to lock user funds
- Change the staking address to any other address which may be controlled by the authorized wallet and can be used to drain staked funds
- Trigger Buyback and clear buyback multiplier.
- Set auto buyback and buyback multiplier settings with any arbitrary values, even set to zero is also possible
- Set transaction limit but within limitations, which means it cannot be set to zero. The requirement is that it must be less than or equal to the value of the total supply divided by "1000"
- Include/Exclude wallets from max tx limit, fees, and dividends.
- Set fee receivers, target liquidity(both the liquidity and the denominator), distribution criteria, and swap threshold to any values because there are no checks in place
- The treasury fee receiver will receive the amount when the swap back function is called. SImilar for liquidity receiver address.
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
67
State variables
public
22
Total lines
of code
799
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.
medium Issues
Pending
#1 Issue
Fees can be 100% or more
L751
The authorized addresses(if any) can change the fees in the contract even after the ownership is renounced and according to the logic, the fees can be set up to 100% or more which is not recommended. However, if the fee is set to more than 100% then the transfer transactions may revert or the users can lose all of their funds.
low Issues
Pending
#1 Issue
Missing Events Arithmetic (events-maths)
L280-283
L702-709
L711-716
L728-731
L751-759
L766-769
L771-774
Emit an event for critical parameter changes.
Pending
#2 Issue
Missing Zero Address Validation (missing-zero-check)
L162
L560
L761
L761
Check that the address is not zero.
Pending
#3 Issue
Floating Pragma
-
The current pragma Solidity directive is â^0.8.0". 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
#4 Issue
Contract doesnât import npm packages from source (like OpenZeppelin etc.)
-
We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L718-720
L78-83
L67-69
L85-90
L10-16
L37-42
L44-49
L25-35
L18-23
Remove unused functions.
Pending
#2 Issue
Function initializing state variables (function-init-state)
L411
L463
Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.
Pending
#3 Issue
Unused state variables (unused-state)
L400
L404
Remove unused state variables.
Pending
#4 Issue
Unused return values (unused-return)
L618-660
Ensure that all the return values of the function calls are used.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L400
L402
L404
L403
L410
L242
L255
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L134-136
L141-143
L162-166
L722-726
Use the `external` attribute for functions never called from the contract.
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.