The Grays Currency Info

TGXen aims to be a top contributor in the Xen burn by allowing the Xen community members to burn their Xen to earn a 1 to 1 allocation of TGXen and be eligible for the future XN airdrop. The Grays Ecosystem is designing TGXen as 1 to 1 allocation for the Xen community members that want to participate in the Xen burn and also be eligible for the XN airdrop while receiving another token as proof of participation in the Xen burn. When Xen community members burn Xen we want to make sure they are also receiving a token that follows the first principles of crypto. (decentralization, transparency, counterparty risk resistance, peer-to-peer value and self-custody)

The Grays Currency 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.

On-Chain Insights

Smart Contract Audit

Select the audit
Static Analysis Dynamic Analysis Symbolic Execution SWC Check Manual Review
Contract address
0x51B0...BF83
Network Ethereum - Mainnet
License N/A
Compiler N/A N/A
Type N/A
Language Solidity
Onboard date 2023/07/26
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.

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 and Exclude accounts from rewards

We strongly suggest using the non-reentrant modifier in all the external functions

Note - This Audit report consists of a security analysis of the TGXEN Token smart contract. This analysis did not include functional testing (or unit testing) of the contract’s logic. Moreover, in this audit, we only audited a token contract for the TheGraysEcosystem team, other contracts associated with the project that were audited by our team can be found at "https://github.com/solidproof/projects/tree/main/Grays%20Currency". We recommend investors to do their own research before investing.

Scope of Work

Files and details

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.

The auditing process follows a routine series of steps:
  1. Review the specifications, sources, and instructions provided to SolidProof to ensure we understand the smart contract's size, scope, and functionality.
  2. Manual review of code, which is the process of reading source code line-by-line in an attempt to identify potential vulnerabilities.
  3. Specification comparison checks whether the code does what the specifications, sources, and instructions provided to SolidProof describe.
  4. Test coverage analysis determines whether the test cases are actually covering the code and how much code is exercised when we run those test cases.
  5. Symbolic execution is analyzing a program to determine what inputs cause each part of a program to execute.
  6. Based on the established industry and academic practices, recommendations, and research, best practices review smart contracts to improve efficiency, effectiveness, clarity, maintainability, security, and control.
  7. Specific, itemized, actionable recommendations to help you take steps to secure your smart contracts.

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.

Findings and Audit result

informational Issues | 1 findings

Pending

#1 informational Issue
NatSpec documentation missing
TGXen.sol
-
Description

If you started to comment on your code, also comment on all other functions, variables etc.