Wallet Requirements
SuperformOS uses Dynamic.xyz for wallet/account sign-in. Follow Authentication to establish your browser session.- 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 access is assigned offchain; private vault and rule inspection still requires an authenticated account with access to that vault. Writes require the role authorized for that operation.
Supported Chains
The SuperVault contract architecture supports additional chains. Contact the Superform team for expansion requests.
SuperformOS
API Base URLs
These are upstream service base URLs. Browser operations use the session-mediated BFF; headless integrations require an approved endpoint, identity, and scope. See Authentication.Role Requirements by Page
Getting Access
Joining an existing vault: The Primary Manager assigns Secondary Managers through an onchain transaction. Either manager can add or remove view-only collaborators and update their display names offchain through User Management. Creating a new vault: Any wallet with operator access can create a vault and automatically becomes its primary manager.Authentication
Browser sign-in, public reads, and approved automation access.