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

# Mint sequence

A mint exchanges USDC for a share of the trading account. The token amount is fixed at settlement.

```mermaid
sequenceDiagram
    participant U as Holder
    participant T as Token
    participant S as Takes
    participant H as Hub and trading account
    U->>T: Approve USDC; submit signed mint quote
    T->>T: Hold USDC for accepted request
    S->>T: Execute request and deduct fees
    T->>H: Transfer USDC after mint fees
    H->>H: Confirm account credit
    H->>T: Return credit and pricing confirmation
    T->>T: Settle and issue request shares
    S->>T: Deliver original controller entitlement
    T->>U: Transfer tokens
```

Arc, Ethereum, Base, Arbitrum, and Monad transfers and confirmations pass through Circle CCTP. Ethereum, Base and Arbitrum deposits use Fast when available; Arc and Monad use Standard. Confirmations follow the configured authenticated route. HyperEVM uses local token/hub calls without a cross-chain transfer.

For an existing supply, settlement prices new tokens using equity before the deposit. Exactly the accepted net principal is deposited into Core. Bridge charges are funded from settlement fees and operating reserves; excess destination credit belongs to platform surplus. The contract also checks the executing request before settling.

You can cancel only while the mint request remains accepted. Once execution starts, there is no timeout refund.

Trading toward the basket runs separately. Credit confirmation does not prove every trade has filled.

See [Accounting model](/takes-docs/technical-design/accounting-model.md#accounting-model) and [Cross-chain security](/takes-docs/security-and-trust/cross-chain-security.md#cross-chain-security).


---

# 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://takes.gitbook.io/takes-docs/technical-design/mint-sequence.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.