Ripmex Info
Ripmex; It aims to make it possible for banks, payment providers, digital asset exchanges and companies to send money and value globally, of any size, securely, with low transaction fees and almost free of charge, using advanced blockchain technology.
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.
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 can mint
It is possible to mint new tokens.
Contract owner can blacklist addresses
It is 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 not renounced
Contract can be manipulated by owner functions.
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 lock and unlock the ownership.
- The owner can withdraw ETH from the contract.
- The owner can mint an unlimited amount of tokens.
- The owner can burn his tokens.
- The owner can blacklist wallets from transferring tokens.
- The owner can exclude/include wallets in fees.
- The owner can set the tax fees, liquidity fees, and marketing fees more than 100%.
- The owner can update any arbitrary amount in the max transaction amount.
- The owner can update any arbitrary amount in the minimum swap amount.
- The owner can update any arbitrary address as the marketing wallet address.
- The owner can enable/disable swapping.
- The owner can set the fees and maximum transaction amount for presale.
- The owner can exclude wallets from the max wallet limit.
- The owner can set any arbitrary amount in the max wallet limit.
Note - This Audit report consists of a security analysis of the Ripmex 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 Ripmex 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 | 5 findings
Pending
#1 medium Issue
The owner can mint tokens
The owner can mint an unlimited amount of tokens, which is not recommended as this can manipulate the supply of tokens as this can manipulate the price of the tokens. it is recommended that there must be a fixed supply so that the tokens cannot be minted not more than that particular amount.
Pending
#2 medium Issue
The owner can blacklist wallets
The owner can blacklist wallets from transferring tokens for an indefinite period of time as this is not recommended. There must be a locking period so that the user should not be locked permanently in the contract.
Pending
#3 medium Issue
Liquidity is added to externally owned address.
The contract's liquidity is automatically added to the 'owner' address, which is not recommended because, in an extreme scenario, this can be used to drain liquidity from the contract.
Pending
#4 medium Issue
The owner can set fees more than 100%.
The owner can set any arbitrary amount in the tax, liquidity, and marketing fees in the contract, which is not recommended as this can cause the loss of funds for the users. It is recommended that the fees should not be more than 25% in the contract.
Pending
#5 medium Issue
The owner can lock tokens.
The owner can update any arbitrary amount in the max transaction and max wallet amount including zero as this can cause the lock of the transfer function in the contract. There must be a minimum threshold limit so that the transfer function should not be locked for an indefinite period of time.
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
The 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
Costly operations in a loop (costly-loop)
Use a local variable to hold the loop computation result.
Pending
#2 informational Issue
Functions that are not used (dead-code)
Remove unused functions.