Ripmex
0xc49bda8D35C450D7CE70A7530C1C42F9cC4169ba 0xc49b...4169ba

Static analysis Dynamic analysis Symbolic Execution SWC check

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.

Contract address
0xc49b...4169ba
Network Binance Smart Chain
License MIT
Compiler v0.8.18 v0.8.18+commit.87f61d96
Type N/A
Language Solidity
Request date 2024/02/29
Revision date 2024/03/02
Critical
Passed
High
Passed

Owner privileges

Crucial issues found The contract does contain issues of high or medium criticality. In some circumstances, the Contract may not function as intended and may pose a safety risk.
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 burn function within the contract.
Ownership is not renounced Contract can be manipulated by owner functions.
Comments

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.

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)
The auditing process follows a routine series of steps:
  • 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

108

State variables
public

10

Total lines
of code

1004

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

The owner can mint tokens

Ripmex.sol

L488-496

Description

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 Issue

The owner can blacklist wallets

Ripmex.sol

L511-514

Description

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 Issue

Liquidity is added to externally owned address.

Ripmex.sol

L713-726

Description

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 Issue

The owner can set fees more than 100%.

Ripmex.sol

L886-899

Description

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 Issue

The owner can lock tokens.

Ripmex.sol

L902-904

L998-1001

Description

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

Pending

#1 Issue

Local variables shadowing (shadowing-local)

Ripmex.sol

L548

L626

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Events Arithmetic (events-maths)

Ripmex.sol

L886-889

L891-894

L896-899

L902-904

L907-909

L998-1001

Description

Emit an event for critical parameter changes.

Pending

#3 Issue

Missing Zero Address Validation (missing-zero-check)

Ripmex.sol

L912

Description

Check that the address is not zero.

Pending

#4 Issue

Remove safemath library

Ripmex.sol

L30-78

Description

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.

informational Issues

Pending

#1 Issue

Costly operations in a loop (costly-loop)

Ripmex.sol

L613-624

Description

Use a local variable to hold the loop computation result.

Pending

#2 Issue

Functions that are not used (dead-code)

Ripmex.sol

L119-136

L102-104

L106-108

L110-112

L114-117

L82-91

L93-99

L12-15

L954-956

L70-72

L74-77

Description

Remove unused functions.

optimization Issues

Pending

#1 Issue

State variables that could be declared constant (constable-states)

Ripmex.sol

L426

L424

L425

Description

Add the `constant` attributes to state variables that never change.

Pending

#2 Issue

Public function that could be declared external (external-function)

Ripmex.sol

L161-164

L166-170

L172-174

L176-178

L180-185

L187-192

L488-496

L499-507

L522-524

L526-528

L530-532

L534-536

L543-546

L548-550

L552-555

L557-561

L563-566

L568-571

L573-575

L577-579

L581-583

L586-595

L603-611

L874-876

L878-880

L882-884

L993-996

L998-1001

Description

Use the `external` attribute for functions never called from the contract.

Diagrams

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.