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

# Overview

### CHYPE brings native HYPE into Canton workflows

CHYPE is a wrapped native HYPE token on Canton Network, built on BitSafe infrastructure and designed to represent HYPE at a 1:1 ratio. It gives institutions and application teams a path to hold, transfer, mint, redeem, and integrate HYPE-denominated value within Canton applications.

This page explains the product and routes readers to the right task. Setup, lifecycle details, contract interfaces, backing evidence, and security controls have their own pages.

### What you can do

* Hold and transfer CHYPE between authorized Canton parties using compatible applications.
* Mint CHYPE following an eligible native HYPE deposit to the HyperEVM bridge.
* Redeem CHYPE to a HyperEVM address that can receive native HYPE.
* Integrate supported CHYPE workflows through pinned libraries, APIs, and the bridge interface.
* Review bridge governance, privacy boundaries, backing evidence, and operational controls.

Direct minting and redemption require onboarding and the CHYPE Minter credential. A deployed bridge does not, by itself, establish general availability or provider support.

### Choose a path

| Goal                                      | Canonical page                                                                                                                                                 |
| ----------------------------------------- | -------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| Find a wallet, venue, or lending provider | [CHYPE Ecosystem](/chype/chype-ecosystem.md)                                                                                                                   |
| Understand the lifecycle                  | [How CHYPE works](/chype/how-chype-works.md)                                                                                                                   |
| Choose an operation                       | [Choose a CHYPE path](/chype/choose-a-chype-path.md)                                                                                                           |
| Build an integration                      | [Developer quick start](/chype/get-started/developer-quick-start.md)                                                                                           |
| Review architecture and controls          | [Architecture and trust boundaries](/chype/concepts-and-reference/architecture-and-trust-boundaries.md); [Security](/chype/concepts-and-reference/security.md) |
| Check versions and upgrade requirements   | [Compatibility and release notes](/chype/concepts-and-reference/compatibility-and-release-notes.md)                                                            |

### Product boundaries

CHYPE represents native HYPE. The current design does not stake reserve HYPE or automatically provide staking rewards.

HYPE is held by the HyperEVM bridge, while CHYPE holdings and transfers are recorded on Canton. A Canton transfer does not move HYPE on HyperEVM for each transfer. Canton's configurable sub-transaction privacy applies to entitled Canton contract data. HyperEVM deposits, bridge balances, and redemptions remain visible on HyperEVM.

CHYPE's design links issuance to eligible HYPE deposits and redemption to CHYPE burns. The evidence, accounting boundaries, pending-redemption treatment, and limitations belong in Proof of Reserve. HyperEVM redemption authorization and bridge administration are separate trust boundaries.

### Technical sources

* [BitSafe token library](https://github.com/DLC-link/bitsafe-token-lib)
* [Shared Canton library](https://github.com/DLC-link/canton-lib)
* [HyperEVM bridge](https://github.com/DLC-link/evm-asset-bridge)

### Next step

👉 **Understand the operating model:** [How CHYPE works](/chype/how-chype-works.md).


---

# 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.bitsafe.finance/chype/readme.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.