Beefyfinance
Beefyfinance zap connects supported token choices with vault entry and exit
Beefyfinance zap converts a supported starting token into the assets that a chosen vault needs, or converts a withdrawal into a supported output token. Token choice therefore changes the route, the required swaps, and the eventual wallet balance. Supported crosschain and vault-to-vault routes also serve moves between networks or products, subject to the selected route's availability.
A wallet token, an LP token, and a vault receipt represent different holdings. Matching the intended outcome to the correct holding makes entry and exit easier to interpret. A convenient conversion route does not change the vault's underlying investment exposure.
Key takeaway: A crosschain deposit reaches its intended outcome only when the destination vault issues the correct receipt to the wallet.
The input token, deposit asset, and vault receipt serve different purposes
Zap is an asset-conversion workflow around a vault, so the token used to enter may differ from the asset that the strategy holds. A standard deposit uses the vault's own deposit asset. For a liquidity pool (LP) vault, that asset represents a pool position. A compatible zap can construct the required position from a supported starting token. The vault then issues its receipt, commonly a mooToken. That receipt represents a share of the deposited assets. The strategy continues to compound its own deposit asset, even when a zap accepts a different funding token.
Exit choices run in the other direction. A normal redemption returns the vault asset, while an eligible zap route converts it into the selected output when the next task requires liquid tokens rather than an LP position. Compatibility belongs to the exact product and route, so support for one asset does not establish support for every token.
Can a pool component fund an LP vault deposit?
A supported pool component can fund an LP vault deposit through a V1-style zap, subject to the product's available routes. This route uses the pool's liquidity to obtain the other component. The LP token represents exposure to both assets. Funding from one component therefore serves a different purpose from holding only that component.
Aggregator-based routes address entry from a supported token outside the pool's component set. They acquire the deposit assets through integrated swap services. Product design determines the required mix. A conventional UniV2-style pool uses equal-value proportions, while Beefy's concentrated liquidity manager (CLM) products can require an unequal mix. Simulation estimates that mix before the route calculates swaps. Supplying equal token counts does not establish equal value. If the wallet already holds the accepted LP token, a direct deposit can avoid conversion that the entry task does not require.
Withdraw into the token required for the next task
A zap withdrawal suits an exit whose goal is a supported liquid token rather than the vault's deposit asset. For an LP vault, the route unwinds the liquidity position and converts the proceeds into the chosen output. Ordinary redemption leaves the LP token available for separate liquidity management. Use an integrated exit only when its output list includes the asset you need.
Can a zap reach a vault on another chain?
A supported crosschain zap can connect funds on one network with a vault on another network through Zap V4. Circle's Cross-Chain Transfer Protocol (CCTP) carries value between the chains using USDC burning and minting. Source-chain execution and destination-chain completion occur separately. The wallet needs the source chain's native token for gas. Eligibility requires a compatible product, input asset, and chain combination; Beefy's broader presence on a network does not establish crosschain support for every product.
Move a position between supported vaults
Vault-to-Vault Zaps, or V2V, serve a change of product through Beefy's supported routing system. They extend Zap V4 to connect an existing Beefy product with another compatible product, including supported crosschain routes. The starting holding is already a vault position. Availability belongs to the pair of products, so a compatible destination alone does not establish a complete route.
A dedicated Migration Module can provide a replacement route for an affected product when Beefy offers one. Such a module does not establish that every retired product has a replacement. Direct redemption fits a move whose intended destination lies outside the available routing options.
Follow a crosschain deposit from token choice to vault receipt
A crosschain token-to-vault deposit uses Zap V4's conversion, bridging, and deposit components to turn a supported wallet asset on the source network into a vault share on the destination network. Direct deposit alone requires the accepted asset on the vault's own chain. The crosschain route only fits while its product, token, and network requirements remain satisfied.
Read each amount in its displayed token units. The funding amount counts the input token. An estimate expressed in the vault asset counts that asset; a receipt balance counts vault shares. Those quantities need not match because they describe different holdings.
Compatibility and authorization come before execution. The wallet must cover source-chain gas. Token transfers also require the permissions that the chosen method uses. A Permit2 transfer needs both sufficient token allowance to Permit2 and a signed permit.
| Stage of a crosschain vault deposit | What can prevent or obscure completion |
|---|---|
| Select the input token, source chain, and destination vault. | The required combination may have no supported route. |
| Review the route and estimated deposit assets. | Price impact can make an available conversion unattractive. |
| Provide the token permission that the route requires. | Insufficient allowance can require approval before execution. |
| Submit the source transaction that prepares USDC and initiates bridging. | Pending or failed source execution leaves the destination deposit incomplete. |
| After the source transaction succeeds, wait for Beefy's Hook Executor to trigger the relay and the receiver to attempt the destination zap. | The deposit can fail after bridging and enter a refund or recovery path. |
| Confirm the destination vault receipt and remaining wallet assets. | The receipt count need not match the estimated deposit-asset amount. |
Check the source-chain transaction's success status before treating that stage as complete. Destination execution still needs the bridging attestation and relay. Beefy's Hook Executor obtains the attestation and triggers destination processing. The receiver attempts the final zap, which can produce a vault receipt or a recovery outcome. USDC arriving on the destination network does not itself establish a completed deposit.
Unused tokens can return to the wallet alongside a successful deposit's vault receipt. The receipt confirms the vault holding, while those leftovers remain separate wallet assets.
Which conditions make a direct withdrawal preferable?
A direct withdrawal fits a need to retain the vault asset, particularly when a zap quote involves an unfavorable conversion. A zap's slippage protection does not eliminate the price impact of its swaps. Slippage concerns movement between quoting and execution. Price impact comes from the trade changing the pool's price. Thin liquidity can make a supported output expensive to obtain even when the transaction stays within its slippage limit.
A zap also relies on the underlying position becoming withdrawable. Lending strategies can struggle to unwind when their lending market lacks available liquidity. Choosing another output token does not remove that dependency. The product's Risk Checklist remains relevant to the investment exposure; a convenient exit route does not replace that assessment.
Exit retired Sonic products through their own routes
Beefy ended yield generation in its Sonic products and validator as part of the October 6, 2026, retirement. The deprecation left retired vault positions available for withdrawal and supported crosschain exits through CCTP. The app's My Positions tab exposes relevant retired products after the wallet connects. Their continued appearance does not indicate an active earning opportunity.
beS redemption follows a separate request-and-claim process with a 14-day withdrawal period from the initial request. Swapping beS through a liquidity pool uses the thin liquidity described in the retirement notice and can return less than its underlying S redemption value. Sonic-held mooBIFI can leave through its bridge route, which Beefy recommends over swaps through thin liquidity. Beefy closed the route into Sonic. Identify the actual holding before choosing an exit, because a retired vault position, beS, and mooBIFI require different routes.
Quick answers about Beefyfinance zap
-
Why can a zap return a small balance of another token?
- A zap can return unused assets when execution produces a different asset mix from the simulated deposit. Swaps and liquidity additions can change the quantities that the product accepts. A leftover token therefore does not, by itself, prove that the deposit failed. The vault receipt and the transaction outcome establish whether the intended position exists.
-
Is a Permit2 signature the same as an onchain token approval?
- A Permit2 signature supplies permission for a specified transfer, while an onchain token approval sets an allowance. The BeefyZapRouter supports an entry method using existing approval and another accepting a signed Permit2 permit. The signed-permit method also requires sufficient token allowance to Permit2; a signature does not itself establish that the vault deposit completed.
-
What makes quotes for the same output token differ?
- Different swap paths and aggregator pricing can produce different quotes for the same output token. The required amount of conversion also depends on the product's deposit composition. Some aggregators incorporate charges into their quoted output. Compare the estimated received amount for the same input and intended destination; token availability alone does not establish equivalent execution terms.
-
Will closing the app cancel a crosschain zap?
- Closing the app does not undo a confirmed source-chain transaction. A crosschain zap can still require destination minting or deposit execution afterward. Beefy's progress interface can offer continuation for an interrupted process, and technical support can assist with pending CCTP minting. The relevant state follows the onchain transfer and destination processing, not whether the browser stayed open.
-
Does a Free Zap promotion cover token-to-vault deposits?
- The June 19, 2026, launch promotion covered selected Vault-to-Vault routes and excluded token-to-vault deposits. Free Zap meant waiving Beefy's zap swap fee on included routes. Source-chain gas and applicable crosschain bridge and relay fees remained payable. Only routes with the applicable promotion tags qualify for an active offer.