Aura finance wind-down, withdrawals and redemption limits
Aura finance wound down its Balancer yield operations, leaving pools in withdrawal-only mode. Existing positions and redemption tokens require different exit decisions. A pool withdrawal releases a deposited position; AURA redemption exchanges tokens for treasury assets. The token held, its location and the applicable claim window determine the available action. A displayed balance alone does not establish whether assets sit in a wallet, a vault or a locker.
In this guide
Key takeaway: A withdrawal releases an existing position, while treasury redemption follows the eligibility and timing attached to each token.
Withdraw a position or resolve a missing balance
LP, vault and locker positions remain withdrawable during the sunset. A missing wallet balance can reflect assets held inside a staking or vault contract. That calls for identifying the deposited position before choosing a redemption action. Withdrawing vault shares and redeeming a wallet token involve different contracts and different outputs. If the connected account shows no eligible position, changing the amount cannot resolve an account or network mismatch.
Establish token identity before authorization
The connected account must control the position that the selected contract accepts, with the wallet on the network where that position exists. Similar token names do not establish compatibility. A vault share represents a claim on underlying assets, while a freely held token has its own balance. An interface can display both without making them interchangeable.
Authorization also has a narrower meaning than completion. A token approval permits a specified contract to spend tokens; it does not itself perform the intended redemption. The requested spender, amount and subsequent operation determine what authority the transaction grants. An unexplained approval should not become a substitute for resolving an unsupported token or missing position.
For a withdrawal preview, distinguish the quantity of shares surrendered from the quantity of underlying tokens returned. Those numbers describe different units, even when a dashboard presents them beside each other.
Balancer rewards and the positions they left behind
Aura originally combined Balancer liquidity staking, pooled voting power and AURA incentives. Liquidity providers deposited Balancer Pool Tokens, or BPTs, into its staking system. Aura's protocol-held veBAL helped boost eligible BAL rewards, while AURA supplied additional incentives. That arrangement explains why an old position can include deposited liquidity and separate reward balances.
BAL stakers had another entry path. Aura issued auraBAL against deposited 80/20 BAL/WETH BPT, which the protocol locked to obtain veBAL voting power. The original minting operation was irreversible. Trading auraBAL through a liquidity pool provided a separate market exit rather than undoing that deposit. AURA lockers directed governance and the protocol's veBAL voting power. These functions describe how the protocol operated before its wind-down. Aura protocol mechanics
When do the redemption rights change?
Stage 1 opened on 13 May 2026, allowing AURA redemption for proportional treasury assets while minting rAURA redemption tokens.
Stage 1 claims close on 10 May 2027. Stage 2 redemption for rAURA and Stage 3 redemption for auraBAL are scheduled to open on that date.
The rAURA allocation includes unclaimed Stage 1 treasury assets plus 10% of the 80/20 BAL/WETH BPT.
The auraBAL allocation covers the remaining 90% of that BPT. WETH means wrapped Ether; the allocation concerns pool tokens.
These percentages divide the specified BPT allocation between holder groups. They do not describe investment returns or the percentage of an individual's purchase cost recovered. The shared later date also does not make AURA, rAURA and auraBAL interchangeable claims.
Vault shares and shutdown unlocks
The AuraBalVault compounder uses ERC-4626-compatible shares, with preview and maximum-withdrawal functions that distinguish shares from underlying assets. Its redemption operation calculates underlying tokens from surrendered shares and deducts the configured withdrawal penalty unless the withdrawal burns the last outstanding shares. The last withdrawal instead harvests and withdraws the remaining underlying assets. The locker has a separate shutdown condition: its emergency withdrawal requires shutdown and a nonzero locked balance. That route concerns locked staking tokens, not a treasury distribution.
Match the holding to its exit condition
The relevant choice starts with the asset or position already held. These options are not substitute products: each accepts a particular input and applies its own conditions. A withdrawal from one contract can leave an asset whose eventual disposal involves another decision.
| Holding or position | Applicable exit condition |
|---|---|
| AURA | Treasury redemption within Stage 1. |
| rAURA | Later-stage redemption entitlement. |
| auraBAL | Separate later-stage BPT allocation. |
| AuraBalVault shares | Underlying withdrawal subject to the owner's available shares and contract limits. |
| Locked AURA | Emergency withdrawal requires locker shutdown and a positive locked balance. |
| Selection rule | Match the operation to the holding, then apply its timing and contract conditions. |
A successful transaction record confirms execution, while token transfers identify what the account actually received. Neither a disappearing dashboard entry nor a completed approval establishes that the intended assets reached the intended recipient.
The boundary between withdrawal and an asset sale
Reviewing a balance or preview leaves the position unchanged. Once an authorized transaction executes, closing the interface cannot reverse its transfers. Confirm token identity, expected output and recipient before signing any transaction. A missing compatible withdrawal route is a reason to pause the transaction, not to send assets directly to a contract address.
Withdrawing staked BPT generally leaves ownership of the underlying pool position intact. Exiting that pool is another operation, with its own supported assets and output conditions. Similarly, a treasury distribution can leave several assets whose market values change independently. The next decision concerns the assets actually received: whether to retain that exposure or evaluate a separate pool exit or sale.
Your questions, answered
Why does an old Aura APR not predict a redemption payout?
An old APR described an annualized reward estimate, while a redemption payout depends on the assets allocated to the relevant claim. Historical reward estimates also depended on changing token prices, staking balances and emissions. Applying an old percentage to a token balance does not calculate the treasury assets that a redemption will deliver.
Do withdrawals still require a network transaction fee?
A withdrawal that changes blockchain state requires a network transaction, even during a protocol wind-down. The wallet needs the network's fee asset to submit it. That cost is separate from the withdrawn token amount and any contract-level deduction; an available position does not mean the wallet can fund its transaction.
Does the locker emergency withdrawal also collect every reward?
The locker emergency withdrawal releases locked principal without checkpointing or accruing rewards in that operation. It should not be treated as a combined withdrawal and reward claim. Its implementation requires the locker to be shut down and the account to have a positive locked balance.
Is a rejected wallet request the same as a failed on-chain transaction?
Rejecting a request before submission leaves that requested transaction unbroadcast. An on-chain transaction that reverts has reached the network and can consume a transaction fee despite reverting its state changes. Separately completed approvals remain separate transactions; a failed redemption does not automatically remove authority granted by an earlier approval.