Astro Chain Info
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.
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 can set high fees
Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.
Token transfer can be locked
Owner can lock user funds with owner functions.
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:
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
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
medium Issues | 1 findings
Pending
#1 medium Issue
Fees can be 100% or more
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 | 4 findings
Pending
#1 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#2 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Pending
#3 low 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 low 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
optimization Issues | 2 findings
Pending
#1 optimization Issue
State variables that could be declared constant (constable-states)
Add the `constant` attributes to state variables that never change.
Pending
#2 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
informational Issues | 4 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
Pending
#2 informational Issue
Function initializing state variables (function-init-state)
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 informational Issue
Unused state variables (unused-state)
Remove unused state variables.
Pending
#4 informational Issue
Unused return values (unused-return)
Ensure that all the return values of the function calls are used.