Zakujira Info
Created to show the rebirth and rise of the original meme and community projects such as Shiba,Floki, Akita, etc. Our goal is to attract like-minded investors who will work together for the overall success of the project and exemplify the true meaning of community-driven. Zakujira Is a multiple-utility token on the Ethereum block chain. DEX SWAP, COIN LISTING PLATFORM, TRADING PLATFORM, WALLET, and DEBIT CARD will be the main utilities. Our goal is to have a balanced ecosystem as a result of these projects.
Overall Score
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
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 renounced
Contract cannot 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:
- Include/Exclude accounts from rewards and fees
- Set taxes/fees to any arbitrary value, even more than 100%.
- Update Marketing Wallet, and Dev wallet address.
- Lock user funds by setting the maximum wallet balance to zero or very close to zero because there is no prevention against it.
- Stop users from buying or selling tokens by setting the maximum buy and sell amount to zero
- Enable/Disable the swap and update the amount to "swap tokens at", any arbitrary value.
- Blacklist addresses by manually setting them in the "Anti-Bot" mapping.
- Update the router and pair address.
- WIthdraw tokens from the contract, but not the native ones.
Note - The privileges mentioned above are no longer valid because the ownership has been renounced.
Files and details
Functions
public
/
State variables
public
/
Total lines
of code
/
Capabilities
Hover on items
/
Findings and Audit result
medium Issues | 1 findings
Resolved
#1 medium Issue
Fees can be 100% or more
The owner is able to set the fees up to 100% or even more which will lead in loss of user funds and may cause some functions to revert, It is recommended to limit the maximum fees under 25% which is to be set by the owner.
low Issues | 5 findings
Pending
#1 low Issue
Local variables shadowing (shadowing-local)
Rename the local variables that shadow another component.
Pending
#2 low Issue
Missing Events Arithmetic (events-maths)
Emit an event for critical parameter changes.
Pending
#3 low Issue
Missing Zero Address Validation (missing-zero-check)
Check that the address is not zero.
Pending
#4 low Issue
Floating Pragma
The current pragma Solidity directive is “^0.8.10". Contracts should be deployed with the same compiler version and flags that they have been tested thoroughly. Locking the pragma helps to ensure that contracts do not accidentally get deployed using other versions
Pending
#5 low Issue
Contract doesn’t import npm packages from source (like OpenZeppelin etc.)
We recommend importing all packages from npm directly without flattening the contract. Functions could be modified or can be susceptible to vulnerabilities
optimization Issues | 1 findings
Pending
#1 optimization Issue
State variables that could be declared constant (constable-states)
Add the `constant` attributes to state variables that never change.
informational Issues | 3 findings
Pending
#1 informational Issue
Functions that are not used (dead-code)
Remove unused functions.
Pending
#2 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
#3 informational Issue
Unused return values (unused-return)
Ensure that all the return values of the function calls are used.
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:
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.