> For the complete documentation index, see [llms.txt](https://docs.onre.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.onre.finance/for-capital-providers/minting-onyc.md).

# Minting ONyc

Minting ONyc converts your capital (USDC or USDG) into OnRe's yield-bearing collateral asset. The process differs depending on whether you mint through Open Access or Institutional Access, but the underlying mechanism is the same.

### How Minting Works

Minting ONyc is non-custodial, transparent, and designed for seamless integration across Solana DeFi.

* **Capital Enters OnRe**\
  Users deposit eligible stablecoins into the minting contract (USDC or USDG).
* **Capital is Allocated to Reinsurance Exposures**\
  OnRe deploys the backing collateral into regulated reinsurance programs.
* **Yield is Generated**\
  Reinsurance premiums and performance generate steady, uncorrelated yield.
* **ONyc Supply Grows**\
  Yield is reflected through ONyc's daily auto-compounding mechanism.
* **ONyc Becomes Fully Composable**\
  Holders can use ONyc as collateral, LP on partner venues, trade ONyc, redeem it back into stablecoins.

### Supported Assets

ONyc currently mints against USDC and USDG. Additional assets may be added over time as OnRe expands its collateral base.

### Fees

Minting ONyc carries no mint fee. Users pay network fees on Solana.


---

# 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.onre.finance/for-capital-providers/minting-onyc.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.
