Vault economics
Operate approved allocation, market attachment, caps, routing, roles, and fee configuration workflows.
Vault economics are governed protocol configuration, not a general-purpose billing API. Approved vault owners, curators, allocators, and asset managers can use the maintained Developer Preview workflows that match their current onchain authority.
Available workflow families
| Objective | Maintained workflow examples |
|---|---|
| Allocate or deallocate capacity | role.allocator.vaultAllocate, role.allocator.vaultDeallocate, role.vault_owner.vaultReallocationBatch |
| Attach a vault and market | role.curator.vaultMarketListingSave, role.vault_owner.attachMarketToVault |
| Configure caps and minimum deposit | role.vault_owner.vaultCuratorCapsSettingsSave, role.vault_owner.vaultSettingsUpdate |
| Configure fees | role.vault_owner.vaultFeeConfigUpdate |
| Change allocator, routing, or role configuration | role.vault_owner.vaultAllocatorUpdate, vaultRoutingUpdate, vaultRoleSettingsSave |
The API derives calls from the current canonical vault state, verifies the active signer authority, rejects no-ops where appropriate, preserves transaction order, and requires canonical postconditions. It never exposes an arbitrary contract-call surface.
Fee semantics
The active V2 vault stores a single curator fee recipient across management and performance fee
rates, plus separate reseller and borrower-manager fee fields. Use the current
vaultFeeConfigUpdate request schema and API reference. Do not model two conflicting nonzero curator
recipients or assume that a zero rate implies a payable fee.
Allocation and attachment
Allocation actions are value-moving and must retain exact vault, market, asset, amount, authority,
and freshness context. Market attachment can require an ordered registry, supply-access, and vault
sequence. Each predecessor reaches canonical final_success before the next transaction is
registered.
Product-facing accounting
Configuration receipts are operational evidence, not customer balances. After a successful action, refresh the affected vault, allocation intelligence, fees, market, and deployment resources before presenting the new state. See Yield and fee accounting.