Introducing TrumpArmy – the crypto meme token that’s going to make waves in the digital asset world! TrumpArmy is a unique digital token that pays homage to the meme culture and the spirit of the TrumpArmy. The project is built on the Finance Smart chain and is designed to create a fun and engaging experience for crypto investors and meme enthusiasts alike. The TrumpArmy token is designed to be a reflection of the community that supports it. It will be used as a form of payment within the community and will have real-world value. The token will be available for purchase on various crypto exchanges and will be tied to the value of the Binance smart chain.
- Withdraw foreign tokens from the contract
- Include/Exclude accounts from fees and dividends
- Set/Update marketing wallet
- Set liquidity threshold but it must be greater than 0.001% of the total supply
- Process account for dividends manually
- Set the last processed index to any arbitrary value
- Update claim wait but it must be between 1 and 24 hrs
Note - This Audit report consists of a security analysis of the TRUMP Army 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 TRUMP Army team, other contracts associated with the project were not audited by our team. We recommend investors to do their own research before investing.
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.
Hover on items
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.
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Local variables used prior their declaration (variable-scope)
Move all variable declarations prior to any usage of the variable, and ensure that reaching a variable declaration does not depend on some conditional if it is used unconditionally.
Functions that are not used (dead-code)
Remove unused functions.
Unused state variables (unused-state)
Remove unused state variables.
Unused return values (unused-return)
Ensure that all the return values of the function calls are used.
Uninitialized local variables (uninitialized-local)
Initialize all the variables. If a variable is meant to be initialized to zero, explicitly set it to zero to improve code readability.
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.