> For the complete documentation index, see [llms.txt](https://docs.vesper.finance/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.vesper.finance/vesper-2/risks.md).

# Risks

Vesper 2 provides a common interface for accessing yield through onchain strategies, but participation involves risks associated with the underlying assets, external protocols, market conditions, and Vesper's own smart contracts.

#### Asset & Depeg Risks

Each Vesper 2 product is backed by a specific underlying asset. Vesper USD uses USDC, while Vesper ETH uses WETH.

These assets carry their own risks, including issuer, custody, smart-contract, liquidity, and market risks.

For example, USDC may trade below its intended $1 value during periods of market stress or issuer-related disruption. Similarly, WETH remains exposed to movements in the market value of ETH and risks associated with its underlying contracts.

Vesper USD and Vesper ETH use fixed-price adapters configured at 1.0 for their respective underlying assets. These adapters do not automatically adjust conversion rates in response to external market-price movements.

As a result, a fixed 1:1 conversion within Vesper 2 does not guarantee that the underlying asset will maintain its expected market value.

#### Strategy & External Protocol Risks

Assets deposited into Vesper 2 may be allocated across YieldVault strategies interacting with external DeFi protocols.

These strategies inherit risks associated with the protocols and positions they use, including smart-contract vulnerabilities, liquidity constraints, oracle failures, market movements, and protocol-specific economic risks.

Some strategies may involve additional risks associated with lending markets, liquidity pools, or fixed-yield instruments, depending on how capital is allocated. Although capital can be diversified across strategies, diversification does not eliminate the possibility of losses.

#### Liquidity & Redemption Risks

The value backing a Vesper 2 product may differ from the amount immediately available for redemption. Some underlying strategies may hold positions that cannot be withdrawn immediately or exited at their accounting value without incurring slippage or discounts.

Vesper 2 is designed to avoid intentionally forcing strategy exits below their net asset value (NAV) solely to satisfy redemptions. As a result, users may experience delays or be temporarily unable to redeem their Vesper tokens when sufficient liquidity is unavailable, even if the product remains fully backed from an accounting perspective.

Users staking their Vesper tokens may also be subject to a configurable cooldown period when unstaking. Once a cooldown request is submitted, the corresponding assets stop earning yield until the request is completed or cancelled.

Instant unstaking may be available as an alternative, subject to the contract's configuration and applicable fees.

#### Smart Contract & Administrative Risks

Vesper 2 relies on smart contracts to manage deposits, redemptions, staking, capital allocation, and yield distribution. Several core contracts use upgradeable proxies, while administrative and operational functions are controlled through privileged roles and contract ownership.

These permissions allow authorized parties to manage protocol parameters, including fees, withdrawal conditions, supported assets, and capital allocation. The PeggedToken contracts also include administrative permissions to restrict token transfers involving blacklisted addresses.

These controls are part of the protocol's operational and security architecture, but they introduce risks associated with contract upgrades, access control, operational errors, and the potential compromise or misuse of privileged permissions.

Role-based access control separates responsibilities, but it does not eliminate smart-contract or administrative risks.

#### Audits & Security

Vesper 2 builds on smart contracts developed in collaboration with Vetro. The underlying contracts have undergone third-party security audits, including an audit by **Quantstamp**. Vesper 2 includes some modifications to the underlying Vetro implementation.

The audit reports are available here:

[**Audit Reports**](https://github.com/vetro-protocol/audit-reports/tree/main/Vetro_Protocol)

Audits provide independent assessments of smart-contract security and can help identify potential vulnerabilities. However, an audit does not guarantee that a protocol is free from bugs, exploits, or other risks.

Users should understand the risks associated with Vesper 2 and its underlying strategies before depositing assets.
