Shinigami Info
SHINIGAMI’SPROPOSALBASEDSYSTEM ISDETERMINEDTHROUGH A TOKEN HOLDERCOUNTBASEDSYSTEM TOPROVIDETHECOMMUNITY POWERTODIRECT ASTO WHERETHEPROJECTSHOULDGO SHINIGAMI SWAP WILL PROVIDE YOU WITH A FASTER WAY TO BUY AND SELL USING OUR CUSTOM SWAP UTILITY, WHICH WILL ALSO BE PAIRED WITH FLOOZ FOR DIRECT CREDIT OR DEBIT CARD PAYMENTS
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 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.
Token transfer can be locked
Owner can lock user funds with owner functions.
Token can be burned
There is a function to burn tokens in 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 can Enable/Disable trading anytime. Although in the comment on L1004 it is mentioned that "once enabled, can never be turned off", but the is no check in the code for it. Hence, the owner can change the status of 'trading active' to true or false at any time.
- Remove limits and disable transfer delay.
- Change the minimum amount of tokens to sell from fees but within a range.
- Update/Set the maximum transaction amount but not lower than 0.1%
- Update/Set the maximum wallet amount
- Include/Exclude wallets from the maximum transaction limit and fees
- Disable the swap and lock user funds
- Update/Set buy and sell fees but less than or equal to 25%
- Set a new AMM, marketing wallet, and dev wallet
- Set auto LP burning settings within a range on L1294
- Burn 10% of tokens in LP every 30 minutes (by default) and also update the lp burn frequency at a minimum of 10 minutes which means the owner can manipulate the price of the token
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
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
Redundant Code
The "_basicTransfer" function is redundant because it has no instructions inside it rather than an event emission.
Pending
#4 low Issue
Dangerous usage of `tx.origin` (tx-origin)
Do not use `tx.origin` for authorization. An attacker can bypass the transfer-delayed functionality. We recommend using msg.sender for verification of the sender
informational Issues | 1 findings
Pending
#1 informational Issue
Unused return values (unused-return)
Ensure that all the return values of the function calls are used.