> For the complete documentation index, see [llms.txt](https://docs.openetf.xyz/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openetf.xyz/how-it-works/hypercore-hyperevm.md).

# HyperCore × HyperEVM

**HyperCore is where the portfolio trades and HyperEVM is where ownership lives. OpenETF makes them one fund: the Vault contract is both the fund's treasury on HyperEVM and its trading account on HyperCore.**

## Two layers, one fund

On HyperCore, the Vault contract's address is the fund's trading identity. Balances, orders, positions and collateral belong to that account, not to the Manager's personal wallet. On HyperEVM, the same contract issues shares, records subscriptions and redemptions, and pays holders.

| Layer         | What it does for the fund                                                                                                               |
| ------------- | --------------------------------------------------------------------------------------------------------------------------------------- |
| **HyperEVM**  | The Vault contract issues and burns shares, prices subscriptions and redemptions, accrues fees, records payment rights and pays holders |
| **HyperCore** | The same Vault's account holds spot balances, perpetual positions, orders and collateral                                                |

Two things tie the layers together. [Managed Execution](https://docs.openetf.xyz/how-it-works/risk-controls/managed-execution.md) checks, signs and submits the Manager's trades on HyperCore. Fund accounting brings every balance, position, in-transit transfer and liability on both layers into one NAV.

## Why the Manager cannot withdraw

Three separate limits keep the Manager away from the fund's money:

* **No key.** The Manager directs trades through OpenETF and never receives the fund's Hyperliquid agent key. OpenETF generates that key inside its signing infrastructure and uses it only through Managed Execution.
* **HyperEVM.** The Vault contract owns the fund's assets. It pays out only what recorded rights and disclosed fees require, to the addresses entitled to them. It has no function that lets a Manager withdraw fund assets.
* **HyperCore.** Hyperliquid documents that an agent key can place and cancel orders for an account and move funds between that account's own balances. In OpenETF's testnet tests, an agent key could not send or withdraw the account's funds to another owner, but it could deposit the account's perpetual margin into a Hyperliquid Legacy Vault. Managed Execution permits only implemented trading actions and defined movements between the fund's own balances, and rejects everything else, including Hyperliquid Legacy Vault deposits.

The first and last limits depend on OpenETF's execution service, which holds the key and refuses every action outside the fund's rules; the Vault contract supplies the second.

None of these limits prevents losses through trading. The Manager, or anyone who gains trading authority, can harm the fund by trading, including against another account in a thin market ([Risks](https://docs.openetf.xyz/risks-and-security/risks.md)).

The Manager is paid like everyone else: disclosed fees, and redemptions of their own shares under the same rules as any holder, within the commitment ratio. Hyperliquid Legacy Vaults work the same way at the protocol level: a leader trades the vault but can withdraw only their own share.

What the structure does not decide is *how* the Manager trades: which markets, how much of the fund's cash, within which limits. [Managed Execution](https://docs.openetf.xyz/how-it-works/risk-controls/managed-execution.md) enforces those fund rules.

An OpenETF Vault is the fund's own container. It is not a deposit into a Hyperliquid Legacy Vault, and its shares follow OpenETF's fund model. [How OpenETF differs from Hyperliquid Legacy Vaults](https://docs.openetf.xyz/why/vs-hyperliquid-vaults.md).

## How money moves

![How money and rights move: a holder's wallet exchanges USDC and shares with the ETF Vault on HyperEVM; the same Vault trades on HyperCore, and the fund moves cash only between its own HyperEVM and HyperCore accounts.](https://2014689345-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FDRVctdoUAkrx2SF3VR1s%2Fuploads%2Fgit-blob-9b05305e13369b77f092eff938b1a9f4c96925b9%2Fmoney-flow.svg?alt=media)

A holder's USDC follows one path in and one path out:

1. **Subscribe.** USDC goes to the ETF's Vault on HyperEVM, which mints shares to the investor's wallet in the same transaction.
2. **Trade.** The fund moves capital to its own HyperCore accounts, where the Manager builds positions in spot, perpetual and admitted HIP-3 markets.
3. **Redeem.** When a holder redeems, the fund raises cash, returns it to the Vault on HyperEVM and pays the holder's wallet.

Each step is a separate onchain event that completes on its own timing. A trade on HyperCore, a transfer back to HyperEVM and a payment to a wallet are three distinct facts, and the fund records each one as it actually happens. While a transfer is in flight, it counts once, following Hyperliquid's documented transfer timing. If a transfer does not arrive as documented, the fund stops pricing new subscriptions and redemptions until the records reconcile. [Pauses and surviving rights](https://docs.openetf.xyz/risks-and-security/interruptions.md).

Throughout, the capital stays with the same fund and the same beneficiaries. Moving between layers never creates a new fund or a new owner.

## One NAV from onchain data

The fund's NAV brings every permitted asset domain into one view: assets, accrued fees and liabilities. Cash already set aside for fixed payments sits outside the share pool.

The NAV used to price a subscription or redemption comes from onchain reads inside that same transaction, together with the contract's ledger. Offchain observations can trigger a pause or a disclosure, but they never become pricing inputs. [NAV](https://docs.openetf.xyz/how-it-works/nav.md).

A fund can have a healthy NAV while much of its capital backs open positions. That is why a redemption is a process, described below, rather than an instant cash-out.

## A wider strategy canvas

Spot holdings, perpetual positions and admitted HIP-3 markets give a strategy different ways to express a view. The expansion direction adds **HIP-4 outcome contracts** and **HyperEVM DeFi**, such as lending and liquidity provision, held under one set of fund terms and one NAV; for an ETF with outside holders, adding them is a material expansion that comes through a new ETF ([Who controls what](https://docs.openetf.xyz/how-it-works/control.md#changing-a-funds-risk-scope)). Outward, each ETF's share token is something other applications can build on. [Roadmap](https://docs.openetf.xyz/roadmap.md).

## From shares back to cash

A redemption pays from cash the fund already has, and trims every position by the redeemed fraction so that, absent other flows, the holders who remain keep the fund's leverage and mix. At every point, a holder can tell what they own: shares whose value still moves, a fixed cash entitlement, or funds already delivered. [How redemptions are funded](https://docs.openetf.xyz/economics/redemption.md).
