Azuki Pepe Info
A unique and stylish NFT collection created by the Azuki 2.0 Developers team. We are an art collection and a complex ecosystem around NFTs. NFT owners can enjoy special privileges such as participating in the Azuki Pepe community, owning limited editions, and even trading on NFT marketplaces.
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.
On-Chain Insights
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
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
- Swap the contract's balance manually
- Authorize/Unauthorize addresses that can trade tokens even when the trading is not enabled.
- Can enable trading only once.
- Set buy/sell fees not more than 5%.
- Set swap threshold amount, but it must be less than or equal to 1% of the total supply
- Set marketing wallet address, and this is the wallet where the liquidity will be credited automatically
- Withdraw any tokens from the contract including the native ones, Basically, owner can drain the contract's balance.
- Include/Exclude addresses from fees.
Note - This Audit report consists of a security analysis of the Azuki Pepe 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 Azuki Pepe 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
Findings and Audit result
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.
medium Issues | 2 findings
Pending
#1 medium Issue
Authorized addresses can transfer the tokens without Enabling Trade
The trading needs to be enabled by the owner in order for regular users to transfer tokens. On the contrary, the owner can authorize addresses manually and those addresses will be able to trade tokens. It is recommended to enable trading during deployment so that this functionality cannot be exploited.
Pending
#2 medium Issue
Liquidity is adding to externally owned address.
The liquidity of the contract is automatically added to the Marketing Wallet address which is not recommended because, in an extreme scenario, this can be used to drain liquidity from the contract.
optimization Issues | 2 findings
Pending
#1 optimization Issue
State variables that could be declared constant (constable-states)
Add the `constant` attributes to state variables that never change.
Pending
#2 optimization Issue
Public function that could be declared external (external-function)
Use the `external` attribute for functions never called from the contract.
informational Issues | 2 findings
Pending
#1 informational Issue
Function initializing state variables (function-init-state)
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
#2 informational Issue
Unused state variables (unused-state)
Remove unused state variables.
This audit covered the following files listed below with a SHA-1 Hash. The Team mentioned above provided us with the files that need to be evaluated.
A file with a different Hash has been intentionally or otherwise modified 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.