IX-CORE at a glance
IX-CORE is currently backed ~100% by the compute sleeve, shown as a live weight — not described as “diversified.” New sectors enter the index by a published, rules-based weight as cohort vaults are onboarded.
Share price, exactly
Price is not set by anyone — it is computed from two on-chain terms:How ownership is issued
You mint IX-CORE by depositing into the vault; shares are issued at the current NAV-per-share. Redeeming burns your shares and returns value at NAV.1
You deposit
Approve, then
deposit(assets, receiver) USDC into the IX-CORE vault.2
Shares are minted at NAV
The vault mints IX-CORE to you at the current NAV-per-share — your slice of the whole book.
3
Your holding is your on-chain balance
balanceOf is the record of what you own; its value is shares × NAV-per-share.Fees
IX-CORE follows OpenZeppelin’s ERC-4626 fees pattern, so apreview* call always equals the actual result — no hidden slippage. Full schedule and redemption terms: Fees & terms.
The streaming management fee accrues on every deposit, redeem, and param change (and can be poked with
pokeFees()), so it dilutes at a smooth, predictable rate rather than in lumps. All four parameters are admin-settable and capped at 100%.
Worked example — depositing 1,000 USDC
Worked example — depositing 1,000 USDC
Suppose NAV-per-share is
1.05 and the entry fee is 0%.- You deposit
1,000USDC. - Entry fee
0%→ the full1,000is priced in. - Shares minted
= 1,000 ÷ 1.05 ≈ 952.38IX-CORE. - As revenue accrues, NAV-per-share rises; your
952.38shares are worth more USDC on redeem — you never claim a separate payout.
0.10% exit fee, redeeming those shares later returns NAV minus 0.10%.What IX-CORE entitles you to
- A pro-rata claim on the index’s NAV — the underlying compute assets plus revenue accrued into the vault. See Revenue & distributions.
- A verifiable position reflected in live NAV, reserve coverage, and the on-chain asset registry. See Transparency & NAV.
- Redemption at NAV — burn shares to withdraw, paid instantly when cash allows or via a FIFO queue drained from the smoothing reserve.
Redeeming: instant or queued
Because a liquid token sits on top of illiquid hardware, redemptions are paid instantly only up toavailableCash (vault balance minus the reserve floor). Larger exits burn now and queue — the request is paid FIFO by a keeper (processQueue) or pulled by you (claim) once the vault balance plus smoothing reserve can cover it. This is what stops a liquid share token from bank-running the hardware behind it.
Supply & bootstrap
IX-CORE supply is dynamic: shares are minted on deposit and burned on redemption, ERC-4626 style. There is no fixed cap and no pre-mine. The initial supply that represents existing hardware is minted once — either by the adminseedShares bootstrap or by the migration Merkle claim — which also prevents a “zero-share trap” where hardware value exists but no shares do.