Wallet Requirements
SuperVaults uses Dynamic.xyz for wallet connection and JWT issuance.
EVM-compatible wallet (MetaMask, Rabby, Frame, or any WalletConnect-compatible wallet)
Native gas token for each chain where you operate vaults
Operator access assigned on at least one vault before SuperformOS features are accessible
View-only users are added offchain and do not require a wallet connection. All write operations require at minimum a secondary manager role.
Supported Chains
Chain Chain ID Status Ethereum Mainnet 1 ✅ Live Base 8453 ✅ Live HyperEVM 999 ✅ Live Flare 14 ✅ Live
The SuperVault contract architecture supports additional chains. Contact the Superform team for expansion requests.
Environment URL Production os.superform.xyz
API Base URLs
Each backend service exposes its own base URL. Use these when building automation:
Service Base URL OpenAPI Spec Erebor (management API)https://erebor.superform.xyz✅ Available Strategy Engine https://strategy.superform.xyz✅ Available OMS (DeFiX intents)https://oms.superform.xyz✅ Available
Role Requirements by Page
Page Minimum Role Home Public (no auth) Dashboard Operator Strategy Operator Yield Sources Operator Merkle Trees Operator User Management Primary Manager Vault Settings Primary Manager Pause Operator Create Vault Operator (you become primary manager of the new vault) Alerts Operator
Getting Access
Joining an existing vault: The primary manager adds you via User Management as a secondary manager (onchain transaction) or view-only user (offchain).
Creating a new vault: Any wallet with operator access can create a vault and automatically becomes its primary manager.
Authentication JWT auth flow, token storage, and programmatic access.