> For the complete documentation index, see [llms.txt](https://docs.heroglyphs.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.heroglyphs.com/seba/rocket-pool.md).

# Rocket Pool

Seba now supports Rocket Pool (RP) validators, allowing RP node operators to register their **Minipools** directly in Seba!

### What are Minipools?

Minipools are Rocket Pool's version of a validator where the node operator does ***not*** need to contribute the full 32 ETH stake normally required to have a validator. Instead, users are able to stake a partial amount (either 8 ETH or 16 ETH), and the remaining ETH is provided by Rocket Pool users through the purchase of their **rETH** liquid staking token.

Rocket Pool supports two types of Minipools:

* 8 ETH Minipool
* 16 ETH Minipool

### How Minipools Work in Seba

#### Attestation Points

RP validators registered in Seba earn attestation points <mark style="color:green;">**proportional**</mark> <mark style="color:green;">**to their personal stake**</mark>:

* 8 ETH Minipool: earns 25% of a normal validator’s attestation points

  *(32 /* *8 = ¼ = 25%)*
* 16 ETH Minipool: earns 50% of normal attestation points (*32 / 16 = ½ = 50%)*

#### TVL Contribution

Thinking about how Rocket Pool works, even though the Node Operator only Stakes <mark style="color:green;">8 or 16 ETH</mark> within Rocket Pool, **the full 32 ETH validator weight still counts towards Seba's TVL.** &#x20;

### Execution Rewards&#x20;

Normal validator within the Seba app must points their fee recipient to the Seba contract address. Rocket Pool validators cannot do this unless they opt into specific RP punishment modes which of course is not optimal. This led to the creation of a dedicated '**Back-Paying**' contract to handle this situation ([0xDF...E9E5](https://etherscan.io/address/0xDF5fff71608095e6eD34e582C1B7eBD0c5A9E9E5)).


---

# 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.heroglyphs.com/seba/rocket-pool.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.