Siri Info
SIRIUS IS KNOWN AS THE "DOG STAR" IN EGYPTIAN MYTHOLOGY, IN CHINESE MYTHOLOGY, IT'S CALLED THE "CELESTIAL WOLF", AND IN JAPANESE, IT'S CALLED THE "HEAVENLY WOLF", REFLECTING BOTH ITS IMPORTANCE AND PROMINENCE IN THE NIGHT SKY. SIRIUS ($SIRI) WILL BE THE HOTTEST TOKEN IN THE CRYPTOVERSE, BRINGING PROSPERITY AND HAPPINESS TO ALL HER HOD LERS.
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.
TrustNet DataPulse
0xeD6e09024ef262Cd24312DfE313726142Fad9388
0x3710D96cA960a40f47729ac3ab2A7F3F7849Cc40
Data provided by 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.
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 can blacklist addresses
It is 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
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:
- 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 can enable trading only once.
- The owner can remove limits from the contract.
- The owner can update any arbitrary amount in the minimum swap amount.
- The owner can update the max transaction and wallet amount to any arbitrary amount including zero.
- The owner can exclude wallets from max transaction limits.
- The owner can enable/disable swapping.
- The owner can set total buy and sell fees of more than 25%.
- The owner can exclude wallets from fees.
- The owner can add an automated market maker pair address.
- The owner can update any arbitrary address as the marketing wallet address.
- The owner can blacklist wallets from transferring of tokens.
- The owner can remove wallets from the blacklist list.
- The owner can update the booster wallet and percentage in the contract.
- The owner can withdraw ETH and tokens from the contract.
- The owner can transfer the liquidity percentage to the booster wallet address.
Note - This Audit report consists of a security analysis of the Star Siri smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, we only audited one token contract for the Star Siri team. Other contracts associated with the project were not audited by our team. We recommend investors 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 | 5 findings
Pending
#1 medium Issue
The owner can lock funds.
The owner can set any arbitrary amount in the max transaction and max wallet amount, including zero, which is not recommended as this can lock the transfer function for an unlimited period of time. There must be a threshold amount so that the amount cannot be set to zero. Add a 'require' check in the contract so that the amount cannot be less than at least 0.1% of the total supply of tokens.
Pending
#2 medium Issue
Transfer of tokens without enabling trade.
The trading needs to be enabled by the owner in order for regular users to transfer tokens. On the contrary, the owner can authorize addresses manually and those addresses will be able to trade tokens. This functionality can be exploited in the following way, For example, there is a presale and the wallets used for the presale can be authorized by the owner. All the tokens obtained can be consolidated into a final wallet address and facilitate trading and selling of the acquired tokens, the last wallet address can be authorized.
Pending
#3 medium Issue
The owner can set fees more than 25%.
The owner can set the total buy and sell fees of more than 25% in the contract which is not recommended. The fees in the contract should not be more than 25% so that the user not lose his token values.
Pending
#4 medium Issue
The owner can blacklist wallets.
The owner can blacklist wallets from transferring tokens for an unlimited period of time which is not recommended as this can lock the user's funds indefinitely. There must be a locking period in the contract so that the user should not be locked for an unlimited period of time.
Pending
#5 medium Issue
Missing 'require' check. (Potential honeypot)
The owner can set any arbitrary amount to the marketing wallet address, including zero address as this can lead to a potential honeypot if the owner has set the address to a contract address that cannot receive ETH. It is recommended that the address cannot be set to a contract address that cannot receive ETH to avoid these circumstances.
low Issues | 5 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#3 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Pending
#4 low Issue
Floating pragma solidity version.
Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.
Pending
#5 low Issue
Remove safemath library
The compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow. It is recommended to remove the unwanted code in order to avoid high gas fees.
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 | 1 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.