Security and Risk Considerations

Liminal Cash is designed to make idle USDC productive while keeping user positions separated through dedicated Cash Accounts. However, it still depends on smart contracts, keeper execution, xLEND, and the underlying redemption infrastructure.

Integrators should understand the main security properties and risks before using it.

Per-User Account Isolation

Each depositor has their own Cash Account.

The account is deployed deterministically from the user address and the xLEND share token. This means a user’s xLEND shares are held in a dedicated smart-contract account rather than being merged into one application-wide treasury balance.

This is the main reason Liminal Cash can support a self-custodial account model. The productive position sits in a user-specific on-chain account, not in an opaque off-chain ledger or a pooled app wallet.

Non-Custodial Execution Model

The Liminal Cash keeper triggers approved actions, but it is not meant to custody redeemed USDC.

When a redemption is executed, the Cash Account receives the redeemed USDC and routes it through the configured HyperCore deposit flow. The keeper pays gas and coordinates execution, but the flow is designed so the keeper does not receive the user’s assets.

That said, the keeper is still an important operational component. Liminal Cash should be described as self-custodial through its account architecture, with keeper-based execution for redemptions.

Approved Assets and Redemption Pipes

The factory controls which share tokens and redemption pipes are approved.

A Cash Account cannot freely redeem through any contract. It checks with the factory before using a share token or redemption pipe. This reduces integration risk by narrowing the set of contracts that can interact with user positions.

The factory can approve or revoke:

• Supported share tokens such as xLEND

• Redemption pipes

• The keeper address

• USDC configuration

• CoreDepositWallet configuration

Pause Controls

The system includes pause controls.

If an issue is detected, authorized pausable admins can pause the factory. When paused, Cash Account redemption actions are blocked. This gives Liminal and integrators an emergency response mechanism in case of unexpected behavior, integration issues, or external risk.

Smart Contract Risk

Liminal Cash relies on smart contracts for account deployment, share custody, redemption requests, and USDC routing.

As with any on-chain system, there is smart contract risk. Bugs in the Cash Account, factory, redemption pipes, xLEND contracts, token contracts, or external dependencies could affect user funds or delay withdrawals.

Audits, testing, limited approvals, and monitoring reduce this risk, but they do not eliminate it completely.

xLEND Risk

Liminal Cash uses xLEND as its underlying yield source.

This means Liminal Cash inherits the risks of xLEND, including strategy risk, smart contract risk, liquidity risk, oracle/accounting risk, and any risks connected to the underlying lending markets or assets used by xLEND.

Liminal Cash does not guarantee yield. The productive balance depends on xLEND’s performance and redemption conditions.

Redemption Liquidity Risk

Redemptions depend on available liquidity and the behavior of the underlying xLEND redemption process.

Instant redemption may only be available when sufficient liquidity exists. Standard redemption may require waiting for the underlying position to unwind or settle. During periods of market stress, high withdrawal demand, or infrastructure issues, redemptions may take longer than expected.

Integrators should make this clear in their user interface.

HyperCore and External Infrastructure Risk

Liminal Cash can route redeemed USDC to HyperCore through the configured CoreDepositWallet flow.

This introduces dependency on external infrastructure, including HyperEVM, HyperCore, USDC contracts, Circle-related deposit infrastructure, and any chain-level systems involved in the route.

If one of these systems is delayed, paused, congested, or unavailable, users may experience delayed access to redeemed USDC.

Admin and Configuration Risk

The factory has privileged roles for configuration.

Admins can update key system parameters such as approved tokens, approved redemption pipes and keeper address. These controls are necessary for maintaining and securing the system.