Shinigami
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
Owner privileges
Comments
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
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
102
State variables
public
31
Total lines
of code
1369
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.
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L965
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L1005-1076
L1294-1300
Emit an event for critical parameter changes.
Pending
#3 Issue
Redundant Code
L1302
The "_basicTransfer" function is redundant because it has no instructions inside it rather than an event emission.
Pending
#4 Issue
Dangerous usage of `tx.origin` (tx-origin)
L1133
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
Pending
#1 Issue
Unused return values (unused-return)
L1236-1249
Ensure that all the return values of the function calls are used.
Diagrams
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.