Beefy finance vault selection and supported asset requirements

The underlying strategy determines the exposure you accept

Vault compatibility concerns the actual token contract and strategy, including the assets beneath any liquidity position. A matching ticker does not establish compatibility across networks or between different token representations. The vault’s accepted asset and the assets that generate its returns can also differ.

Single-asset strategies may earn through lending or staking arrangements. Liquidity pool strategies expose deposits to the pool’s assets and trading activity. These choices have different dependencies: lending relies on the underlying market, while liquidity provision also changes the position’s asset composition as relative prices move. Selecting a single input token through a conversion route does not make the resulting position single-asset exposure.

View full-size image

Zap routes change the input without changing the destination strategy

Beefy Zap can convert supported inputs into the assets that a destination product requires, subject to route availability.

Direct assets and converted deposits

A direct deposit uses the asset that the vault already accepts. A Zap route may add swaps and liquidity provision before the vault deposit. Its quote therefore includes conversion effects that a direct deposit may avoid. Examine the destination product and estimated output together; a convenient starting token does not change the underlying investment.

Transfers between vault positions

Supported vault-to-vault routes connect an existing position to another vault, including routes that cross networks. Availability depends on the particular products and route. Swaps introduce price impact and slippage, while a cross-network route adds bridge or relay dependencies. A successful source transaction alone does not prove completion on the destination network. The destination position must also exist.

Harvesting turns farm rewards into more strategy assets

Autocompounding strategies collect earned rewards and reinvest them into the asset or position that the vault manages. In a typical liquidity pool strategy, harvesting claims farm rewards, swaps them into the required constituent assets, and adds liquidity. The strategy then deploys the resulting liquidity tokens again.

This process pools operational work across depositors. It reduces the need for each wallet to claim, swap, and reinvest rewards separately, although the strategy still incurs execution costs. Harvest activity follows the strategy’s economics and configuration rather than a universal schedule. Some strategies also harvest during deposits to account for existing rewards before admitting new funds.

Reward reinvestment increases exposure to the strategy’s assets. It does not protect their market value.

View full-size image

Vault shares separate your claim from the displayed token count

Standard vault shares track proportional ownership, so their quantity need not match the quantity of deposited assets. A standard Beefy vault issues mooTokens representing the depositor’s share of its assets. Successful compounding can increase the underlying assets attributable to each share while the wallet’s share count stays unchanged. Losses can reduce that entitlement. The share balance and the redeemable asset balance therefore answer different questions, and neither alone establishes the position’s value in money. A successful direct withdrawal burns the redeemed mooTokens and returns the vault’s deposit asset, less any applicable withdrawal fee. For a standard LP vault, that asset is the LP token; removing the underlying liquidity requires a separate action.

What does a vault’s APY tell you?

A vault’s annual percentage yield estimates a compounded annual return using the earning conditions reflected in its calculation. The figure annualizes those conditions; it does not establish what the vault will earn throughout a future year. Annual percentage rate expresses a rate without the same compounding treatment.

Reward emissions, trading activity, deposited capital, and token prices can change the estimate. A liquidity position may accumulate additional tokens while losing market value. Similarly, a temporary reward program can lift projected earnings without supporting that rate indefinitely.

Compare yields alongside their source. Lending interest, trading fees, and incentive tokens expose returns to different conditions. Total value locked describes deposited value, but it does not measure withdrawal liquidity or establish contract safety. Neither a large deposit base nor a high APY replaces understanding the strategy.

Performance fees and transaction costs use different calculation bases

Vault performance fees apply to harvested earnings, while entry and exit costs arise from the transactions and routes used.

Charges within the strategy

Most Beefy vaults charge a performance fee on harvested rewards. The displayed yield accounts for the applicable performance fee, so subtracting it again would double-count that deduction. Fee settings vary across products. Some vaults also charge a withdrawal fee, which has a different calculation basis from the fee on earnings.

Costs attached to your route

Wallet transactions require network fees. Zap routes can add swap fees and price impact, and cross-network routes can involve bridge or relay charges. These costs depend on the chosen route and transaction conditions. A quoted yield does not describe the total cost of entering and leaving your particular position.

Frequent movement can consume earnings through repeated execution costs. A route promotion that waives one charge does not necessarily remove the others.

Concentrated liquidity changes the balance of assets you hold

Beefy’s Cowcentrated Liquidity Manager, or CLM, manages liquidity within price ranges rather than across every possible price. Its positioning logic manages the supplied assets as market prices change. Concentrating liquidity changes both its earning opportunities and its sensitivity to relative price movements.

CLM reinvests trading fees where the underlying pool pays them; additional incentive rewards receive different treatment. A CLM Pool can provide separately claimable rewards. A CLM Vault adds an autocompounding strategy that reinvests applicable incentives into the underlying position. Their receipt tokens and reward treatment differ, so the standard mooToken explanation does not describe every product identically.

Impermanent loss remains possible. This is the shortfall caused by relative price changes compared with holding the same starting assets separately, before fees and rewards. A withdrawal returns a proportional share of the assets then held, which can differ from the original deposit mix. Automated range management does not guarantee recovery of that original mix or value.

View full-size image

BIFI participation and boosts have separate purposes

BIFI connects governance participation and tokenholder incentive programs, while boosts add rewards to eligible vault positions. Holding BIFI gives governance rights under the protocol’s arrangements. Participation in its tokenholder earnings products requires depositing into the relevant BIFI Pool or BIFI Vault. Ordinary vault access instead follows that vault’s own asset requirements.

A boost generally involves staking an eligible vault receipt token into an additional rewards contract. The underlying autocompounding position continues operating while the boost distributes separate incentives. Availability and rewards belong to the particular campaign. A boosted position therefore includes an additional contract dependency and may require separate reward claims, unlike earnings that the underlying vault reinvests automatically.

Pauses and underlying protocol failures can constrain access

Strategy controls and underlying protocol conditions can interrupt deposits, harvesting, or withdrawals, depending on the affected contracts. Standard vaults generally have no fixed holding period, but execution still requires functioning contracts and access to the underlying assets. Emergency controls can stop new activity or attempt to pull funds back from an underlying protocol. They cannot guarantee recovery after a loss. A retired vault also differs from an active deposit destination; its status alone does not establish whether every withdrawal dependency works.

Automated compounding versus managing the underlying position yourself

A Beefy vault delegates strategy execution to contracts, whereas direct participation leaves more operational work with the depositor. Manual farming can require separate reward claims, swaps, and reinvestment transactions. It also leaves the timing of those operations under the wallet holder’s control. A vault exchanges that control for shared execution and its associated fees.

The comparison includes additional contract exposure. Vault and strategy contracts sit alongside the underlying farm, lending market, or liquidity pool. Reviews, testing, and emergency controls address particular risks, but they cannot eliminate contract defects, asset failures, or inaccessible underlying funds. Concentrated liquidity and optional conversion routes add their own dependencies.

Holding assets without deploying them avoids the vault and farming operations, while retaining the assets’ own price and custody risks. Direct farming retains the underlying protocol exposure and requires more transaction management. An autocompounding vault suits the task of maintaining a chosen strategy without manually reinvesting each reward, provided its accepted assets, costs, and dependencies fit the intended position.