Built On ERC-7540
SuperformOS is not an offchain vault wrapper. It is an operating system around onchain ERC-7540 SuperVaults. The vault contract holds depositor assets, issues shares, and enforces the core request and fulfillment flow. SuperformOS sits around that onchain vault: it helps operators define strategy rules, authorize executable actions, coordinate automation, maintain price attestations, and inspect operating history. SuperformOS simply makes vault operations easier to run for everyone to see, but it does not replace the vault contract as the source of custody or protocol enforcement.The Operating Stack
SuperformOS coordinates five layers:What Operators Define
Operators use SuperformOS to turn a vault mandate into explicit operating rules:- which yield sources the vault can use
- which oracles price those positions
- which hooks and action parameters are authorized
- how deposits, withdrawals, claims, and rebalances are handled
- which operators have access
- when services should pause, resume, or drain risk
- how the vault appears in Superform distribution surfaces
SuperformOS never takes custody of vault assets or private keys. It prepares transactions, displays operational state, and coordinates automation. Onchain state changes still require authorized signatures.
What The Protocol Enforces
SuperformOS is useful because the operating layer maps to protocol-enforced constraints:
This is the difference between a private operating process and a verifiable strategy engine: the rules are visible, and execution is constrained by the system.
How Execution Flows
1
Define the vault
The operator creates or imports a SuperVault, assigns operators, configures fees, funds upkeep, and prepares the vault for listing.
2
Authorize actions
The operator configures allowed hooks and parameters. SuperformOS generates merkle roots and proof artifacts, then the authorized wallet proposes and publishes them onchain.
3
Create strategies
The operator defines rule-based strategies for deposits, withdrawals, claims, swaps, bridges, or rebalances.
4
Evaluate and execute
Strategy Engine evaluates rules on ticks. When conditions pass, it submits DeFiX intents to OMS, which validates authorization and executes the corresponding hook transactions.
5
Inspect history
SuperformOS records strategy state, intent lifecycle, events, fills, errors, and transaction hashes so operators can inspect what happened and why.
Price-Per-Share And Upkeep
PPS is the accounting value of one vault share in the underlying asset. It determines deposit and redemption exchange rates, high-water-mark fee accrual, and whether a vault is operational. Validators compute PPS offchain, sign EIP-712 attestations, and submit updates onchain. Updates are checked for quorum, signature validity, timestamp staleness, replay protection, and abnormal movement. Operators fund upkeep so validators can keep PPS current. If upkeep is insufficient or PPS goes stale, vault operations can be blocked until the issue is resolved.Roles In SuperformOS
SuperformOS uses operator language in the product, but some onchain roles have precise names:
Use Permissions for the full access matrix.
Why This Matters
Programmable vaults need more than contracts and dashboards. They need an operating layer where strategy can be expressed, constrained, executed, reviewed, and distributed. SuperformOS makes that operating layer inspectable:- operators can launch vaults without rebuilding the full stack
- strategies can be described as rules instead of private process
- actions can be bounded by merkle authorization
- pricing can be backed by validator attestations
- operating history can be reviewed after the fact