> For the complete documentation index, see [llms.txt](https://staderlabs.gitbook.io/ethereum/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://staderlabs.gitbook.io/ethereum/node-operator/permissionless-node-operator/ethx-rewards-for-permissionless-node-operators/claim-el-and-sd-rewards.md).

# Claim EL and SD rewards

### **Check rewards status**

Check the EL and SD rewards for you node using the node status command:  **`~/bin/stader-cli node status`**

* SD rewards will be visible on the CLI after the first Merkle tree is created for your node. The Merkle tree is created every 28 days.
* If you have Opted In for Socializing Pool, then EL rewards will be visible after the first Merkle tree is created for your node. The Merkle tree is created every 28 days.
* If you have Opted out of Socializing Pool, then fee recipient rewards will be visible depends on the blocks you have proposed. This is not predictable and completely randomized. A validator may propose a block once in \~2 months
* Your EL and SD rewards will be claimed in the Operator Reward Address. The Opt-In and Opt-Out of socializing pool will have a cool-off period of 56 days. i.e you will have to wait for 56 days to Opt-Out of the Socializing pool once you Opt-In and vice versa.&#x20;

### **If you have opted IN for Socializing pool**

**Claim your EL and SD rewards together by following the belwo mentioned steps**

* **Step 1**: Check your SD and EL rewards unclaimed cycles using the command: **`~/bin/stader-cli node claim-sp-rewards`**
* **Step 2:** Please specify the cycle numbers for which you want to claim the rewards.
* **Step 3:** Please confirm the entered cycle numbers, and your rewards will be claimed to your operator reward address.

### **If you have opted OUT of Socializing pool**

**Claim your EL and SD rewards separately by following the below mentioned steps**

**Claim SD rewards**

* **Step 1**: Check your SD rewards unclaimed cycles using the command: **`~/bin/stader-cli node claim-sp-rewards`**
* **Step 2:** Please specify the cycle numbers for which you want to claim the rewards.
* **Step 3:** Please confirm the entered cycle numbers, and your rewards will be claimed to your operator reward address.

**Claim EL rewards (Fee Recipient)**

{% hint style="success" %}
**Stader node helps you save gas cost**\
Stader node has a default feature that transfers the unclaimed EL(Fee Recipient) rewards for your node to a claim vault when it reaches 0.15 ETH. This movement of rewards is done once a month. This allows node operators to claim the EL(Fee Recipient) rewards for their node in a single transaction from the claim vault to their operator reward address.
{% endhint %}

**To claim EL(Fee Recipient) rewards without waiting for Stader to transfer them to the claim vault, follow these steps:**

* **Step 1:** Check EL(Fee Recipient) rewards accrued for your node using the node status command: `~/bin/stader-cli node status`
* **Step 2:** Send your  EL(Fee Recipient) rewards to the Claim vault using the command: `~/bin/stader-cli node send-el-rewards`
* **Step 3:** Claim your EL(Fee Recipient) rewards from the claim vault using the following command. `~/bin/stader-cli node claim-rewards`

**To claim EL(Fee Recipient) rewards after Stader has transferred them to the claim vault, follow these steps:**

* **Step 1**: Claim your EL(Fee Recipient) rewards from the claim vault using the following command. `~/bin/stader-cli node claim-rewards`

### &#x20;<a href="#rewards-and-checkpoints" id="rewards-and-checkpoints"></a>

### Rewards cycle and Merkle tree[​](https://docs.rocketpool.net/guides/node/rewards.html#rewards-and-checkpoints) for Socializing pools <a href="#rewards-and-checkpoints" id="rewards-and-checkpoints"></a>

On the Stader network, a merkle tree is created on regular intervals for the Stader node Socializing pool rewards. Currently, a new cycle occurs every 28 days. During each reward cycle, Stader node generates a merkle tree representing the state of node operators on the Stader network. This tree determines the SD and Socializing pool ETH rewards for each node operator during that specific cycle.

After a merkle tree is created, the ETHx smart contracts transfer SD tokens and the entire ETH balance from the socializing pool to the Stader vault. Node operators can then check the number of SD and ETH rewards they earned for a particular cycle and claim them. Each reward cycle is independent, meaning the rewards earned in one interval don't affect the earnings in subsequent cycles.&#x20;

Node operators have the flexibility to claim rewards for one cycle, multiple cycles, or all at once. Node operators can accumulate rewards for as long as they want without a fixed time interval to claim them. The rewards will always be available and provide the same amount of SD and ETH regardless of when they are claimed.

###

###

### &#x20;<a href="#rewards-and-checkpoints" id="rewards-and-checkpoints"></a>


---

# 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://staderlabs.gitbook.io/ethereum/node-operator/permissionless-node-operator/ethx-rewards-for-permissionless-node-operators/claim-el-and-sd-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.
