Tazz coin Info

Tazz Coin is born out of the idea that memes have the power to transcend boundaries and bring people together. As the world increasingly embraces digital currencies, we believe it's time to infuse the crypto space with the infectious joy and humor found in meme culture. Tazz Coin is not just a cryptocurrency; it's a movement that celebrates laughter, creativity, and community.

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

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

Security Assessments

Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x67FE...51e3
Network
BNB Smart Chain - Mainnet
License N/A
Compiler N/A
Type N/A
Language Solidity
Onboard date 2023/11/09
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 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:

  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 exclude/include wallets in rewards.
  • The owner can claim stuck tokens.
  • The owner can enable trading only once.
  • The owner can set the minimum swap amount of not less than 0.001% of the total supply.
  • The owner can enable/disable swapping.
  • The owner can exclude wallets from fees.
  • The owner can update the marketing wallet address.
  • The owner can update the total buy and sell fees of not more than 10%. 
  • The owner can enable/disable wallet-to-wallet transfers without any fees.

Note - This Audit report consists of a security analysis of the Tazz coin 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 Tazz coin team. Other contracts associated with the project were not audited by our team. We recommend investors 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 | 2 findings

Pending

#1 low Issue
Local variables shadowing (shadowing-local)
Tazz.sol
L467
L666
Description

Rename the local variables that shadow another component.

Pending

#2 low Issue
Missing events arithmetic.
Tazz.sol
L674-677
Description

Emit all the critical parameter changes.

optimization Issues | 2 findings

Pending

#1 optimization Issue
State variables that could be declared constant (constable-states)
Tazz.sol
L339
L337
L338
Description

Add the `constant` attributes to state variables that never change.

Pending

#2 optimization Issue
Public function that could be declared external (external-function)
Tazz.sol
L36-39
L41-45
L441-443
L445-447
L449-451
L462-465
L467-469
L471-474
L476-480
L482-485
L487-490
L492-494
L496-498
L500-507
L509-518
L526-533
L662-664
Description

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

informational Issues | 3 findings

Pending

#1 informational Issue
Costly operations in a loop (costly-loop)
Tazz.sol
L535-546
Description

Use a local variable to hold the loop computation result.

Pending

#2 informational Issue
Functions that are not used (dead-code)
Tazz.sol
L101-122
L84-86
L88-90
L92-94
L96-99
L65-74
L10-13
Description

Remove unused functions.

Pending

#3 informational Issue
Unused state variables (unused-state)
Tazz.sol
L366
Description

Remove unused state variables.