Signed a cBridge Withdrawal? Find the Missing Payout Step
A signed cBridge withdrawal is only a request; tokens arrive after authorization and a successful release transaction, which may be delayed. If your wallet has no payout, identify the withdrawal’s current stage in Liquidity History before deciding whether to wait, confirm, or investigate a failed transaction.
Three milestones separate your signature from a payout
The initial signature records your request to remove liquidity; it does not send tokens to your wallet. The request must then be authorized by the State Guardian Network (SGN), and the release must complete on the withdrawal chain. Each milestone has different evidence, so a signature in your wallet is not proof that a payout transaction occurred.
For a standard signing wallet, cBridge security is relevant at this boundary: your first signature records intent, while a later wallet transaction can authorize the release of tokens. The cBridge LP Guide’s liquidity removal flow describes the initial signing, subsequent confirmation, and tracking in Liquidity History.
Open the existing withdrawal entry using the wallet that submitted it. Note the withdrawal chain, intended recipient, and displayed stage. Those details identify where the tokens should arrive and help you match any later transaction to the right request.
Use the withdrawal stage to choose your next action
The displayed stage tells you whether the next step belongs to the authorization process, your wallet, or the chain:
- Awaiting authorization: the request is not ready for release. Wait for it to become ready; signing the same request again does not complete authorization.
- Ready for release: authorization is complete, but the payout still needs the required wallet transaction. Review the transaction details and submit it from the original wallet.
- Submitted: a release transaction has been sent. Its receipt shows whether it is still pending or completed successfully, or reverted.
- Delayed or failed: the entry records an execution delay or an unsuccessful attempt. Follow the guidance shown for that state before deciding on another request.
These are different outcomes, not interchangeable signs of a missing wallet balance. A withdrawal that is merely awaiting authorization needs time; one ready for release needs a transaction; a submitted one needs its receipt reviewed. A recorded delay is not proof of failure and, by itself, is no reason to create a duplicate withdrawal.
Confirm the release transaction and its gas
When Liquidity History shows that release is ready, inspect the proposed transaction in your wallet before approving it. The wallet submitting that release needs enough of the withdrawal chain’s native token to pay gas. Without sufficient gas, the transaction may not be submitted or may fail, even though the withdrawal request was authorized.
If you already submitted the release, find its transaction in the wallet or on the withdrawal chain and inspect the receipt. A pending transaction has not finished executing. A successful receipt confirms the transaction ran, while a reverted receipt means that attempt did not complete the payout. Use the request’s current status and the receipt together before resubmitting anything; an absent balance alone cannot tell you whether a transaction is pending, reverted, or delayed.
Some large withdrawals can enter delayed execution. If Liquidity History records a delay, use the stated status and guidance to determine when or whether another action is needed. The Celer Inter-chain Messaging Framework and cBridge liquidity pools support cross-chain operations, but the practical evidence for your withdrawal is its recorded stage and the release transaction on the specified chain.
Keep other withdrawal workflows separate
A transfer refund concerns a different flow from removing liquidity, so refund instructions do not diagnose this withdrawal. Contract wallets also use a separate withdrawal workflow; the cBridge Smart Contract as LP documentation describes its distinct readiness, failure, and delayed-execution states. This article’s wallet steps apply to an individual liquidity provider using a standard signing wallet, not to manual contract calls.
After a successful release, confirm the transaction on the withdrawal chain and check the intended recipient’s token balance there. The task is complete when that recipient has received the tokens on the specified chain.
Does your existing Liquidity History entry say “awaiting authorization,” “ready for release,” “submitted,” or “delayed/failed”? That answer determines whether you should wait, submit the release with gas, inspect a receipt, or follow the recorded state guidance before making another request.
Comments
Post a Comment