Deploy Capital with Policies

Documentation Index

Fetch the complete documentation index at: https://v2-docs.exponent.finance/llms.txt

Use this file to discover all available pages before exploring further.

---

Vault capital is deployed through a policy model where every strategy action must match an approved onchain policy before it can proceed. This is one of the core design principles of Exponent Strategy Vaults. At a high level, vault strategy execution works like this:

1. the vault has defined roles
2. the vault adds support for one or more policies
3. the authorized Allocator role builds a supported strategy action
4. the action is wrapped into executable vault transactions
5. the transaction executes only if it matches an approved policy

​

What Policies Do

Policies define what the vault is allowed to do. In practice, they gate:

• which programs the vault can interact with
• which instructions are allowed
• which assets can be used
• which accounts or protocol contexts are valid for execution

If a strategy action does not match an installed policy, the transaction is rejected.

​

Strategy Execution Flow

A typical strategy interaction follows this pattern:

​

Supported Strategy Interfaces

Exponent Strategy Vaults currently support multiple strategy interfaces.

​

Exponent Core

Use Exponent Core when the vault needs to interact directly with yield stripping mechanics. Typical uses include:

• stripping base assets into PT and YT
• merging PT and YT back into base
• building fixed-rate or variable-yield strategies directly on top of Exponent’s issuance layer

​

Exponent CLMM

Use the Exponent CLMM when the vault strategy needs to provide concentrated liquidity or direct PT / YT trading through the CLMM venue. Typical uses include:

• providing PT / SY concentrated liquidity
• buying or selling PT
• buying or selling YT through the CLMM routing path
• collecting fee and emission flows tied to LP positions

​

Exponent Order Book

Use the Exponent Order Book when the strategy needs precise rate execution or passive quoting through offers. Typical uses include:

• posting offers
• taking liquidity
• removing offers
• withdrawing settled funds

​

Kamino Lend

Use Kamino Lend when the strategy needs to allocate capital into lending, borrowing, or loop-based position management on Kamino. Typical uses include:

• deposit
• withdraw
• borrow
• repay

​

Kamino Vaults

Use Kamino Vaults when the strategy needs direct exposure to a managed Kamino Vault instead of reserve-level lending positions. Typical uses include:

• deposit into a Kamino Vault
• withdraw Kamino Vault shares back into the underlying asset

​

Loopscale

Use Loopscale when the strategy needs lender-side strategy management or borrower-side loan execution through Loopscale’s API-backed flow. Typical uses include:

• create and fund strategies
• update or withdraw from strategies
• create loans
• deposit collateral
• borrow principal
• repay and close loans

​

Titan

Use Titan when the strategy needs swap routing through the Titan DEX aggregator. Typical uses include:

• spot swaps required to rebalance a vault strategy
• asset routing between strategy legs
• handling execution paths outside native Exponent venues

​

Policy Builders

Each supported integration typically has a policy builder that helps define the allowed action surface before execution. These builders are used to create the policy configuration that the vault installs onchain before the strategy is allowed to run. As a result, there are two distinct steps:

1. define what is allowed
2. execute an action within that allowed set

Installing an instruction builder alone is not enough. The corresponding policy must also exist.

​

Before and After AUM

Policy management matters around the vault’s AUM lifecycle. Before the vault holds depositor funds, policy setup is more flexible and should be finalized as much as possible. Once the vault has AUM, changes to the strategy surface become more sensitive and may require governed change flows depending on the setting being modified. Therefore, strategy and policy design should be treated as part of vault setup, not as something to postpone until after launch.

​

To Summarize

• Policies define what the vault may do
• Action builders define what the strategy wants to do
• Vault sync transactions turn the Allocator’s actions into executable transactions

​

Where to Go Next