PUDEL
0x6113E696A85cAcF0fE9E4Fd5F420598d9bA2fE85 0x6113...A2fE85

Static analysis Dynamic analysis Symbolic Execution SWC check

Pudel ($PD) is a decentralized finance (DeFi) token operating on the Binance Smart Chain (BSC). Unlike projects focused solely on farming and liquidity pool acquisition, Pudel aims to mitigate price fluctuations. Our ecosystem is designed to foster a stable and secure environment for our token holders.

Contract address
0x6113...A2fE85
Network Binance Smart Chain
License MIT
Compiler v0.8.7 v0.8.7+commit.e28d00a7
Type N/A
Language Solidity
Request date 2023/06/23
Revision date 2023/06/23
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 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

  • Include/Exclude wallets from rewards and fees
  • Set fees without any limitations
  • Enable/Disable Swap and Liquify
  • Set max transaction percent to any arbitrary value including zero and lock user funds
  • Withdraw any type of token from the contract
  • Include/Exclude addresses from the blacklist

Note - This Audit report consists of a security analysis of the PUDEL 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 PUDEL team, other contracts associated with the project were not audited by our team. We recommend investors to do their 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

103

State variables
public

12

Total lines
of code

979

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

Liquidity will be credited to an EOA

PUDEL.sol

L921

Description

The liquidity of the contract is automatically added to the owner's address which is not recommended because, in an extreme scenario, this can be used to drain liquidity from the contract.

Pending

#2 Issue

Fees can be 100% or more

PUDEL.sol

L615

L619

L653-675

Description

The owner can set the tax fee up to 100% or more and if done so then it may lead to the loss of user funds

low Issues

Pending

#1 Issue

Local variables shadowing (shadowing-local)

PUDEL.sol

L514

L776

Description

Rename the local variables that shadow another component.

Pending

#2 Issue

Missing Events Arithmetic (events-maths)

PUDEL.sol

L615-617

L619-621

L623-627

L653-656

L658-661

Description

Emit an event for critical parameter changes.

Pending

#3 Issue

State Variable Visibility not set

PUDEL.sol

L422

Description

It is the best practice to set the visibility of state variables explicitly

informational Issues

Pending

#1 Issue

Functions that are not used (dead-code)

PUDEL.sol

L110-127

L93-95

L97-99

L101-103

L105-108

L75-84

L85-91

L68-71

L53-55

L57-60

Description

Remove unused functions.

Pending

#2 Issue

Function initializing state variables (function-init-state)

PUDEL.sol

L390

L408

L411

Description

Remove any initialization of state variables via non-constant state variables or function calls. If variables must be set upon contract deployment, locate initialization in the constructor instead.

Pending

#3 Issue

Unused state variables (unused-state)

PUDEL.sol

L132

Description

Remove unused state variables.

Pending

#4 Issue

Unused return values (unused-return)

PUDEL.sol

L911-924

Description

Ensure that all the return values of the function calls are used.

optimization Issues

Pending

#1 Issue

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

PUDEL.sol

L132

L395

L393

L394

L389

L429

L386

Description

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

Pending

#2 Issue

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

PUDEL.sol

L151-154

L156-160

L488-490

L492-494

L496-498

L500-502

L509-512

L514-516

L518-521

L523-527

L529-532

L534-537

L539-541

L543-545

L547-554

L556-565

L573-582

L607-609

L611-613

L648-651

L772-774

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.