Neopunk Info
The Cypherpunks are a group of passionate individuals who advocate fiercely for the use of cryptography to challenge the current political and social norms that threaten our privacy. They actively contribute to the development of cutting-edge privacy-focused technologies to support their cause. Through the use of the Cypherpunks electronic mailing list, the group strives to achieve maximum privacy and security by proactively utilizing cryptography.
Team and KYC Verification
The KYC verification for this project is currently in progress.
The team has submitted their information and verification is pending.
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.
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.
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 burning within the contract without any allowances
Ownership is not renounced
The owner retains significant control, which could potentially be used to modify key contract parameters.
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:
- Specification Review: Analyze the provided specifications, source code, and instructions to fully understand the smart contract's size, scope, and functionality.
- Manual Code Examination: Conduct a thorough line-by-line review of the source code to identify potential vulnerabilities and areas for improvement.
- Specification Alignment: Ensure that the code accurately implements the provided specifications and intended functionalities.
- Test Coverage Assessment: Evaluate the extent and effectiveness of test cases in covering the codebase, identifying any gaps in testing.
- Symbolic Execution: Analyze the smart contract to determine how various inputs affect execution paths, identifying potential edge cases and vulnerabilities.
- Best Practices Evaluation: Assess the smart contracts against established industry and academic best practices to enhance efficiency, maintainability, and security.
- 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
- Set marketing wallet address, uniswap router address, and AMM Pair address
- Include/Exclude accounts from fees and limits
- Set/Update fees to any arbitrary value including 100% or more and lock user funds, which is not recommended
- Set max wallet and transaction amount limits but not to zero or nearby. Thus, tokens cannot be locked by these methods
- Withdraw stuck tokens from the contract. However, native tokens cannot be withdrawn
- Claim Marketing Fees from the contract
- Blacklist addresses manually which is not recommended as it gives the owner power to control the trade of the tokens
Note - This Audit report consists of a security analysis of the NEOPUNK 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 NEOPUNK 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
medium Issues | 3 findings
Pending
#1 medium Issue
Owner needs to Enable Trading
The trading needs to be enabled by the owner in order for regular users to transfer tokens. On the contrary, the owner can exclude addresses from the limits manually and those addresses will be able to trade tokens. This functionality can be exploited in the following way, For example, there is a presale and the wallets used for the presale can be excluded from fees by the owner. All the tokens obtained can be consolidated into a final wallet address and facilitate trading and selling of the acquired tokens, the last wallet address can be excluded from the limits.
Pending
#2 medium Issue
Liquidity will be credited to an EOA
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. However, this will be automatically mitigated once the ownership is renounced.
Pending
#3 medium Issue
Fees can be 100% or more
The owner is able to set the Buy and Sell fees up to 100% or more by changing the "maxFeePercent" state variable, which is not recommended as it may cause the users to lose their funds.
low Issues | 2 findings
Pending
#1 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#2 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
optimization Issues | 1 findings
Pending
#1 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
informational Issues | 1 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.