Astar
Astar releases staked ASTR through unlocking and withdrawal.
Last updated
Astar dApp staking returns committed ASTR to a transferable balance after unlocking and withdrawal, provided no other balance restriction remains. Unstaking alone removes the allocation to a dApp while leaving the tokens locked. Before exiting, claim outstanding rewards and ensure you have transferable ASTR for fees. Then remove any active stake, initiate unlocking, wait until the request becomes withdrawable, and complete the withdrawal transaction. The Astar Portal can combine parts of this process.
The useful distinction is between a reduced stake, a pending unlocking request, and an amount available to withdraw. Each permits a different next action. A wallet’s total ASTR balance doesn’t establish how much you can send.
Keep supporting a dApp or release the funds
Changing the dApp that you support and making ASTR transferable require different operations. Unstaked tokens can remain locked for another allocation. That makes unstaking useful when you want to keep participating without committing to the same project.
An exit requires unlocking. At the protocol level, actively staked tokens must first become unstaked before they can enter unlocking. The Portal’s Unstake flow can carry out the exit sequence through its interface. Read the transaction summary before signing. After the transaction succeeds, check that an unlocking request exists to confirm that the release process has started. A lower staked balance alone doesn’t establish that.
Prepare reward claims and a transferable fee balance
Outstanding reward claims and transaction fees can prevent an exit before an unlocking request exists. Confirm the connected account and inspect its staking balances before signing. The account holding the stake must authorize the relevant operations.
Reward claims before unstaking
The protocol requires outstanding rewards to be claimed before unstaking. A reward claim can also present a choice about what happens to the payout. That choice matters when the intention is to reduce the amount committed.
Receive rewards as transferable tokens
If you decline the Portal’s restaking option, you receive the claimed rewards as transferable tokens. Claiming rewards doesn’t withdraw the original stake; the principal keeps its existing staking status.
Restake the payout
Accepting restaking allocates the rewards across active stakes. This increases the amount committed to staking, so include the payout when reviewing how much remains to exit.
Funds for transaction fees
ASTR locked in dApp staking cannot pay transaction fees. A substantial total balance can therefore coexist with insufficient funds for a claim or withdrawal. Use the transferable balance and the proposed transaction’s fee estimate to assess affordability. Don’t assume that the pending withdrawal can fund its own transaction.
Follow the exit through its recorded states
For a time-sensitive transfer, a confirmed unlocking request establishes a pending release rather than immediate spending capacity. An interface can combine compatible operations, so these stages don’t necessarily require separate transactions.
| Exit stage | Condition that can prevent progress |
|---|---|
| Prepare the account and reward claims | Unclaimed rewards or insufficient transferable ASTR for fees can block the required operation. |
| Remove the active stake allocation | A reduced stake alone leaves tokens locked; it doesn’t establish an unlocking request. |
| Start unlocking the unstaked amount | The request must succeed before the amount enters its unlocking period. |
| Wait for the request to become withdrawable | A pending chunk remains unavailable for withdrawal until its release condition is met. |
| Withdraw the matured amount | Elapsed waiting time alone doesn’t complete withdrawal; the transaction must succeed. |
Suppose the unlocking request exists, but an attempted withdrawal fails because its release block hasn’t arrived. The amount stays pending. Repeating the same withdrawal doesn’t advance that block or shorten the wait. Compare the request’s release block with finalized chain progress before trying again.
Once the request becomes eligible, a successful withdrawal transaction provides completion evidence. Check its chain result independently of the Portal notification, then reconcile the remaining unlocking entries and transferable balance. If the transaction failed, its error determines what must change before another attempt.
When does an unlocking request become withdrawable?
An unlocking request becomes withdrawable when the chain reaches the release condition recorded for that request. An unlocking chunk records an amount together with the block at which it becomes eligible for withdrawal. Treat a displayed calendar countdown as an estimate of chain progress, rather than a promised appointment.
Block production affects elapsed time. The configured unlocking period and the request’s recorded release block determine eligibility, so an old duration from another staking version isn’t a reliable deadline. Tokens that were already locked without an active stake still require unlocking; time spent sitting unstaked doesn’t substitute for that process.
Partial exits can remove more stake than requested
A partial unstake can remove the entire allocation to a dApp when the remainder would fall below the minimum stake requirement. The minimum applies to the remaining allocation, so requesting a partial unstake doesn’t necessarily preserve a small active stake.
The minimum locked balance is a separate constraint. Unlocking that would leave the account below this requirement can trigger a full unlock under the protocol’s rules. Review the proposed amount and the remaining commitments together. Neither minimum is a permanent figure to assume from an older transaction.
After a partial exit, inspect both the surviving dApp allocations and pending unlocking amounts. They describe different commitments.
Why is ASTR still unavailable after withdrawal?
ASTR can remain unavailable after a successful staking withdrawal when another balance restriction still applies, such as a vesting lock. Tokens can carry overlapping restrictions. Removing the dApp staking restriction doesn’t remove an unrelated lock, so the transferable increase can differ from the amount released by staking.
Withdrawing the principal doesn’t add it to the account’s total balance again. The committed tokens remained associated with the account throughout staking. Changes in total balance can include claimed rewards and transaction fees, while the withdrawal chiefly changes the restriction on using the principal.
An outdated Portal display can obscure the result. Confirm the account and network, then inspect the transaction’s chain status. If the interface connection isn’t synchronized, refreshing or changing its network endpoint can resolve the display problem. A successful signature alone isn’t proof that the chain executed the withdrawal.
Re-locking keeps ASTR committed to staking
Re-locking returns unlocking tokens to the locked staking balance before the release process finishes. It cancels the intended exit for those funds. A locked balance still needs a dApp allocation to earn staking rewards; re-locking alone doesn’t establish one.
For continued participation, re-locking retains funds within the staking system. For a transfer, the relevant endpoint is a successful withdrawal and a sufficient transferable balance.
Astar - your questions answered
Does unstaking reduce rewards for the current era?
Unstaking removes the affected amount from the current era’s reward calculation. It reduces the stake for both the current and next era where that stake exists. Previously earned, claimable rewards are separate from this change. Funds undergoing unlocking don’t earn dApp staking rewards.
Will a new staking period automatically release my ASTR?
A new staking period resets dApp allocations while leaving the tokens locked. An empty allocation after the reset therefore doesn’t mean that a withdrawal is pending. Reaching a transferable balance still requires an unlocking request, its release condition, and withdrawal.
Why would the protocol reject another unlocking request?
An account can reach the limit on simultaneous unlocking chunks. Each outstanding request occupies an entry. Withdrawing eligible chunks frees capacity; when none are eligible, their release conditions must be met first. A chunk-limit error calls for checking existing requests rather than repeatedly submitting another one.
Can a faster transaction setting shorten the unlocking period?
A faster transaction setting doesn’t shorten the protocol’s unlocking requirement. Transaction inclusion and the subsequent release condition are separate. An interface’s speed option concerns submitting the transaction; the resulting chunk must still reach its recorded withdrawal eligibility.
Do I need the dApp owner’s approval to withdraw my stake?
The dApp owner doesn’t approve a staker’s ordinary exit. The account controlling the stake authorizes unstaking, unlocking, and withdrawal under the protocol’s conditions. Those conditions include reward claims, available transaction fees, and withdrawal eligibility; supporting a dApp doesn’t hand its owner custody of the staked tokens.