As owner of Cointalk Germany we decided to launch our first Project with our Community Members. We wanted to give our Community a safe place to ape and we are super excited to be on the Arbitrum-Chain. The Arbitrum-Chain is super fast and has lower fees compared to the Ethereum-Chain while also using ETH. We are the Kings and Queens of Arbitrum and now it’s our chance to take a position in this bear market because we are sure that this chain gonna blow up in the next bull run.
The contract has two modifiers after the ownership is renounced - onlyToken, and authorized
onlyToken (deployer or distributorOwner address) had the following privileges:
- Set distribution criteria, min period and min distribution to any arbitrary values including zero
- Set shares for any address
- Deposit ETH in the contract, and process dividends
- Claim dividend for a shareholder. Hence, the shareholders cannot claim the dividends by themselves
- Change distributor Owner address
- Withdraw ETH from the contract
authorized Addresses had the following privileges:
- Enable/Disable trading and lock user funds
- Enable/Disable the fee in the contract
- Set max wallet, and transaction limit
- End happy hour but cannot start it again
- Change fees, but cannot set it more than 25%
- Change swapBack settings and distribution criteria
- Process Dividends
- Set router, and pair address
- Include/Exclude wallets from fee, tx limit, and dividends
- Change Fee Receiver address
Since the ownership is renounced and the blacklist status is true, the blacklisted wallets can never be removed from the blacklist
Note - The privileges mentioned above are not applicable now as the ownership has been completely renounced. But we cannot confirm whether an authorised address exists or not.
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.
Missing Events Access Control (events-access)
Emit an event for critical parameter changes.
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.
Functions that are not used (dead-code)
Remove unused functions.
Function initializing state variables (function-init-state)
Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.
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.
State variables that could be declared constant (constable-states)
Add the `constant` attributes to state variables that never change.
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
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.