Wall Street Pepes Info

wallstreetpepes.com

Hey there, meme maestros, crypto crusaders, and all-around cool cats – brace yourselves for the Wall Street Pepes (WSP) phenomenon! In a universe where finance meets memes, and hilarity reigns supreme, WSP takes center stage as the most outrageous, internet culture-infused cryptocurrency you've ever seen. We're not just here to make money; we're here to make you giggle, guffaw, and maybe even ROFL a time or two!



Overall Score
77.99
Poor Excellent
Wall Street Pepes Logo

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

Smart Contract Audit

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x847D...8887
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/10/03
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 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 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
  • The owner can lock/unlock the token, meaning the owner can renounce and transfer ownership to the previous owner's address.
  • The owner can exclude/include wallets in rewards.
  •  The owner can enable trading only once.
  • The owner can reset liquidity tokens, dev tokens, marketing tokens, charity tokens, and reserve tokens collected amount to zero.
  • The owner can update the totalSwapableFee and totalSwapableSaleFee to not more than 20%.
  • The owner can exclude and include wallets from fees.
  • The owner can set any arbitrary value, including zero, to the minimumTokenBeforeSwap amount.
  • The owner can change the marketing, charity, dev, and reserve wallet address.
  • The owner can enable/disable swapping.
  • The owner can enable/disable rescue swap, which means if the contract balance is greater than zero then the contract balance will be transferred to the marketing wallet address.
  • The owner can manually burn any arbitrary amount of tokens from his wallet.

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

Files and details

Functions
public

/

State variables
public

/

Total lines
of code

/

Capabilities
Hover on items

/

Findings and Audit result

low Issues | 4 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
WSP.sol
L464
L528
L603
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Floating pragma solidity version.
WSP.sol
L2
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.

Pending

#3 low Issue
Missing events arithmetic.
WSP.sol
L612-615
L653-659
Description

Emit all the critical parameter changes.

Pending

#4 low Issue
Missing visibility.
WSP.sol
L437
Description

Add 'public' or 'private' during the initialization of a state variable.

optimization Issues | 1 findings

Pending

#1 optimization Issue
Public function that could be declared external (external-function)
WSP.sol
L112-115
L123-125
L127-129
L131-136
L138-143
L502-504
L506-508
L510-512
L514-516
L523-526
L528-530
L532-535
L537-541
L543-546
L548-551
L553-555
L558-560
L653-659
Description

Use the `external` attribute for functions never called from the contract.

informational Issues | 2 findings

Pending

#1 informational Issue
Costly operations in a loop (costly-loop)
WSP.sol
L590-601
Description

Use a local variable to hold the loop computation result.

Pending

#2 informational Issue
Functions that are not used (dead-code)
WSP.sol
L69-86
L52-54
L56-58
L60-62
L64-67
L32-41
L43-49
L9-12
L1013-1025
L999-1002
Description

Remove unused functions.