> For the complete documentation index, see [llms.txt](https://cheomayield.gitbook.io/cheomayield-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://cheomayield.gitbook.io/cheomayield-docs/partner-vaults.md).

# Partner Vaults — Bond Model

CheomaYield's growth model is **partnership vaults**: a partner community locks up its own token as a bond to access CheomaYield's fixed APY. The partner token bond is that community's own commitment — it does not give depositors ownership of CheomaYield's sukuk book, and depositors' yield is backed by the protocol's own holdings and listed activities.

## How the bond gate works

1. A partner community (e.g. GIWA Markets) has a native token.
2. CheomaYield deploys a `PartnerPreDeposit` vault configured for that token.
3. To deposit, a user must **hold ≥ `minGateUsd`** worth of the partner token — this amount is **escrowed** into the vault (the "bond").
4. The bond stays locked alongside the user's USDC until **full withdrawal**, then is returned in-kind.
5. Partner-token price is read from a 30-minute Uniswap V3 TWAP (two-leg route).

This creates a mutually beneficial loop: the partner community gets access to high APY, and the partner token gets a utility-driven demand sink.

## First partner — GIWA Markets — **legacy, deposits closed**

* **Partner token**: GIWA `0xdaB0E8CE3b999D16898709A6DfC44c953bFc43b1`
* **Chain**: Robinhood Chain (chainId 4663)
* **Vault**: `0xd487e29c9f628395252707f72b220eB9D9afECBB`
* **APR**: 56.3% · **Cap**: $50,000 · **Bond**: $100 GIWA
* **Deposit asset**: USDG (Global Dollar / Paxos)
* **Status**: legacy — deposits closed (superseded first deploy `0xADaacBFDA2Ab1744b804F241e81533187a0Da843`, 52%, is also closed)

## Repeating the model

Each new partner is a fresh `PartnerPreDeposit` deploy with its own token, TWAP pools, gate amount, cap, and APR. The contract is reusable and chain-agnostic.


---

# 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://cheomayield.gitbook.io/cheomayield-docs/partner-vaults.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.
