> For the complete documentation index, see [llms.txt](https://docs.liminal.money/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.liminal.money/liminal-cash/minting-and-bridging.md).

# Minting and Bridging

In Liminal Cash, “minting” does not mean minting a new stablecoin.

It refers to the process of using deposited USDC to enter the underlying xLEND position and receive xLEND shares. Those shares are then associated with the user’s Cash Account.

The user-facing experience can be simple, but the technical flow has two sides:

* Minting xLEND shares when idle USDC is made productive
* Redeeming and routing USDC back when the user or application needs liquidity

### Minting Flow

When a user deposits USDC into an integrated application, the application can decide to route that USDC into xLEND.

A typical flow looks like this:

1. The user deposits USDC into the application.
2. The application identifies the user’s Cash Account for xLEND.
3. If the Cash Account does not exist yet, it can be deployed deterministically.
4. The USDC is supplied into the xLEND minting flow.
5. xLEND shares are received and held by the user’s Cash Account.
6. The application can display the user’s productive USDC balance in its own interface.

The important point is that the user’s position is not represented by a new Liminal Cash token. It is represented by xLEND shares held in that user’s dedicated Cash Account.

### Redeeming Flow

When USDC is needed again, the xLEND position can be redeemed.

Liminal Cash supports redemption flows through approved redemption pipes. These pipes are controlled at the factory level, which means Cash Accounts cannot redeem through arbitrary contracts.

There are two main redemption patterns:

* Instant redemption
* Standard redemption

### Instant Redemption

Instant redemption is used when liquidity is available immediately.

In this flow, the Cash Account redeems xLEND shares through an approved redemption pipe. The redeemed asset is USDC. Once the USDC is received, the Cash Account routes it toward the configured HyperCore recipient through the CoreDepositWallet flow.

This is useful when the application needs to quickly make the user’s USDC available again.

### Standard Redemption

Standard redemption is used when the position needs to be unwound through a queued or delayed process.

In this flow, the Cash Account submits a redemption request. The account records the pending redemption state, including the redemption pipe, the recipient, and the USDC balance at the time of the request.

Once the redemption is fulfilled and USDC has arrived back in the Cash Account, the keeper can sweep the fulfilled USDC to the intended HyperCore recipient.

This prevents overlapping pending redemptions for the same Cash Account and gives the system a clearer accounting model for delayed withdrawals.

### Bridging and HyperCore Routing

For Liminal Cash, bridging does not mean bridging a transferable Liminal Cash token across chains.

The main bridge-like action is the routing of redeemed USDC between HyperEVM and HyperCore. After redemption, USDC can be deposited into HyperCore using Circle’s CoreDepositWallet integration.

The Cash Account approves the CoreDepositWallet only for the exact USDC amount being routed, calls the deposit flow, and then resets the approval. This keeps the routing narrow and avoids leaving open-ended token approvals.

From the user or integrator perspective, the result is that productive USDC can be returned to the user’s HyperCore destination when needed.