> For the complete documentation index, see [llms.txt](https://whitepaper.silencio.network/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://whitepaper.silencio.network/disclaimer/token-features.md).

# Token Features

The native digital cryptographically-secured cryptocurrency of the Silencio Platform ($SLC Token) is a transferable representation of attributed functions specified in the protocol/code of the Silencio Platform, designed to play a major role in the functioning of the ecosystem on the Silencio Platform, and intended to be used solely as the primary utility and future governance token on the platform. The goal of introducing $SLC Token is to provide a convenient and secure mode of payment and settlement between participants who interact within the ecosystem on the Silencio Platform, and it is not, and not intended to be, a medium of exchange accepted by the public (or a section of the public) as payment for goods or services or for the discharge of debt; nor is it designed or intended to be used by any person as payment for any goods or services whatsoever that are not exclusively provided by the issue. $SLC Token may only be utilized on the Silencio Platform, and ownership of $SLC Token carries no rights, express or implied, other than the right to use $SLC Token as a means to enable usage of and interaction within the Silencio Platform.


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

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

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://whitepaper.silencio.network/disclaimer/token-features.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

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.