Coin Raffle
At CoinRaffle.io, we are committed to transparency, security, and fostering thriving crypto communities. Join us on this journey where community growth meets practical token utility. Unleash the potential of your project with CoinRaffle.io today!
Owner privileges
Comments
Ownership Privileges
- The owner can withdraw tokens and ETH from the contract.
- The owner can update the coin raffle wallet address.
- The owner can set the coinraffle bps between 0 to 99.
- The owner can end the game.
- The owner can abort games in progress.
- The owner can abort all games at once.
The contract is also deployed to FTM chain, here's the link of the contract:
https://ftmscan.com/address/0xb424fb772432654fb41fb1695a80d29463f926db#code
Note - This Audit report consists of a security analysis of the Coin Raffle 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 Coin Raffle team. Our team did not audit other contracts associated with the project. 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
87
State variables
public
15
Total lines
of code
992
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.
informational Issues
Pending
#1 Issue
Costly operations in a loop (costly-loop)
L744-751
Use a local variable to hold the loop computation result.
Pending
#2 Issue
Missing Events Arithmetic (events-maths)
L913-921
Emit an event for critical parameter changes.
optimization Issues
Pending
#1 Issue
State variables that could be declared constant (constable-states)
L691-692
Add the `constant` attributes to state variables that never change.
Pending
#2 Issue
Public function that could be declared external (external-function)
L89-95
L203-212
L214-229
L231-252
L258-305
L753-770
L792-845
L852-874
L876-880
L882-886
L888-892
L901-911
L913-921
L923-960
L984-991
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.