Request a withdrawal

V3 withdrawals are self-service: there is no admin approval step and no fixed queue time. Every withdrawal goes through redeemWithQueue, which automatically picks the fastest path your balance and the vault's liquidity allow.

---

Steps

1. Go to stakexdc.com/xdc-liquid-staking.
2. Enter the amount of psXDC shares you want to redeem. The app shows you, in real time:
   • The XDC you will receive based on the current exchange rate.
   • Whether the withdrawal will settle instantly or enter the queue, based on the vault's liquid buffer.
3. Click Withdraw and confirm the transaction. Under the hood the app calls redeemWithQueue(shares, receiver).

---

What happens next

If the vault has enough buffer liquidity

The redemption settles in the same transaction. You receive XDC immediately. No queue entry is created, nothing else for you to do.

If buffer liquidity is constrained

Your psXDC shares are escrowed inside the vault and a request is added to the FIFO queue. The withdrawal does not have a fixed time. It is settled as the queue's dedicated budget (queueBackingBudget) is topped up — primarily from masternode resignation principal returning after the XDC Network's candidateWithdrawDelay (~35 days under normal block times), routed to the queue by the team. New deposits refill the instant buffer, not the queue. Your escrowed shares are paid at the exchange rate of the moment they are processed, so they keep earning while you wait.

You can monitor the queue at any time from the Overview page. When your request is processed, your XDC lands either directly in your wallet or in the vault's pendingQueuedAssets bucket. If it lands in pendingQueuedAssets (because the original payout failed for any reason), you collect it by calling claimQueuedAssets. The app exposes this as a Claim button on the queued withdrawal entry.

You can also cancel a queued request before it settles. The vault returns the escrowed psXDC shares to your wallet, and no XDC moves.

---

Why a queue exists at all

The vault keeps most of the XDC working in masternodes earning yield and holds only its unencumbered balance liquid for instant redemptions. When demand to withdraw exceeds that, the queue ensures that everyone is served in FIFO order from a ring-fenced budget without forcing the protocol to disrupt active validators (a request the budget cannot yet cover is passed over and retried, never cancelled).

The queue is preferred over the previous "request and wait for admin approval" model because:

• No admin signature is needed at any point.
• You can cancel at any time and get your shares back.
• Settlement is automatic: anyone can call processWithdrawalQueue to push the queue forward.

→ Withdrawals: Instant vs Queued → Smart Contract Reference