Richie Rich Info
$RICHIE is a meme token built on the BNB Smart Chain. Holders receive BNB rewards by holding $RICHIE tokens in their wallets.
Overall Score
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.
TrustNet DataPulse
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 burn function within the contract.
Ownership is not renounced
Contract can be manipulated by owner functions.
Scope of Work
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.
Ownership Privileges
- The owner can exclude/include wallets in rewards.
- The owner can exclude/include wallets from fees.
- The owner can claim the contract's stuck tokens, including the contract's tokens.
- The owner can claim the contract's balance in his wallet.
- The owner can set any arbitrary value in the maximum transaction amount including zero.
- The owner can set any arbitrary amount in the minimum swap amount.
- The owner can set buy fees of more than 100%.
- The owner can set any arbitrary amount in the buyback limit including zero.
Note - This Audit report consists of a security analysis of the Richie Rich 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 Richie Rich team. Other contracts associated with the project were not audited by our team. We recommend investors 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
medium Issues | 3 findings
Pending
#1 medium Issue
The owner can lock tokens.
The owner can set any arbitrary value in the max transaction amount, including zero. This can lock the transfer functionality of the contract. There must be a threshold amount where the max transaction amount cannot get below that number.
Pending
#2 medium Issue
The owner can set fees more than 100%.
The owner can set any arbitrary value in the reward, buyback, and marketing fees, which can lock the tokens, and the user may lose their value. It is recommended that no fees should be more than 25% in the contract.
Pending
#3 medium Issue
Missing 'require' check (potential honeypot)
The owner can set any arbitrary address as the marketing wallet address, which is not recommended if the address is set to any contract address that cannot receive ETH. Add a 'require' check that the marketing wallet address cannot be set to a contract address.
low Issues | 4 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#3 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Pending
#4 low Issue
Remove safemath library
Compiler version above 0.8.0 has the ability to control arithmetic overflow/underflow. It is recommended to remove the unwanted code in order to avoid high gas fees.
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 | 2 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
Pending
#2 informational Issue
Unused state variables (unused-state)
Remove unused state variables.
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:
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.