> For the complete documentation index, see [llms.txt](https://docs.kiln.fi/v1/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.kiln.fi/v1/kiln-products/dashboard/staking/ethereum-eth/convert-skimming-validators-to-compounding-validators.md).

# Convert skimming validators to compounding validators

A new consolidation feature will let you convert skimming validators to compounding validators and merge them into target compounding validators. These consolidation requests are sent from the execution layer to a special smart contract with fee mechanisms to prevent **DDoS** attacks. To consolidate validators, you must control the **withdrawal credentials** of the source validators, and only compounding validators can be targets. There is one exception: when converting a single skimming validator to a compounding validator, you can send a consolidation request using the same validator as both source and target.

## Enable compounding

You can enable compounding for any of your skimming validators through a consolidation request that uses the same validator as both source and target.

When connected to Kiln Dashboard, navigate to the **Ethereum → Reporting** page of your account. By hovering over an active Ethereum skimming validator, you’ll see the **Enable Compounding** option appear.

<figure><img src="/files/XzRzLWTLt7tNEnon7TkX" alt=""><figcaption><p>Enable compounding from reporting page</p></figcaption></figure>

From the Enable Compounding page, select a skimming validator to enable compounding. To finalize, connect your wallet holding the withdrawal key and click **Enable compounding** to initiate the consolidation operation. Once the transaction is signed and broadcast, it will enter the consolidation on‑chain queue for execution by the consensus layer.

<figure><img src="/files/LLBVNk4fAbSJnQesLORt" alt=""><figcaption></figcaption></figure>

## Consolidate validators

In Kiln Dashboard, you will be able to merge source skimming or compounding validators into target compounding validators.

After connecting to Kiln Dashboard, go to your account’s **Ethereum → Reporting** page. Click **Consolidate** to access the Consolidation page.

Connect the wallet holding the withdrawal key for the source validators you want to consolidate. Once connected, all validators associated with this withdrawal key will be displayed. Select your source validator and target validator. You can choose any active compounding validator from your account that Kiln operates as the target.‍

Click **Consolidate** to initiate the consolidation operations. Once the transaction is signed and broadcasted, they will enter the consolidation on‑chain queue for execution by the consensus layer.

<figure><img src="/files/dCJ95ClWMbCuJOYvmChi" alt=""><figcaption><p>Consolidation page</p></figcaption></figure>


---

# 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://docs.kiln.fi/v1/kiln-products/dashboard/staking/ethereum-eth/convert-skimming-validators-to-compounding-validators.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.
