Rapper Token Info
Rapper Token Is A Listen To Earn Project That Adopts The Blockchain System To Bring Rap Artists And Listeners Together. Rapper Token Will Unite Rap Artists And Amateur Rap Artists Who Want To Deal With New Rap Under One Roof, With Future Updates And Innovations On The Platform, And The Products Produced By These Artists Will Be Sold On The Platform As A Marketplace, And Listeners And Users Will Be Able To Listen To These Products And Earn Daily Passive Income. With The Development Of This Application And The Adoption Of The NFT System, Artists Will Be Able To Convert Their Products Into NFT And Offer Their NFT Music For Sale. In Order To Be A Unique Rap Platform, Special Rap Tracks Will Be Produced Only For Rapper Token As Rapper Token And These Products Will Be Exhibited On The Platform. Creating A P2P Marketplace Will Thus Be Combined With Crypto In Order To Settle Into The System And Add Value To The Border, And Aim To Make The Platform A Universal Brand.
TrustNet Score
The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.
Real-Time Threat Detection
Real-time threat detection, powered by Cyvers.io,
is currently not
activated
for this project.
This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks.
For more information, click here.
Summary and Final Words
No crucial issues found
The contract does not contain issues of high or medium criticality. This means that no known vulnerabilities were found in the source code.
Contract owner cannot mint
It is not possible to mint new tokens.
Contract owner cannot blacklist addresses.
It is not possible to lock user funds by blacklisting addresses.
Contract owner can set high fees
Contract owner is able to set fees above 25%. Very high fees can also prevent token transfer.
Token transfer can be locked
Owner can lock user funds with owner functions.
Token cannot be burned
There is no burning within the contract without any allowances
Ownership is renounced
The contract does not include owner functions that allow post-deployment modifications.
Scope of Work
This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.
The auditing process consists of the following systematic steps:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.
A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.
Final Words
The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.
The Ownership is renounced but the authorized address can still make the following changes:
- Include/Exclude wallets from fees, transaction limit, dividends and timelock.
- Set fee receivers, target liquidity(both the liquidity and the denominator), distribution criteria, and swap threshold to any values because there are no checks in place
- Set tx limit to any arbitrary value including zero and lock user funds.
- Set Fees up to 100% or more if there is any other authorized address remain after the renouncing of the ownership
The contract has 3 modifiers - onlyToken, onlyOwner, and authorized.
The token address/wallet can perform the following actions in the Dividend Distributor contract:
- Set the distribution criteria which will set the minimum period and minimum distribution values.
- Set/Assign shares to other accounts with any arbitrary number
- Deposit tokens in the contract
- Process accounts for dividends
We recommend investors/users to do their own research before investing
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
high Issues | 1 findings
Resolved
#1 high Issue
Owner can drain funds
The owner is able to transfer tokens from any address by the airdrop function without approval because the "_basicTransfer" function has no checks for approval. Hence, funds can be transferred from any address to any address by the owner. We recommend to restrict the airdrop function to the owner's address only instead of passing a "from" parameter. Thus, replace the "from" parameter with "msg.sender" to make sure that only the funds of the owner will be transferred as an airdrop to addresses
medium Issues | 1 findings
Pending
#1 medium Issue
Fees can be 100%
The authorized addresses(if any) can change the fees in the contract even after the ownership is renounced and according to the logic, the fees can be set up to 100% or more which is not recommended.
low Issues | 5 findings
Pending
#1 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#2 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Pending
#3 low Issue
Floating Pragma
The current pragma Solidity directive is “^0.7.4". Contracts should be deployed with the same compiler version and flags that they have been tested thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions
Pending
#4 low Issue
Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities
Pending
#5 low Issue
Old Compiler Version
The contract uses an old compiler version and we don't recommend using it because old versions tend to have known vulnerabilities that may get exploited in the future.
optimization Issues | 2 findings
Pending
#1 optimization Issue
State variables that could be declared constant (constable-states)
Add the `constant` attributes to state variables that never change.
Pending
#2 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
informational Issues | 3 findings
Pending
#1 informational Issue
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.
Pending
#2 informational Issue
Unused state variables (unused-state)
Remove unused state variables.
Pending
#3 informational Issue
Unused return values (unused-return)
Ensure that all the return values of the function calls are used.