> For the complete documentation index, see [llms.txt](https://docs.quaiscan.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.quaiscan.io/using-quaiscan/token-support.md).

# Token Support

Quaiscan supports the following token types:

* ERC-20: Fungible tokens
  * Standard for interchangeable tokens
  * Used for cryptocurrencies, stablecoins, utility tokens
* ERC-721: Non-fungible tokens (NFTs)
  * Unique, indivisible tokens
  * Often used for digital art, collectibles, game items
* ERC-1155: Multi-token standard
  * Combines fungible and non-fungible tokens
  * Efficient for gaming and complex ecosystems
* ERC-777: Advanced fungible tokens (basic indexing but no additional views, provides similar info to ERC-20)
  * Adds features like operator support and hooks
  * Backward compatible with ERC-20.
* ERC-4626: Tokenized Vaults (basic indexing but no additional views, provides similar info to ERC-20)
  * Standard for yield-bearing tokens
  * Used in DeFi for lending and yield farming


---

# 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 dynamically by asking a question.

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

```
GET https://docs.quaiscan.io/using-quaiscan/token-support.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.