Flasko
0x1B8EAcf3D0f1B151925b1686b8ce089ae050e3b8 0x1B8E...50e3b8

Static analysis Dynamic analysis Symbolic Execution SWC check

INVEST IN WHISKEY, WINES AND CHAMPAGNES.

Contract address
0x1B8E...50e3b8
Network Ethereum Mainnet
License MIT
Compiler v0.8.15 v0.8.15+commit.e14f2714
Type N/A
Language Solidity
Request date 2022/08/31
Revision date 2022/12/16
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

  • Owner can lock user funds by setting "maxTxAmount" to 0
  • liquidity will be added to the owner address
  • Tokens will be burned while transferring but only if the contract take fees from the sender

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

90

State variables
public

15

Total lines
of code

732

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

State variables shadowing (shadowing-state)

Flasko.sol

L444

Description

Remove the state variable shadowing.

low Issues

Pending

#1 Issue

Missing Events Arithmetic (events-maths)

Flasko.sol

L512-515

L525-528

L628-637

L639-648

Description

Emit an event for critical parameter changes.

Pending

#2 Issue

Missing Zero Address Validation (missing-zero-check)

Flasko.sol

L500

Description

Check that the address is not zero.

Pending

#3 Issue

Visibility is missing

Flasko.sol

L420

Description

Visibility of state variable is missing. Please add explicitly a visibility.

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

Flasko.sol

L140-146

L167-178

L161-166

L153-155

L157-159

Description

Remove unused functions.

Pending

#2 Issue

Wrong comment

Flasko.sol

L719

Description

"Can't withdraw negative or zero" comment is wrong. An uint256 cannot be negative.

optimization Issues

Pending

#1 Issue

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

Flasko.sol

L98-101

L107-111

L126-128

L129-131

L132-134

L469-471

L475-478

L479-481

L482-485

L486-490

L491-494

L495-498

L507-510

L516-518

L520-522

L628-637

L639-648

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.