> For the complete documentation index, see [llms.txt](https://doc.auditx.net/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://doc.auditx.net/auditx-ecosystem/multi-chain-contract-scan/supported-contract-types.md).

# Supported Contract Types

* **Types of Contracts It can Scan**:
  * **ERC-20 Tokens**: Standard fungible tokens commonly used in DeFi and other applications.
  * **ERC-721 Tokens**: Non-fungible tokens (NFTs), used for digital art, collectibles, and unique assets.
  * **ERC-1155 Tokens**: Multi-purpose tokens that can be fungible or non-fungible, popular in gaming and asset management.
  * **Other Standards**: The tool also supports blockchain-specific standards, like BEP-20 on Binance Smart Chain and SPL on Solana, making it adaptable for projects on multiple chains.
* **Flexibility**: It’s built to handle not only standard tokens but also more complex contract structures like multi-signature wallets and upgradeable contracts, ensuring comprehensive coverage for different project needs.


---

# 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://doc.auditx.net/auditx-ecosystem/multi-chain-contract-scan/supported-contract-types.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.