> For the complete documentation index, see [llms.txt](https://docs.cryptodo.app/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.cryptodo.app/blockchains/avalanche.md).

# Avalanche

Avalanche is an open-source platform for launching decentralized applications and deploying public and private blockchains within a unified, scalable ecosystem. Avalanche consists of a primary network and an unlimited number of subnets. In turn, the primary network includes three blockchains:

* The Platform Chain (P-Chain) stores metadata, coordinates validators, and tracks subnets.
* The Contract Chain (C-Chain) enables the creation of Ethereum-compatible smart contracts.
* The Exchange Chain (X-Chain) provides tools for exchanging data between subnets, as well as creating interchangeable tokens and NFTs.

Avalanche subnets are similar to L2 solutions for Ethereum and parachains in Polkadot, but with fully isolated blockchain states. Any Avalanche user can create a subnet by paying a fee of 0.01 AVAX. All Avalanche nodes must verify transactions in the primary network, and optionally in other subnets.

Subnet creators can include various parameters, such as launching multiple blockchains and setting their own validator requirements, such as mandatory KYC/AML compliance.


---

# 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.cryptodo.app/blockchains/avalanche.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.
