> 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/important-notes.md).
# Important Notes
### Strong Recommendation About Smoothing Pool
RP validators who opt into Seba are strongly advised NOT to opt into the Rocket Pool Smoothing Pool and should instead receive execution rewards via the RP distribution contract.
This is not enforced but highly recommended for two reasons:
#### 1. “Lucky Block” Risk
If a validator proposes a block with a large execution reward:
* The smoothing pool spreads the reward across many participants
* The validator loses direct access to the reward
* But Seba still expects their share of back-pay
This may result in the validator needing to pay more than they actually receive.
#### 2. Smoothing Pool Withdrawal Delay
* Smoothing pool rewards unlock every 28 days
* Seba requires back-pay within 15 days
This means validators using the smoothing pool may be forced to pay upfront out of pocket.
It is strongly advised to use the RP Distributor Contract instead of the RP Smoothing pool for these reasons. Please keep this in mind!
---
# 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/important-notes.md?ask=&goal=
```
`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.