Skip to content

NEST OVERVIEW

Vault Operations & Valuation

Nest vaults are designed to make institutional yield strategies accessible onchain while preserving transparent accounting, controlled minting and redemption flows, and asset-specific liquidity treatment.

Each vault token represents a pro rata claim on the vault’s net asset value. When users deposit supported stablecoins, the vault mints shares based on the current vault price. When users redeem, shares are burned or queued for redemption, and the user receives the supported redemption asset once liquidity is available.

Because Nest vaults can hold assets with different pricing and settlement conventions, the operating model combines onchain controls with asset-specific valuation inputs, liquidity management, and redemption policies.

Users subscribe to a Nest vault by depositing an approved stablecoin, such as USDC, pUSD, USDT, or another supported deposit asset for that vault and chain.

A mint uses the current vault share price to calculate how many vault tokens the user receives. The share price reflects the vault’s net asset value, including liquid assets, deployed underlying assets, pending asset movements where applicable, and accrued yield that has been incorporated into vault accounting.

After a deposit is received, Nest operations may allocate available stablecoin balances into the vault’s target portfolio. Allocation timing depends on the vault strategy, available capacity, issuer subscription windows, minimum trade sizes, and the liquidity profile of the underlying assets.

Not every deposit is immediately invested into long-duration assets. Vaults may maintain liquid reserves to support redemptions, operational settlement, and ordinary asset rotation.

Nest vaults are priced using net asset value. NAV reflects the value of assets held by the vault, including liquid stablecoin balances, short-duration liquidity assets, and underlying yield-generating positions.

For underlying assets, Nest generally uses issuer NAV as the primary pricing input. Different assets update on different schedules:

  • Highly liquid or market-priced assets may update frequently.
  • Tokenized treasury and fund products may update daily or on business days.
  • Private credit, structured credit, or longer-duration assets may update less frequently, including monthly or according to the issuer’s reporting cycle.

Routine NAV updates are handled by Nest operations. Price changes are subject to onchain bounds before they are accepted, reducing the risk of erroneous updates, stale inputs, or abnormal price movements being applied without constraint.

When an underlying asset updates less frequently, the vault’s reported NAV may update less frequently as well. This means reported performance can appear smoother than market-traded assets and may update in steps when new valuation data is incorporated.

Nest vaults generally support two redemption paths: standard redemption and instant redemption.

Standard redemption is the default path for vault liquidity. A user submits a redemption request, and the vault processes that request as liquidity becomes available.

For liquid vaults, this may settle quickly. For vaults with longer-duration assets, settlement depends on the underlying asset redemption cycle, available liquid reserves, and the size of the request relative to vault liquidity.

While a redemption is pending, the request remains part of the vault’s redemption process and is settled according to the vault’s asset liquidity and operating cadence. For some strategies, redemptions may require assets to be unwound, issuer redemptions to settle, or cash to be received from the underlying asset.

Some vaults may also support instant redemption when sufficient liquid reserves are available. Instant redemption allows users to exit immediately into a supported redemption asset, usually for a liquidity fee.

Instant redemption availability is not guaranteed. It depends on current vault liquidity, supported redemption assets, chain-specific balances, and vault configuration.

Some underlying assets do not provide continuous daily liquidity or daily NAV updates. This is common for private credit, structured credit, and certain institutional fund products.

For these assets, Nest reflects issuer NAV and aligns redemption expectations with the underlying asset’s liquidity terms. A vault that includes periodic-liquidity assets may still support onchain transfers and redemption requests, but final settlement can depend on the underlying asset’s reporting and redemption cycle.

This structure is intentional: users receive onchain access to institutional strategies, while the vault preserves the real-world economics and liquidity constraints of the assets it holds.

Nest vault operations are designed around controlled execution rather than discretionary unilateral movement.

Key controls include:

  • Approved deposit and redemption assets per vault and chain.
  • Onchain price update bounds.
  • Role-based permissions for vault operations.
  • Smart-contract enforced minting and redemption paths.
  • Public contract addresses and API-visible vault state.
  • Asset-level reporting, risk materials, and issuer links where available.
  • Audited vault contracts and operational review for sensitive changes.

The goal is to make the vault’s operating model legible: users should be able to understand what assets are held, how the vault is priced, what redemption path applies, and what liquidity timeline is reasonable for the strategy.