PUDEL Info

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.

PUDEL Logo

TrustNet Score

The TrustNet Score evaluates crypto projects based on audit results, security, KYC verification, and social media presence. This score offers a quick, transparent view of a project's credibility, helping users make informed decisions in the Web3 space.

77.44
Poor Excellent

Real-Time Threat Detection

Real-time threat detection, powered by Cyvers.io, is currently not activated for this project.

This advanced feature provides continuous monitoring and instant alerts to safeguard your assets from potential security threats. Real-time detection enhances your project's security by proactively identifying and mitigating risks. For more information, click here.

TrustNet DataPulse

Security Assessments

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x6113...fE85
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/06/23
Revision date In progress

Summary and Final Words

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 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.

Scope of Work

This audit encompasses the evaluation of the files listed below, each verified with a SHA-1 Hash. The team referenced above has provided the necessary files for assessment.

The auditing process consists of the following systematic steps:

  1. Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
  2. Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
  3. Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
  4. Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
  5. Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
  6. Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
  7. Actionable Recommendations: Provide detailed, specific, and actionable steps to secure and optimize the smart contracts.

A file with a different Hash has been intentionally or otherwise modified after the security review. A different Hash may indicate a changed condition or potential vulnerability that was not within the scope of this review.

Final Words

The following provides a concise summary of the audit report, accompanied by insightful comments from the auditor. This overview captures the key findings and observations, offering valuable context and clarity.


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.

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

medium Issues | 2 findings

Pending

#1 medium 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 medium 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 | 3 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
PUDEL.sol
L514
L776
Description

Rename the local variables that shadow another component.

Pending

#2 low 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 low Issue
State Variable Visibility not set
PUDEL.sol
L422
Description

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

optimization Issues | 2 findings

Pending

#1 optimization 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 optimization 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.

informational Issues | 4 findings

Pending

#1 informational 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 informational 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 informational Issue
Unused state variables (unused-state)
PUDEL.sol
L132
Description

Remove unused state variables.

Pending

#4 informational Issue
Unused return values (unused-return)
PUDEL.sol
L911-924
Description

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