Skip to main content
Terms specific to SuperVaults (v2). For legacy SuperAssets (v1) terms, see the v1 documentation.
  • EIP-7702 — Ethereum standard allowing EOAs to act as smart accounts, enabling existing wallets to use account-abstraction features without migration.
  • ERC-4337 — Account-abstraction standard that lets smart-contract wallets function like EOAs via a UserOperation mempool and bundler system.
  • ERC-4626 — Tokenized vault standard defining a common deposit/withdraw interface. SuperVaults implement this for synchronous deposits.
  • ERC-7540 — Async vault extension to ERC-4626. Defines requestRedeem / requestDeposit flows for cross-chain or illiquid positions. SuperVaults use ERC-7540 for redemptions.
  • ERC-7579 — Modular smart-account standard enabling plug-and-play functionality through a standardized module interface. SuperExecutor and SuperValidator are ERC-7579 modules.
  • ECDSAPPSOracle — Onchain oracle contract that validates PPS updates submitted by validators. Checks EIP-712 signatures, enforces supermajority quorum (≥ 2/3 weighted stake), verifies nonce binding, and forwards accepted updates to the SuperVaultAggregator.
  • Escrow — Immutable contract that holds user shares during pending redemptions (allowing cancellation) and holds assets during fulfillment until the user claims.
  • Hook — Lightweight, ERC-7579-compliant module that performs a single action (lend, bridge, swap, etc.) inside a strategy. Hooks are composable and chainable. All hook executions are Merkle-gated — only pre-authorized hook + parameter combinations can execute.
  • Keeper — Automated worker that executes authorized vault actions: allocating deposits, fulfilling redemptions, claiming rewards, swapping, bridging. Keepers operate within Merkle-authorized bounds.
  • Merkle Root — Onchain commitment to the set of authorized hook + parameter combinations for a vault. No hook can execute unless its exact call matches a leaf in the active root. Updated via a timelocked proposal flow.
  • Price Per Share (PPS) — The exchange rate between one vault share and the underlying asset. PPS = totalAssets / totalSupply. Increases as yield accrues; steps down at each performance fee-skim event. Net direction is upward when the vault generates yield. Signed by validators and accepted onchain after supermajority consensus.
  • Primary Manager — Highest-authority operator for a SuperVault. Proposes Merkle roots, updates fees, manages secondary managers, and authorizes hook configurations. Actions remain bounded by protocol timelocks and accounting constraints.
  • Secondary Manager — Delegated operator that can execute day-to-day vault operations (execute hooks, skim fees, whitelist yield sources) within primary-manager-authorized and Merkle-gated bounds.
  • Session Key — Narrowly scoped automation credential that allows keepers to execute pre-authorized actions without requiring the manager’s primary signing key for each operation.
  • SuperBundler — Off-chain service that aggregates user actions into ERC-4337 UserOps, resolves hook sequences, and returns ready-to-broadcast calldata. Accessed via https://bundler.superform.xyz/.
  • SuperGovernor — Onchain registry and access control hub. Manages role-based permissions, timelocked parameter updates, and emergency intervention powers across all SuperVaults.
  • SuperVault — ERC-7540 vault contract that holds depositor assets and issues share tokens. Entry point for deposits and redemption requests.
  • SuperVaultAggregator — Factory and registry contract. Creates vault/strategy/escrow triads, records PPS attestations, manages upkeep accounting, and enforces governor-level constraints.
  • SuperVaultStrategy — Execution engine paired with each SuperVault. Manages hook authorization via dual Merkle roots, tracks PPS high-water mark, queues and fulfills redemption requests, and enforces fee policies.
  • **UP/sUP∗∗—‘UP / sUP** — `UPis the Superform Protocol utility token. Staking it yieldssUP, which grants governance rights. $UP` also funds vault upkeep (the gas cost of validator PPS writes) and gains validator-bonding utility in later protocol phases.
  • Upkeep — $UP balance held by a vault strategy to fund PPS update gas costs. Vaults with zero upkeep stop receiving PPS updates and enter a degraded operating state. L1 vaults require at least 100,000 UP;non−L1vaultsrequireatleast1,000UP; non-L1 vaults require at least 1,000 UP.
  • Validator — Off-chain node that independently computes PPS, signs an EIP-712 attestation, and submits it onchain. Updates are accepted only with supermajority (≥ 2/3 weighted) consensus across the active validator set.
  • Yield Source — An external protocol (Morpho vault, Aave pool, Pendle PT, etc.) that a SuperVault strategy allocates to. Must be whitelisted by the primary manager and paired with a compatible oracle before keepers can interact with it.