Aura finance AURA redemption and rAURA claim settlement
Aura finance entered wind-down with an AURA redemption process that distributes treasury assets and mints rAURA claim tokens. The first stage opened on 13 May 2026. The schedule places the opening of rAURA claims on 10 May 2027, when stage 1 closes. Completing the initial redemption therefore leaves a separate claim to resolve later. The immediate task is to reconcile the AURA surrendered, the treasury tokens received and the rAURA credited. Those records distinguish a completed transaction from an approval, a pending request or an incomplete wallet display. The later claim requires its own settlement check.
AURA balances and rAURA balances require different actions
An AURA balance belongs to the initial redemption path, while an rAURA balance represents participation in the later distribution. Identify which token the account actually holds before selecting an action. A combined portfolio value cannot establish that distinction because it compresses different assets into one monetary estimate.
AURA held inside a locker also differs from AURA available in the wallet. Withdrawing that position and redeeming the resulting tokens are separate operations. Keep that prerequisite distinct from the treasury claim itself.
Read the redemption record before reconciling balances
The redemption record identifies the account, the amount burned and the payout quantities, providing a more precise basis for reconciliation than a success banner alone. The contract interface exposes a
Redeemed
event with those fields.
Authorization and execution
A token approval grants spending permission. It does not establish that redemption occurred. Where the transaction history contains separate approval and redemption entries, evaluate the redemption entry for the asset movements. Confusing these records can leave an account authorized without having received any distribution.
Amounts and receiving account
Read token quantities alongside their contract identities and destination account. A token symbol alone cannot distinguish unrelated contracts with the same label. Monetary valuations add another source of confusion because wallet software may lack a usable price for a claim token. The balance and the displayed valuation answer different questions.
Reconcile the first redemption before submitting another
Consider an account with available AURA that intends to complete stage 1. Before submission, the account needs the intended redemption contract, an eligible token balance and an open redemption window. Record the starting AURA and rAURA quantities so unrelated holdings do not obscure the change.
- If the AURA remains inside another position, resolve that withdrawal before treating it as available redemption input.
- If authorization is necessary, confirm the intended spender and amount before approving it.
- After submitting redemption, distinguish a pending transaction from a confirmed successful transaction before considering another request.
- For a successful redemption, compare the AURA burn and treasury transfers with the rAURA credit in the same transaction.
- If rAURA is missing only from the wallet display, inspect the account's token balance before attempting redemption again.
The transaction movements should match the balance changes attributable to that redemption. A successful transaction with an incomplete display requires reconciliation, rather than an automatic retry. An unsuccessful transaction requires a different next action: identify its failure condition and establish that the original redemption did not settle before submitting another request.
Retain the transaction identifier and resulting rAURA balance. Stage 1 completion leaves that later claim outstanding.
When does the rAURA claim stage begin?
The published opening date for rAURA claims is 10 May 2027. The sunset schedule closes stage 1 on 10 May 2027. That boundary changes which redemption token applies; holding unredeemed AURA is not equivalent to having completed the earlier conversion.
A calendar date establishes the scheduled transition. Actual claim completion still requires a successful distribution transaction. Avoid treating a countdown reaching zero as evidence that assets have reached an account.
Separate proportional entitlements from monetary value
A pro-rata distribution assigns a fraction of distributable assets using the eligible token amount and the applicable supply denominator. Its output consists of asset quantities. Those quantities and their market value are separate measurements.
The denominator determines the share
The wind-down design excluded treasury-held AURA, ecosystem allocations and unvested AURA from the redemption calculation. A headline total-supply figure therefore does not necessarily represent the eligible supply. Calculating a share against the wrong denominator changes the result even when the account balance is correct.
Received assets determine settlement
Reconcile each distributed token in its own units. Adding different token quantities together produces no meaningful payout total. A monetary estimate requires a valuation for each asset at a stated time, while a settlement check asks whether the expected token transfers occurred.
Pending transactions and failed execution
A pending redemption has no final settlement result. Repeatedly submitting requests during that state makes it harder to identify which transaction eventually executed, especially if the wallet replaces an earlier request.
A reverted transaction does not complete its intended token transfers. Diagnose the reported failure before retrying; an unavailable balance and a closed redemption window require different responses. Adding spending permission cannot reopen a closed stage.
Once a transaction succeeds, investigate discrepancies against that transaction's transfers. A later account balance may also include unrelated activity, so it cannot always reconstruct the redemption by itself.
The backing reserved for the later distribution
The rAURA allocation combines unclaimed stage 1 treasury assets with 10% of the designated 80/20 BAL/WETH Balancer pool tokens, or BPT. The separate auraBAL allocation receives the remaining 90% of that BPT backing. These percentages divide the designated backing; they do not describe returns on a holder's purchase price.
The wind-down design tied this later distribution to unwinding the veBAL position. That explains the separation between immediate treasury redemption and the delayed backing claim. The unclaimed-treasury component also depends on participation in the earlier stage, so an initial redemption cannot establish its final quantity.
Receiving a distribution and selling the received assets
Claim settlement ends with receipt of the assets that the distribution delivers. Converting those assets into another token or currency is a separate transaction with its own execution conditions.
A market sale, where available, exchanges a token at the executable market price. Protocol redemption follows the distribution's eligibility and allocation rules. Compare those distinct outcomes using actual asset quantities and executable terms; a successful redemption does not establish what a subsequent sale will return.
Aura finance questions worth asking
Does a zero displayed rAURA value mean the claim balance is empty?
A zero monetary valuation does not establish a zero rAURA balance. Wallet software may show an amount without assigning it a usable market price. The token quantity identifies the holding, while a price estimate attempts to value it. A blank valuation alone does not prove that redemption failed.
Which transaction details should I retain for a later rAURA claim?
Retain the redemption transaction identifier, account address, token quantities and resulting rAURA balance. These records connect the original redemption with the claim tokens that the account received. A screenshot of a portfolio total omits the individual transfers and can become misleading after later account activity.
Is transferring AURA directly to a contract the same as redeeming it?
A direct token transfer is a different operation from calling the redemption function. The redemption interface accepts an amount through its redeem operation and returns payout quantities. Sending tokens to a contract address does not, by itself, establish that this operation ran or that the account received rAURA.
Why might a later wallet balance differ from the redemption receipt?
Later transfers can change the account balance after redemption has settled. The receipt records movements within the redemption transaction, while the wallet balance reflects subsequent activity too. Compare the relevant transaction movements before attributing a difference to an incorrect payout or missing claim tokens.