Spark Savings, Yearn & Fluid Vaults: Deposits and Exits

Inspect the vault identity

Open Yearn, Spark Savings or Fluid lending. Inspect the exact vault and underlying contract. Yearn discovery uses the endorsed V3 registry and supported withdrawal queues; Fluid uses its lending-token factory. An unavailable vault stays unavailable rather than displaying a fabricated rate.

Deposit assets, receive shares

Deposit uses the underlying asset. Its finite token approval and the deposit are separate wallet transactions. The preview estimates receipt shares using current state. Share exchange rates can move; the standard vault calls do not include a universal minimum-share argument. Check asset behavior and the preview carefully. Keep ETH for gas.

Withdraw assets or redeem shares

Withdraw names an underlying amount. Redeem names a share amount. Read maxWithdraw and maxRedeem, which reflect current liquidity and restrictions. Yearn’s strategy queue shows current allocations and the accountant address. Bitpont does not yet decode every accountant’s fee schedule; inspect the vault’s terms instead of assuming a displayed net share value explains all fees.

Use a Spark withdrawal request

When supported and enabled for the vault, set shares and a deadline, then approve those shares to the withdrawal manager. The request binds the owning wallet as recipient. Inspect an existing request before replacing it. A request can expire or be cancelled; neither means the assets have been delivered. Refresh the account and verify the resulting transfer.

Move proceeds into another position

After confirming an exit, use Position routing for an eligible same-chain ERC20 or vault-share route when Enso access is configured. Inspect both contracts and the minimum output. The new vault adapters are not all interchangeable with the older migration planner. Portfolio lists returned pages and receipt balances without claiming exhaustive discovery.