> 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/choose-a-chype-path.md).

# Choose a CHYPE path

Choose the path that matches your role and immediate task. Start with a read-only check before any state-changing workflow.

### Institutions and trading firms

Start with [CHYPE overview](/chype/readme.md), then review transfer operations and the security model. Use the mint or redemption guides only if your organization runs the required Canton infrastructure and has approved access.

### Application developers

1. Review [CHYPE environments and prerequisites](/chype/get-started/environments-and-prerequisites.md).
2. Complete [CHYPE developer Quick Start](/chype/get-started/developer-quick-start.md).
3. [Install and validate CHYPE DARs](/chype/get-started/install-and-validate-dars.md).
4. Choose the [Transfer and receive CHYPE](/chype/guides/transfer-and-receive-chype.md), [Mint CHYPE](/chype/guides/mint-chype.md), or [Redeem CHYPE](/chype/guides/redeem-chype.md) integration.
5. Add [CHYPE authentication](/chype/get-started/authentication.md), reconciliation, and [CHYPE errors, retries, and troubleshooting](/chype/concepts-and-reference/errors-retries-and-troubleshooting.md).

### Canton operators

Start with [CHYPE compatibility and release notes](/chype/concepts-and-reference/compatibility-and-release-notes.md), [Install and validate CHYPE DARs](/chype/get-started/install-and-validate-dars.md), [CHYPE authentication](/chype/get-started/authentication.md), monitoring, and recovery. Confirm the participant and package state before enabling an application team.

### Security reviewers

Review [CHYPE architecture and trust boundaries](/chype/concepts-and-reference/architecture-and-trust-boundaries.md), [CHYPE Attestor Network](/chype/concepts-and-reference/attestor-network-and-hyperevm-signing.md), [CHYPE Proof of Reserve](/chype/concepts-and-reference/proof-of-reserve.md), [CHYPE authentication](/chype/get-started/authentication.md), [CHYPE security](/chype/concepts-and-reference/security.md), and [CHYPE compatibility and release notes](/chype/concepts-and-reference/compatibility-and-release-notes.md). Match every claim to a release and approved evidence source.

### Task map

| Goal                   | Start here                                                                 |
| ---------------------- | -------------------------------------------------------------------------- |
| Evaluate CHYPE         | [How CHYPE works](/chype/how-chype-works.md)                               |
| Connect an application | [CHYPE developer Quick Start](/chype/get-started/developer-quick-start.md) |
| Mint                   | [Mint CHYPE](/chype/guides/mint-chype.md)                                  |
| Redeem                 | [Redeem CHYPE](/chype/guides/redeem-chype.md)                              |
| Transfer               | [Transfer and receive CHYPE](/chype/guides/transfer-and-receive-chype.md)  |
| Review security        | [CHYPE security](/chype/concepts-and-reference/security.md)                |

### Next step

👉 **New to CHYPE development?** [CHYPE developer Quick Start](/chype/get-started/developer-quick-start.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/choose-a-chype-path.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.