# Token Risk Classification

Token Risk Classification(TRC) aims at identifying and cataloging scams like honeypots, and intentional backdoors that may be present in token smart contracts within the web3 ecosystem. This classification serves as:

* **A Shield against Malicious Smart Contracts:** By showcasing a defined list of malicious token contract patterns, it empowers users and project teams to recognize and steer clear of contracts with hidden intents, thereby ensuring safer interactions within the decentralized space.
* **A Testing Ground for Developers:** With a clear classification of malicious patterns and real-world examples, developers creating tools to detect these malicious token smart contracts can effectively evaluate their systems against a standardized classification.
* **A Catalyst for Research:** By clarifying the deceitful practices adopted in token smart contracts, we hope to drive more research towards crypto user safety, encouraging the community to devise strategies that deter such behaviors.
* **An Educational Asset:** This Github repository stands as an initiative to amplify awareness, serving as an informational storage hub, shedding light on potential contract pitfalls and deceitful patterns to the advantage of the community.

For more details, please visit our [TRC website](https://cryptousersecurity.github.io/token-risk-classification/).

### Contribute <a href="#contribute" id="contribute"></a>

Maintaining the relevance and comprehensiveness of this Github repository is a joint endeavor. We hope for and welcome community contributions. For details on how to contribute, kindly refer to our [Contribution Guidelines](https://github.com/cryptousersecurity/token-risk-classification).

<br>


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://whitepaper.gopluslabs.io/goplus-network/user-security-network/security-data-layer/token-risk-classification.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.