Skip to main content
The Setup page turns a newly-created SuperVault into an operational and discoverable vault. Use it after Create Vault and after any major configuration reset. SuperformOS Setup Checklist - post-create readiness rows Use this page to move from created to available: fund upkeep, add yield sources, configure hooks, create strategies, and confirm Superform availability. If no vault is selected, the page asks the operator to select one from the Operate sidebar. The checklist is vault-scoped: every row is calculated from the selected chain and vault address.

Checklist rows

Statuses are complete, in_progress, needs_setup, or blocked.

Activation gate

Upkeep funding or an applicable exemption satisfies the activation gate. Fund upkeep from Vault Settings → Upkeep and read back activation. The activation route can deep-link with panel=upkeep&activateVault=1 so the primary manager lands on the funding action. Current Erebor-facing activation fields used by the UI include: Use the returned required_balance, shortfall, and effective activation for the selected vault rather than a fixed chain-wide funding assumption.

Distribution Evidence

The live-on-Superform row compares the managed vault against distribution data. Evidence includes visibility and availability, for example listed and available. If no matching distribution entry exists, the vault is onchain and manager-visible but not available in Superform allocator-facing surfaces.

Troubleshooting

Green setup rows summarize configuration, not executable readiness. Before starting, check separately:
  • Funding: UP upkeep pays for automation; native tokens pay execution gas; strategy assets fund the action. One balance does not fund the others.
  • Authority: Browser login is not an execution-session grant. Verify the manager role and session-key readiness.
  • Authorization: Every plan step needs an authorized hook and matching proofs against the active onchain root.
  • Data and controls: Required inputs must be present and fresh, with sufficient action liquidity and no blocking pause, lock, cooldown, or concurrency gate.

Operator rule

Route deposits only after the checklist is complete and the separate execution-readiness checks pass.