$SPACESHIBA Info
$SPACESHIBA is a meme coin that strives to merge humor, community, and blockchain technology to create a novel experience for cryptocurrency enthusiasts. By building on the Ethereum blockchain, $SPACESHIBA benefits from
Overall Score
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
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 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 renounced
Contract cannot be manipulated by owner functions.
Scope of Work
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
- Include/Exclude wallets from rewards and fees
- Set marketing wallet address
- Set buy and sell fee, but cannot set it more than 25%
- Set liquidity threshold to any arbitrary value.
- Enable/Disable Swap and Liquify
- Set max transaction value, but it must be at least 25% of the total supply
Moreover, the contract features an "Ownership Lock" function where the owner can lock their ownership for a particular amount of time. Only after that time is passed can it become active again. Please beware of the lock duration passed while locking the ownership because there are no limits on the function and if it is set really far in the future by accident then the ownership will be locked forever.
Note - This Audit report consists of a security analysis of the SpaceShiba Token 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 SpaceShiba team, other contracts associated with the project were not audited by our team. We recommend investors to do their own research before investing.
-------------------
Note - The owner has renounced the ownership in the following TX: https://etherscan.io/tx/0xc01a8d3a8e2dbdee7585032980fbd7ddd10f52ed1ede91f4f4c1b4855594e1e5
That means, that the owner cannot regain the ownership anymore.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
medium Issues | 1 findings
Resolved
#1 medium Issue
Owner can regain ownership
The owner can regain ownership after transferring it with the following steps: Call lock function to set _previousOwner to the own address Call unlock function to get ownership back Transfer/renounce ownership Call unlock function to get ownership back Make sure to set the _previousOwnership back to address zero after using the unlock function
low Issues | 4 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
State variable visibility is not set
It is best practice to set the visibility of state variables explicitly
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 | 3 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 return values (unused-return)
Ensure that all the return values of the function calls are used.
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:
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.