Catgirl Optimus
With the Optimus narrative currently taking the internet by storm, $OPTIG aims to capitalize on Elon Musk's upcoming Catgirl version of the Optimus robot, which he has mentioned many times on Twitter. $OPTIG is a community-driven project, made to pay homage to Elon's vision of a Catgirl Optimus Robot, through the blockchain. We are decentralized, with a vision of becoming a top 100 cryptocurrency and being recognized by Elon Musk.
Owner privileges
Comments
Owner privileges
- Enable
- trading once
- Disable
- limits once
- transfer delay once
- Enable/Disable
- _isExcludedMaxTransactionAmount
- _isExcludedFromFees
- _setAutomatedMarketMakerPair
- Update
- maxTransactionAmount
- maxWallet
- marketingWallet
- devWallet
- lpBurnFrequency
- percentForLPBurn
- lpBurnEnabled
- Buy-/Sellfees up to max 10% in total for both
- MarketingFee
- LiquidityFee
- DevFee
- Owner is able to burn the liquidity pair tokens manually by calling the "manualBurnLiquidityPairTokens"
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
83
State variables
public
31
Total lines
of code
1608
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)
L1143
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L1200-1215
L1217-1223
L1225-1231
L1245-1255
L1257-1267
L1538-1554
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L1292
L1300
Check that the address is not zero.
Pending
#4 Issue
Tautology or contradiction (tautology)
L1548
Fix the incorrect comparison by changing the value type or the comparison. "_percent" cannot be lower than 0 because it is an uint256 type variable.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L35-37
L503-518
L678-680
L776-785
L736-738
L802-811
L753-762
L607-613
L649-654
L661-666
L632-642
L620-625
Remove unused functions.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L1058
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L93-95
L101-104
L290-292
L298-300
L315-317
L341-344
L349-351
L360-363
L378-392
L406-409
L425-433
L1274-1284
L1305-1307
Use the `external` attribute for functions never called from the contract.
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.