Billicat
0x47a9B109Cfb8f89D16e8B34036150eE112572435 0x47a9...572435

Static analysis Dynamic analysis Symbolic Execution SWC check

BilliCat is a digital currency that originated from an internet meme featuring an adorable and charismatic cat. The meme gained significant traction on social media platforms, captivating audiences with its relatable humor and catchy catchphrases. As a result, a group of crypto enthusiasts saw an opportunity to turn this viral sensation into a blockchain-based asset, and thus, BilliCat was born. Like many meme tokens, BilliCat operates on BSC blockchain, utilizing its smart contract capabilities. This ensures transparency and security for its holders, as transactions are recorded on a decentralized ledger that can be audited by anyone. The token's supply is often limited to create a sense of scarcity and exclusivity, driving up demand and potentially increasing its value over time.

Contract address
0x47a9...572435
Network Binance Smart Chain
License None
Compiler v0.8.19 v0.8.19+commit.7dd6d404
Type N/A
Language Solidity
Request date 2023/12/25
Revision date 2023/12/25
Critical
Passed
High
Passed
Medium
Passed
Low
Passed

Owner privileges

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 burn function within the contract.
Ownership is renounced Contract cannot be manipulated by owner functions.
Comments

Ownership Privileges

  • The ownership of the contract is renounced. Hence, the owner cannot change the contract's settings.

Note - This Audit report consists of a security analysis of the Billicat 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 Billicat team; our team did not audit other contracts associated with the project. We recommend investors to 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

2

State variables
public

0

Total lines
of code

39

Capabilities
Hover on items

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

8

State variables
public

0

Total lines
of code

17

Capabilities
Hover on items

Functions
public

27

State variables
public

0

Total lines
of code

52

Capabilities
Hover on items

Functions
public

3

State variables
public

0

Total lines
of code

28

Capabilities
Hover on items

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Functions
public

11

State variables
public

0

Total lines
of code

365

Capabilities
Hover on items

Functions
public

0

State variables
public

0

Total lines
of code

47

Capabilities
Hover on items

Functions
public

19

State variables
public

0

Total lines
of code

95

Capabilities
Hover on items

Functions
public

5

State variables
public

0

Total lines
of code

44

Capabilities
Hover on items

Functions
public

3

State variables
public

0

Total lines
of code

83

Capabilities
Hover on items

Functions
public

3

State variables
public

0

Total lines
of code

57

Capabilities
Hover on items

Functions
public

1

State variables
public

0

Total lines
of code

15

Capabilities
Hover on items

Functions
public

10

State variables
public

7

Total lines
of code

238

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.

informational Issues

Pending

#1 Issue

Functions that are not used

ERC20.sol

L277-293

L251-264

Description

Remove unused functions.

optimization Issues

Pending

#1 Issue

Public function that could be declared external

ERC20.sol

L62-64

L70-72

L87-89

L94-96

L101-103

L113-117

L136-140

L158-163

L177-181

L197-206

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.