BTCINU
0x3cce423604205e53b148A87254038C55756b8838 0x3cce...6b8838

Static analysis Dynamic analysis Symbolic Execution SWC check

This is the modern solution to make gains with Memecoins fast and easy. After a long and intensive research, the team is determined that BTCINU is able to combine BTC and SHIB into one concentrated MEMECOIN with ENORMOUS POTENTIAL! Thanks to the high level of awareness and acceptance of Bitcoin and the massive flood of new Memecoin investors through Shiba Inu, BTCINU can combine the strenghts of both predecessors and ATTRACT new investors.

Contract address
0x3cce...6b8838
Network Ethereum Mainnet
License MIT
Compiler v0.8.18 v0.8.18+commit.87f61d96
Type N/A
Language Solidity
Request date 2023/11/28
Revision date 2023/11/28
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 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.
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 create the presale.
  • The owner can end presale.
  • The owner can update the start time, end time, price, tokens to sell, and usdt hard cap value in the presale.
  • The owner can update the fund wallet address in the contract.
  • The owner can update the USDT token address in the contract.
  • The owner can pause/unpause presale functionality in the contract.
  • The owner can withdraw the tokens from the contract to the fund receiver address.
  • The owner can withdraw the contract funds to the Fund receiver wallet.
  • The owner can set any arbitrary address as the btcinu token which can lock the claim functionality if it is set to zero address.

Note - This Audit report consists of a security analysis of the BTCINU 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 BTCINU 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

32

State variables
public

9

Total lines
of code

683

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

Owner can lock function.

BtcInuSale.sol

L680-682

Description

The owner can set any arbitrary address as the btcinu address including zero address which can lock the claim function of the contract and user will not be able to claim their tokens. Also, The owner can change the address in mid claim which can loss of funds for the users. For Example, If the user buys one token and at the time of claim the token address is changed then owner will lose its funds.

low Issues

Pending

#1 Issue

Missing Zero Address Validation (missing-zero-check)

BtcInuSale.sol

L383

L680

Description

Check that the address is not zero.

Pending

#2 Issue

Floating pragma solidity version.

BtcInuSale.sol

L8

Description

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.

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

BtcInuSale.sol

L248-260

L109-120

L122-128

L130-142

L144-164

L193-203

L205-218

L166-176

L178-191

L92-94

L96-107

L236-246

L220-234

L42-44

Description

Remove unused functions.

optimization Issues

Pending

#1 Issue

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

BtcInuSale.sol

L72-74

L76-82

L420-423

L650-670

L680-682

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.