Matar AI
Welcome to MATAR, where cutting-edge AI meets the robust security of blockchain solutions. Explore the forefront of innovation as we seamlessly integrate artificial intelligence with blockchain technology, revolutionizing the way businesses operate and ensuring a secure, transparent, and efficient future. Join us on a journey of limitless possibilities at the intersection of AI and blockchain with MATAR.
Owner privileges
Comments
Ownership Privileges
- The owner can update the automated market maker pair address.
- The owner can whitelist wallets from fees.
- The owner can include wallets in fees.
- The owner can update the buy and sell taxes to not more than 4% and 6% respectively.
- The owner can update the tax wallet address.
- The owner can enable/disable trading.
- The owner can enable/disable fee burn.
- The owner can claim ETH from the contract.
- The owner can claim stuck tokens from the contract.
Note - This Audit report consists of a security analysis of the Matar AI Token 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 Matar AI team. Other contracts associated with the project were not audited by our team. We recommend investors to 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
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Functions
public
6
State variables
public
0
Total lines
of code
79
Capabilities
Hover on items
Functions
public
0
State variables
public
0
Total lines
of code
161
Capabilities
Hover on items
Functions
public
8
State variables
public
0
Total lines
of code
19
Capabilities
Hover on items
Functions
public
24
State variables
public
0
Total lines
of code
141
Capabilities
Hover on items
Functions
public
3
State variables
public
0
Total lines
of code
100
Capabilities
Hover on items
Functions
public
21
State variables
public
9
Total lines
of code
323
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
The owner can disable trading
L290-293
The owner can disable trading for the users who are not exempted, which is not recommended as this can lock the token for an indefinite period of time. It is recommended that the trading should not be disabled once enabled so that the user can transfer the tokens without any issues.
Pending
#2 Issue
Transfer of tokens without enabling trade
L195-235
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)
L95
L146
L164
Rename the local variables that shadow another component.
Pending
#2 Issue
Floating pragma solidity version
L2
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.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L25-27
L21-23
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L76-78
L84-89
Use the `external` attribute for functions never called from the contract.
Pending
#2 Issue
Public function that could be declared external (external-function)
L69-71
L73-75
L81-83
L85-87
L89-92
L101-104
L106-114
L116-125
L253-260
L262-269
L271-277
L279-283
L285-288
L290-293
L295-298
L300-303
L307-310
L312-322
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.