Catalog listing connects an onchain SuperVault to Superform discovery. A vault can be created, indexed, and manager-visible without being listed to users.Documentation Index
Fetch the complete documentation index at: https://docs.superform.xyz/llms.txt
Use this file to discover all available pages before exploring further.
State model
| Layer | Meaning |
|---|---|
| Onchain vault | Contract exists on the deployment chain. |
| Managed vault | Erebor can read it and managers can operate it. |
| Catalog listing | Persephone/Superform catalog knows how to display and route users to it. |
| Available listing | The listing is both visible and available for user flows. |
Listing fields
| Field | Description |
|---|---|
provider_ids | Provider or institution IDs associated with the vault. |
category | Catalog category, commonly yield. |
visibility | Whether the vault is listed or hidden from discovery. |
availability | Whether the listed vault is available to users. Non-superadmins cannot set unavailable. |
external_url | Optional external detail page or provider URL. |
name / description | User-facing catalog copy. |
yield_source_ids | Optional catalog yield-source associations. |
visibility: listed and availability: available when the role allows it.
Unlisted SuperVaults
The Unlisted SuperVaults panel finds vaults you manage that are not in the catalog. Adding one pre-fills chain, address, provider IDs, category, visibility, availability, and external URL where known.Operational invariant
Do not treat deployment as launch. Launch requires:- Onchain creation and indexing.
- Upkeep-funded activation.
- Hook and merkle proof readiness.
- Yield sources and strategy setup.
- Catalog row set to listed and available.