MarkElon
Money can't buy you happiness, but can $230 billion buy you a TKO? Elon Musk is apparently ready to find out, with the world's richest man having challenged Mark Zuckerberg to a "cage match" â an offer that the martial arts-loving Facebook co-founder quickly agreed to. For over six years, two of techs biggest names â Elon Musk and Mark Zuckerberg â have been caught up in a feud, clashing over topics like artificial intelligence and rockets. If you thought that a cage fight between two of the worldâs richest men was just a far-fetched social media stunt, think again.
Owner privileges
Comments
Ownership Privileges
- The owner can enable trading only once.
- The owner can transfer tokens to multiple addresses at once.
- The owner can enable/disable swapping.
- The owner can rescue swap tokens to the marketing wallet address.
- The owner can set buy, sell, and transfer fees of not more than 10%.
- The owner can whitelist addresses from fees.
- The owner can set the automated pair address.
- The owner can update the marketing, dev, and reward wallet address.
- The owner can reset all taxes to zero.
- The contract balance of the token can be withdrawn automatically to the marketing wallet address if the rescueSwap is set to true even after the ownership of the token is renounced.
Note - This Audit report consists of a security analysis of the MarkElon 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 MarkElon team. Other contracts associated with the project were not audited by our team. We recommend investors do their own research before investing.
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
98
State variables
public
29
Total lines
of code
1274
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.
medium Issues
Pending
#1 Issue
Transfer of tokens without enabling trade.
L1109-1111
The trading needs to be enabled by the owner in order for regular users to transfer tokens. On the contrary, the owner can authorize addresses manually and those addresses will be able to trade tokens. This functionality can be exploited in the following way, For example, there is a presale and the wallets used for the presale can be authorized by the owner. All the tokens obtained can be consolidated into a final wallet address and facilitate trading and selling of the acquired tokens, the last wallet address can be authorized.
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L930
L934
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L1038-1045
L1047-1054
L1056-1063
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L1082
L1087
L1092
Check that the address is not zero.
Pending
#4 Issue
Floating pragma solidity version
L3
Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.
Pending
#5 Issue
Remove safemathint and uint library
L651-717
compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow, It is recommended to remove the unwanted code in order to avoid high gas fees.
informational Issues
Pending
#1 Issue
Unused state variables (unused-state)
L653
Remove unused state variables.
Pending
#2 Issue
Unused write (write-after-write)
L1238
Fix or remove the writes.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L205-207
L213-215
L230-232
L237-239
L256-259
L264-266
L275-278
L293-301
L315-318
L334-337
L614-616
L633-636
L1220-1225
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.