RNJToken Info
RNJ Token is a BNB Chain-based utility token designed for climbers, outdoor enthusiasts, and social impact initiatives. It supports real-world climbing missions, rescue programs, and environmental efforts through blockchain transparency and community-powered campaigns.
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 cannot set high fees
The fees, if applicable, can be a maximum of 25% or lower. The contract can therefore not be locked. Please take a look in the comment section for more details.
Contract cannot be locked
Owner cannot lock any user funds.
Token cannot be burned
There is no burning within the contract without any allowances
Ownership is not renounced
The owner retains significant control, which could potentially be used to modify key contract parameters.
Contract is not upgradeable
The contract does not use proxy patterns or other mechanisms to allow future upgrades. Its behavior is locked in its current state.
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.
Ownership Privileges
- The owner can set fees not more than 1%.
- The owner can lock fees only once.
- The owner can enable/disable the post-launch tax.
- The owner can permanently lock the post-launch tax configuration.
- The owner can permanently lock the post-launch tax configuration.
- The owner can disable taxes permanently.
- The owner can exempt an address from fees.
- The owner can exempt multiple addresses from fees.
- The owner can lock the list of fee-exempt addresses.
- The owner can set a DEX pair address.
- The owner can set multiple DEX pair addresses.
- The owner can lock the list of DEX pair addresses.
- The owner can set the number of anti-bot blocks.
- The owner can pause/unpause the contract.
- The owner can permanently disable the pause feature.
- The owner can start the presale.
- The owner can activate the token launch.
- The owner can finalize the launch.
- The owner can add an address to the whitelist.
- The owner can remove an address from the whitelist.
- The owner can lock the whitelist.
- The owner can add multiple addresses to the whitelist.
- The owner can set the founder's wallet address.
- The owner can authorize an airdrop sender address.
- The owner can enable the airdrop bypass.
- The owner can authorize a presale distributor address.
- The owner can unlock airdrops.
- The owner can enable or disable the token burn feature.
This contract is administered by a multisignature wallet, ensuring that any modifications to its settings or execution of privileged functions require consensus from multiple authorized individuals.
Note - This Audit report consists of a security analysis of the RNJToken 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 RNJToken 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
high Issues | 1 findings
Resolved
#1 high Issue
The owner can pause the token transfer
The contract's _update function, which handles all token transfers, contains a check that reverts transactions if the contract is in a paused state. This paused state can be activated at any time by the contract owner through the pause() function. There is no time limit for how long the contract can remain paused, nor is there any mechanism for users or a community to override this state. This creates a critical centralization risk where the owner can unilaterally and indefinitely freeze all user assets, preventing anyone from transferring their tokens. Furthermore, the owner could call pause() and then immediately call lockPauseForever(), which would make the paused state irreversible and permanently lock all funds in the contract.
informational Issues | 2 findings
Pending
#1 informational Issue
Floating pragma solidity version.
Adding the constant version of solidity is recommended, as this prevents the unintentional deployment of a contract with an outdated compiler that contains unresolved bugs.
Pending
#2 informational Issue
Function that are not used (Dead code).
It is recommended to check that the address cannot be set to zero or dead address.