> For the complete documentation index, see [llms.txt](https://guide.dem.exchange/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://guide.dem.exchange/earn/liquidity-pools/liquidity-pools/walkthroughs/claiming-rewards.md).

# Claiming Rewards

Kaching! 🤑

## Introduction

This guide provides instructions on claiming rewards as a liquidity provider on our platform.

### **For LPs who did not commit LP tokens**

Fees earned from maker rebates are automatically directed to liquidity pools proportionally. As such, there is no need for liquidity providers to manually claim these fees.

### **For LPs who committed LP tokens**

Only liquidity rewards earned from committing LP tokens will require a claim transaction. Rewards earned from LP tokens can be claimed at any time, but each claim costs 30 SWTH. 

Note that claims are also automatically done at the end of a reward period and when unlocking or withdrawing your LP tokens!

## Guide

**Step 1:** Navigate to the '[Pools](https://app.dem.exchange/pools/)' page and select '**Your Pools**' from the sidebar menu.

<figure><img src="https://3548599389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MO-XZjWplLUJPNs07G8%2Fuploads%2F14Si3PsuihznQrmdL60t%2F2023-06-22%2012.57.31.jpg?alt=media&amp;token=947feb97-9b1d-4848-bf2c-092279af4fb0" alt=""><figcaption></figcaption></figure>

**Step 2:** The page displays all the pools you have added and committed liquidity to.

<figure><img src="https://3548599389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MO-XZjWplLUJPNs07G8%2Fuploads%2Fn24YsKluFIyMzK1MVH9j%2Fimage.png?alt=media&amp;token=27adba00-20b7-4747-b7d8-62f71628728d" alt=""><figcaption></figcaption></figure>

In order to claim rewards for a particular LP, locate the corresponding token and click on the "Claim" button adjacent to it.&#x20;

{% hint style="warning" %}
Note that a network fee of 30 SWTH per liquidity pool is required for claiming rewards. Make sure that your rewards are more than this!
{% endhint %}

Alternatively, if you wish to claim all your rewards simultaneously, simply click on the "Claim All" button located at the top, which will display the following dialog:

<figure><img src="https://3548599389-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2F-MO-XZjWplLUJPNs07G8%2Fuploads%2FXJoj16U3CRXVwUVAVomP%2Fimage.png?alt=media&amp;token=91c3be8e-4368-4c77-8b1e-a36725e8018e" alt="" width="375"><figcaption></figcaption></figure>

Note also that rewards are distributed in a plethora of tokens due to earnings from Carbon block rewards, you can view the full list of tokens for distribution on CarbonScan [here](https://scan.carbon.network/dashboard?net=main).&#x20;

**Step 3:** Click on Claim to confirm your transaction.&#x20;

{% hint style="success" %}
Congratulations! Your claimed rewards have been sent to your wallet.
{% endhint %}


---

# 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://guide.dem.exchange/earn/liquidity-pools/liquidity-pools/walkthroughs/claiming-rewards.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.