> For the complete documentation index, see [llms.txt](https://docs.wanchain.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.wanchain.org/cross-chain-infrastructure/wan-coin.md). # WAN coin The WAN coin is the native asset of the Wanchain L1 Blockchain. WAN coins enable several functions including regular transactions and smart contract interactions on the [Wanchain L1 Blockchain](broken://pages/ZiJoxkixshZnOyHGATRR). A small amount of WAN is burned alongside every transaction. WAN coin’s max supply is 210,000,000. WAN coins also have utility beyond the Wanchain L1 Blockchain. For instance: * WAN coins can be staked to deploy Wanchain PoS Validator Nodes * WAN coins can be [delegated](/products/xstake.md) to existing Wanchain PoS Validator Nodes * WAN coins can be staked to deploy Wanchain Bridge Nodes * WAN coins can be [delegated](/products/xstake.md) to existing Wanchain Bridge Nodes * WAN coins can be used to propose and vote on Community Treasury proposal \[in development] Additionally, holding or [staking](/products/xstake.md) WAN coins grants discounts on cross-chain transactions. Fees collected from all cross-chain transactions are also converted to WAN coins programatically via Wanchain's Convert n' Burn mechanism. A portion of these are burned. --- # 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://docs.wanchain.org/cross-chain-infrastructure/wan-coin.md?ask=&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.