Go to article content
Badgerdao

Badgerdao legacy vaults

Last updated -

BadgerDAO's legacy Sett vaults are deprecated automated yield vaults. Unstake first if the shares that you want to redeem remain in a staking contract. For shares already in your wallet, use the matching vault's withdrawal function without that preliminary unstaking transaction.

Product status
BadgerDAO's June 11, 2025 transition announcement said the vault products had been deprecated in 2022.
Interface access
Legacy vault web interfaces closed after June 30, 2025. BadgerDAO documents direct interaction with the legacy Ethereum contracts through Etherscan.
Unstaking units
The unstaking amount counts vault shares in raw units. The withdrawal guide describes these as shares in Wei; the underlying asset balance is a different quantity.

Shares and withdrawal assets

Vault shares represent a claim on a vault's underlying asset. A separate staking contract can hold those shares while recording a balance for your wallet. Unstaking returns the shares to your wallet, making them available for redemption through the vault.

The legacy manual lists BADGER, WBTC, and DIGG vaults alongside Curve pool tokens and SLP positions. Each vault has its own contract and underlying asset, so a withdrawal does not necessarily produce native BTC.

Withdrawal decision checklist

  • If the relevant staking contract reports a nonzero totalStakedFor balance, unstake the shares that you intend to redeem.
  • If matching vault shares are already in your wallet, use that vault's withdrawal route for those shares.
  • If you have several legacy positions, inspect each applicable staking and vault contract separately.

Contract inputs and transaction order

BadgerDAO's Etherscan Guide places totalStakedFor under Read Contract as Proxy . The query takes your wallet address and reports its staked share balance for that contract.

The documented unstake call uses Write Contract as Proxy with the wallet that holds the stake. Its amount field takes raw shares, and its data field takes 0x , meaning empty data. Vault redemption follows confirmed unstaking for any shares that must first return from a staking contract.

The manual documents withdrawAll on the matching vault's Write Contract as Proxy page. That function redeems all vault shares that the calling wallet holds in the selected vault. Transaction confirmation and the resulting asset balance establish the withdrawal outcome; submitting the transaction alone does not.

Historical fees

The archived Sett Vaults fee schedule distinguished withdrawal fees by vault family. Curve Convex, Sushiswap wBTC/ETH, Sushiswap ibBTC/wBTC, and Convex Helper vaults carried a listed 0.10% withdrawal fee. The Convex Helper entry covered cvxCRV and CVX. Native BADGER and DIGG single-staking and liquidity-pool vaults had a listed withdrawal fee of 0%.

Those historical figures do not establish the fee currently configured in a selected legacy contract. Performance fees in that documentation applied to strategy profits, separately from the withdrawal-fee schedule.

Graphic: Historical fees (Badgerdao legacy vaults)

View full-size image

Separate BadgerTree rewards

BadgerTree rewards use a separate claim process with wallet-specific Merkle data. The getClaimableFor query uses a wallet address, token list, and cumulative amounts to determine remaining claimable rewards. Cumulative allocations alone do not establish the amount that remains claimable, and a vault withdrawal does not perform that reward claim.