How the vault is composed, priced, and secured — fees, mechanics, and risk.
SuiX5 is a passive index vault on Sui. Deposit USDC, receive SUIX5 — a token representing your proportional share of a basket holding the top five Sui ecosystem tokens by market cap, capped at 40% each. The vault rebalances on a schedule and NAV is computed on-chain from Supra prices, read and validated directly by the vault — no separate price-cache adapter in between.
SuiX5 is pure infrastructure — no yield promises, no governance token, no hidden mechanism. You own your proportional share of what the vault actually holds, priced by an oracle the vault itself validates.
Every SUIX5 token is backed by real tokens held in the vault’s smart contract. The vault’s TreasuryCap is consumed at creation — no address holds it, so SUIX5 can only be minted or burned by the contract’s own deposit/withdraw logic, not by an admin key.
These figures are the vault’s live on-chain config — read directly off the vault object, not a static page.
The vault holds exactly five constituents, selected and weighted by market cap, native to Sui, excluding stablecoins and wrappers, with a minimum 24h volume and a live Supra feed. No single constituent’s weight can exceed 40% of the basket — enforced on-chain by the composition module, not by a backend policy.
A keeper cranks the vault once its rebalance interval has elapsed, correcting any constituent whose weight has drifted more than 3.0% of the total portfolio from its target — an absolute band, not one sized to each constituent’s own weight. Every rebalance trade is bounded by an oracle-derived minimum output; a bad fill reverts rather than executing.
If a constituent drops out of the top five, a replacement is proposed on-chain and takes effect after a 24-hour timelock — visible to every holder before it executes, so anyone who disagrees with the change can exit first. The vault’s transparency panel on the Vaults page shows any pending change.
Move has no dynamic dispatch, so a vault that imported a DEX package would be stuck with it forever. Instead the vault hands out an asset plus an obligation — a SwapReceipt with no abilities — and the swap happens inside the same transaction, routed through Cetus’s aggregator. The receipt cannot be discarded; the transaction cannot end until the swap settles at or above the oracle-derived minimum. Switching aggregators is a client-side change with no contract impact.
Deposit and withdrawal fees are both zero at launch — set on-chain, admin-adjustable within a hard 10% cap, read live from the vault rather than hardcoded here.
Charged on the USDC value deposited, before it’s split across the five swap legs.
Charged on the USDC value paid out after your pro-rata share is sold down.
No Management or Performance Fees
No fee for holding, no cut of gains. The real cost of using the vault isn’t a fee line — it’s the round-trip swap cost of five legs in and five out through the aggregator, which the deposit and withdraw previews estimate before you sign.
Every deposit and withdrawal is a single transaction you sign yourself — there is no backend in that path at all. Your assets never sit with an intermediary between your wallet and the vault’s on-chain custody.
The admin key cannot mint SUIX5 or move your assets out.
Admin capabilities are limited to pausing the protocol, proposing composition or oracle price-feed changes (both timelocked), and an emergency exit path that itself requires the protocol to already be paused.
Prices come directly from Supra's on-chain OracleHolder — the vault reads it and validates every commit itself: staleness and a circuit breaker that halts a token's pricing if a committed price moves more than50% from its last accepted value. A tripped breaker blocks deposits and rebalances for that token — both need a live price — but not withdrawals, which are pro-rata against custody and never read a price at all.
Verifiable on SuiScan. The Registry and Gate are permanent for the life of this deployment; the executing core and oracle packages are resolved live off the Gate before every transaction, never hardcoded — see the Vaults page for the same live values.
Smart contract audits are in progress. Reports will be published here once complete.
SuiX5 is experimental beta software. Use at your own risk.
Potential risks include:
Always do your own research and never deposit more than you can afford to lose.
A keeper cranks the vault once its rebalance interval has elapsed, and only trades constituents that have drifted past the tolerance band. See the Vaults page for the vault’s live schedule and last-rebalance timestamp.
The current composition, weights, and drift against target are shown live on the Vaults page, read directly from the vault object — not from this page or any static config.
Yes. Token prices can decline, swaps incur real slippage, and a withdrawal can fail outright if its swap can’t clear the on-chain minimum. The vault tracks the top five Sui tokens by market cap — it does not guarantee a profit.
NAV is computed on-chain from Supra prices and used to size how much SUIX5 a deposit mints. Withdrawals work differently: you get back your exact pro-rata share of what the vault actually holds — no oracle in that split. The two can differ slightly around a swap’s real execution price, which is exactly what the deposit/withdraw cost preview is meant to surface before you sign.
There’s no hard on-chain minimum, but a deposit splits into five separate swaps — gas and swap costs make very small deposits impractical. The deposit preview shows the estimated cost before you sign.
Smart contract audits are in progress. Reports will be published here once complete.
An admin key can pause the protocol and propose timelocked changes to composition or oracle price feeds, plus an emergency exit path that itself requires the protocol to already be paused. It cannot mint SUIX5 or move assets out directly — the TreasuryCap was consumed at genesis.
A dropped constituent’s replacement takes effect after a timelock, but the old token stays in custody — priced and included in every NAV read — until the next rebalance actually sells it. Nothing is ever silently written off.
Pricing for that token halts, which blocks deposits and rebalances that touch it until an admin manually resets it. Withdrawals are unaffected — they're pro-rata against what the vault holds and never read a price at all. This is deliberate: a single stale or manipulated print should never be able to mint against a bad NAV, but it also shouldn't be able to trap your ability to exit.