ArbCate
ArbCate was set to launch at March 2023 with the goal of being a decentralized meme project with true purpose. ArbCateâs mission is to bring popular cryptocurrency concepts to the mainstream. Unlike older, comparable projects, ArbCate introduces holders to concepts such as participation rewards, NFTs, decentralized exchanges, and more
Owner privileges
Comments
Note for Investors: We only Audited a reflection token contract for Arbcate. However, If the project has other contracts, and they were not provided to us then we cannot comment on its security and we are not responsible for it in any way.
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
99
State variables
public
23
Total lines
of code
1278
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)
L956
Rename the local variables that shadow another component.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L1015-1020
L1022-1025
L1027-1030
L1036-1046
L1048-1058
Emit an event for critical parameter changes.
Pending
#3 Issue
Missing Zero Address Validation (missing-zero-check)
L1086
L1091
Check that the address is not zero.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L17-20
L404-412
L581-583
L597-600
L705-708
L696-700
L676-682
L664-671
L687-691
L711-714
L718-722
Remove unused functions.
Pending
#2 Issue
Unused state variables (unused-state)
L659
L884
Remove unused state variables.
Pending
#3 Issue
Unused return values (unused-return)
L1224-1237
Ensure that all the return values of the function calls are used.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L211-213
L219-221
L236-238
L262-265
L270-272
L281-284
L299-307
L321-324
L340-343
L639-642
L648-652
L1070-1072
L1074-1078
L1097-1099
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.