Skip to main content
This guide follows the operator path from vault deployment to a live Superform listing. Use it for sequence; use Setup Checklist as the canonical readiness source after the vault exists. Prerequisites: operator access, connected EVM wallet, gas on the deployment chain, provider profile, and the token/yield-source details for the vault.
1

Create the vault

Open Create Vault (/vaults/create). The editable wizard has four steps:
  1. Basic Information — select chain, provider, underlying asset, listing metadata, and the computed onchain name/symbol.
  2. Managers — assign the primary manager and optional secondary managers.
  3. Fees — configure fee recipient, performance fee, management fee, PPS timing, and redemption timing.
  4. Review — inspect the full configuration before the transaction phase.
After review, the modal moves through transaction signing, indexing, optional yield-source setup, and completion. See Create Vault.
2

Work through the setup checklist

Open Setup. Treat it as the canonical go-live checklist. It coordinates the required rows for creation, upkeep, hook authorization, yield sources, strategy coverage, and Superform availability.Use Setup Checklist for configuration progress and its separate execution-readiness checks; green rows alone do not establish readiness.
3

Fund upkeep and activate automation

Open Vault Settings → Upkeep. Read the required balance, shortfall, and activation status. Erebor marks the vault active and discoverable when the funding threshold is satisfied or an exemption applies.For a non-exempt vault, fund the returned shortfall and read back activation. Direct-link visibility alone does not establish activation.
4

Whitelist yield sources

Open Yield Sources. Add each target yield source with its paired oracle. Bulk add, bulk remove, and bulk oracle update flows prepare a single transaction for multiple rows.Emergency-exit readiness is tied to the whitelist: each whitelisted yield source can have a paired EMERGENCY_EXIT strategy used by the Pause page to drain that source during an incident.
5

Configure hook authorization

Open Merkle Trees and follow the manager-root flow:
  1. Draft a root config.
  2. Activate the config.
  3. Generate the merkle tree.
  4. Have the Primary Manager propose the root onchain.
  5. After the configured timelock, execute the root update onchain.
  6. Publish the proof artifact and verify its root against the onchain root.
Keepers and OMS intents need active merkle proofs for each hook/parameter combination they execute.
6

Create and order strategies

Open Strategy Canvas. Create user-defined strategies for deposits, withdrawals, and rebalances. Strategy priority is server-managed: use drag-to-reorder, which persists through POST /api/v1/strategies/reorder. Create and update requests do not carry priority.Before a strategy can publish intents, the OMS session key must be ready and the active merkle tree must contain the required withdrawal/deposit hooks.
7

Confirm distribution readiness

Open Distribute. Confirm the vault has the metadata, visibility, and availability needed for Superform surfaces.Onchain created means the vault contract exists. Available in Superform means the vault is indexed, activated, configured, and visible to allocator-facing surfaces. See Distribute.
8

Monitor intents and operations

Use Dashboard for vault health, Intent History for execution traces, and Pause for incident controls. Intent History maps Strategy Engine rows to OMS events, fills, gas usage, mined timestamps, and hook transaction details.

​
Source of Truth

After creation, Setup Checklist is the source of truth for go-live readiness. This quickstart intentionally avoids duplicating its row logic. Use the other pages for the work behind each row: