> For the complete documentation index, see [llms.txt](https://docs.chiliz.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.chiliz.com/learn/glossary/wrapped-chz-wchz.md).

# Wrapped CHZ (wCHZ)

Wrapped CHZ (wCHZ) explained: ERC-20/CAP-20 tokenized version of native CHZ, peg mechanics, use in DeFi and bridging, and how to wrap/unwrap on Chiliz Bridge.

{% hint style="info" %}
**In short**\
Wrapped Chiliz (wCHZ) is a tokenized version of the Chiliz cryptocurrency, designed to work like regular ERC-20 tokens while keeping its original value. This makes it more versatile and useful for developers, similar to other wrapped tokens like wETH or Wrapped BNB.
{% endhint %}

## What Is Wrapped Chiliz (wCHZ)? <a href="#header-0" id="header-0"></a>

wCHZ is the wrapped version of Chiliz.

Wrapped tokens, such as wCHZ and wETH, are tokenized versions of cryptocurrencies that are pegged to the value of the original coin and can be unwrapped at any point. Almost every major blockchain has a wrapped version of its native cryptocurrency like Wrapped BNB, Wrapped AVAX, or Wrapped Fantom.

The benefits of this is that developers are able to use an ERC-20 (or CAP-20) version of the native token CHZ, giving the token the benefits that other ERC20 tokens posses and removes the limitations of a native token, while retaining the same price value as the original CHZ.

## How do I get wrapped Chiliz (wCHZ)?

Read it all here:

{% content-ref url="/pages/asZ8uyn2pYREdfp9o1AP" %}
[Use Wrapped CHZ](/develop/basics/use-wrapped-chz.md)
{% endcontent-ref %}


---

# 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.chiliz.com/learn/glossary/wrapped-chz-wchz.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.