The RADA
The RADA Foundation aims to purchase a football club with a solid global blockchain community to integrate technology, transparency, and accountability into club decision-making. Additionally, the Foundation established the RADA program to support youth players and provide a promising football industry opportunity.
Owner privileges
Comments
Ownership Privileges
- The owner can add/remove users from the whitelist, and only whitelisted users can lock/unlock their tokens
Note - This Audit report consists of a security analysis of the RADA 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 RADA 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
13
State variables
public
3
Total lines
of code
237
Capabilities
Hover on items
Functions
public
6
State variables
public
0
Total lines
of code
89
Capabilities
Hover on items
Functions
public
3
State variables
public
0
Total lines
of code
74
Capabilities
Hover on items
Functions
public
6
State variables
public
0
Total lines
of code
65
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
Owner can Lock tokens
L188
The owner is able to add/remove users from the whitelist at any time, and if the owner decides to remove the user after they have locked their tokens, then they will never be able to unlock their tokens. Thus, it will result in the lock of user funds till the owner doesn't add them back to the whitelist
low Issues
Pending
#1 Issue
Local variables shadowing (shadowing-local)
L75
L128
L141
Rename the local variables that shadow another component.
informational Issues
Pending
#1 Issue
Functions that are not used (dead-code)
L22-27
L13-20
Remove unused functions.
optimization Issues
Pending
#1 Issue
Public function that could be declared external (external-function)
L52-54
L60-63
Use the `external` attribute for functions never called from the contract.
Pending
#2 Issue
Public function that could be declared external (external-function)
L24-26
L39-52
L54-56
L58-60
L62-64
Use the `external` attribute for functions never called from the contract.
Pending
#3 Issue
Public function that could be declared external (external-function)
L67-69
L86-89
L95-98
L101-105
L152-162
L164-173
L188-198
L200-205
L232-236
Use the `external` attribute for functions never called from the contract.
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.