> For the complete documentation index, see [llms.txt](https://docs.aspanfi.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.aspanfi.com/yield-options/aspan-vaults.md).

# ASPAN Vaults

ASPAN Vaults are a planned option for managing funds across approved external yield protocols. They sit alongside native ASPAN DeFi as a separate strategy path within the proposed ASPAN Account.

**Status:** the Vault product, contracts, share design, supported integrations, and withdrawal terms remain planned. No production external-strategy Vault or completed integration is claimed here.

### What ASPAN would build

The proposed Vault layer covers deposits, strategy allocation, position valuation, shares, withdrawals, permissions, and reporting. Approved adapters would connect it to underlying protocols.

Building this management layer does not create a new source of yield. Borrower interest, protocol activity, or disclosed incentives must generate the underlying income. Costs and losses can reduce or outweigh that income.

### A defined mandate for every Vault

Each Vault should publish its accepted assets, approved protocols, exposure and leverage limits, valuation method, fee structure, and withdrawal process before it is offered. Users need to understand which risks the Vault can take and which changes require further authorization.

A pooled Vault follows a common strategy mandate. Account-level preferences determine whether and how much a user may allocate to that Vault; they do not make the shared portfolio individually customizable. A user whose rules do not fit the mandate should not be allocated to it.

### Shares and accounting

Shares would represent a claim on the relevant Vault's assets under its own accounting rules. The share standard, token naming, income treatment, and handling of losses will depend on the final design.

The existing s-apUSD token belongs to the native apUSD staking vault. It should not be interpreted as a share in these planned external-strategy Vaults.

### Withdrawals and payment liquidity

The actual withdrawal process depends on the underlying positions. Available cash, protocol utilization, queues, market liquidity, and conversion routes can affect timing and proceeds.

The account manager would need to plan exits ahead of payment commitments and keep pending withdrawals separate from available funds. A Vault's displayed NAV is not an instant-redemption promise.

### Risks and strategy admission

External strategies can introduce smart-contract, stablecoin, counterparty, liquidity, oracle, and concentration risks. Several Vaults may share the same underlying dependency, so limits should consider combined exposure rather than only the number of positions.

A future RWA strategy would also require asset-specific eligibility, transfer, custody, and redemption analysis. RWA integration is an expansion possibility, not a current capability.

New Vault contracts and adapters require their own review. The initial native DeFi audit does not cover this product. Fees and supported strategies will be disclosed when a release is ready; these docs do not set a price or target APY.

See [Yield Options](https://docs.aspanfi.com/yield-options/yield-options) for the comparison framework and [Smart Contract Security](https://docs.aspanfi.com/risk-management/smart-contract-security) for audit boundaries.
