> For the complete documentation index, see [llms.txt](https://graphdex-1.gitbook.io/graphdex-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://graphdex-1.gitbook.io/graphdex-docs/earn-staking/claiming-and-withdrawals.md).

# Claiming and Withdrawals

**Moving rewards or staked funds out of Earn — what to check at every step.**

Earn exposes withdrawal flows for staking balances and closed plans. The terminal includes a staking withdraw-history page and withdraw-staked prompts. Exact availability depends on your account state and the selected plan — always read the live prompts before approving anything.

{% hint style="success" %}
**One prompt at a time**

Withdrawals look quick from the outside; under the hood they touch the wallet, the plan state, and the network. Read each prompt before signing.
{% endhint %}

## Withdraw Staked Funds

Before submitting a withdrawal from Earn, verify:

* **Selected wallet** — the source plan and the destination context.
* **Available balance** — what's actually withdrawable right now.
* **Amount received** — net of fees.
* **Withdrawal fee** — shown by the prompt.
* **Destination wallet** — where funds will land.
* **Processing status** — pending, completed, or errored from a prior attempt.

Submit only after wallet, asset, and amount are all confirmed against your intent.

## Withdrawal History

The history view records every withdrawal attempt:

* **Date** — when initiated.
* **Wallet** — source or destination.
* **Amount** — what was moved.
* **Status** — completed, error, in-processing.
* **Transaction hash** — the on-chain receipt when available.

When a transaction hash is exposed, **use it to verify the record in a block explorer**. The on-chain log is the canonical answer; the terminal view is a presentation layer.

## Claiming Rewards

If a **claim action** is available for your account, review the claim prompt before approving:

* The asset being claimed.
* The amount claimable.
* The wallet receiving the claim.
* Any fees shown.

**Important separation:** claimable balances, staking rewards, and staking withdrawals are **separate from referral claim flows**. Do not treat a referral claim button as a staking reward claim unless the terminal explicitly shows that connection.

## Processing Time

The Earn product page mentions **auto-refund within 24 hours**. In practice, processing depends on:

* Account state.
* Network conditions.
* The terminal's current flow.

If a withdrawal isn't completed immediately:

1. Check **withdraw history** for the pending record.
2. Confirm the status before retrying.
3. **Avoid duplicate submissions** — they can compound fees or create reconciliation issues.

## More to Explore

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-cover data-type="image">Cover image</th></tr></thead><tbody><tr><td><a href="/pages/tmKkLk8NTcZZolNGWdIh"><strong>Staking</strong></a></td><td>The deposit side of the same flow.</td><td><a href="/files/BWULSHt4tqY255s7X9t1">/files/BWULSHt4tqY255s7X9t1</a></td></tr><tr><td><a href="/pages/LWnqmKdIJWwn34bHYZeL"><strong>Rewards</strong></a></td><td>What rewards accrue before they're claimed.</td><td><a href="/files/BWULSHt4tqY255s7X9t1">/files/BWULSHt4tqY255s7X9t1</a></td></tr><tr><td><a href="/pages/rUNLtcMq4Cs8IjCNa3Aw"><strong>Wallet Transactions</strong></a></td><td>Where the withdrawal lands and how to audit it.</td><td><a href="/files/BWULSHt4tqY255s7X9t1">/files/BWULSHt4tqY255s7X9t1</a></td></tr></tbody></table>

{% hint style="info" %}
Always cross-check withdrawal results in [Wallet Transactions](/graphdex-docs/wallet/transactions.md) and the relevant block explorer — terminal status is convenience; the chain is truth.
{% endhint %}

## FAQs

<details>

<summary>How long does a withdrawal take?</summary>

The Earn product page references auto-refund up to 24 hours. Real-world timing also depends on network state and account conditions. Check withdraw history before assuming a delay is a failure.

</details>

<details>

<summary>What if a withdrawal stays in `in-processing` for hours?</summary>

Don't re-submit. Open the row, copy the transaction hash if present, verify in a block explorer. Contact support only after the history view confirms the request didn't progress on-chain.

</details>

<details>

<summary>Why is my withdrawal showing an error?</summary>

Common causes: insufficient gas, account state mismatch (sign-in incomplete), or wallet-network mismatch. The error message in the history row usually points at the cause.

</details>

<details>

<summary>Are claim and withdrawal the same flow?</summary>

No. Claiming rewards moves accrued earnings into a claimable balance; withdrawing moves funds from claimable balance to the destination wallet. Check the prompt label carefully.

</details>

<details>

<summary>Can I claim referral rewards through this flow?</summary>

No — referral claims live in \[Referral Rewards]\(../referrals/referral-rewards.md). The Earn claim flow only covers staking-related balances.

</details>


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://graphdex-1.gitbook.io/graphdex-docs/earn-staking/claiming-and-withdrawals.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.