> 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/graduation.md).

# Graduation

Graduation is the key milestone for a validator in the Seba protocol. It signifies the shift from active participation to continuous reward collection.

A validator graduates after meeting <mark style="color:green;">two key conditions</mark>:

1. Completing the entire graduation period without violating fee address requirements and with strong attestation performance.
2. Include the validator ID as a ticker in a valid <mark style="color:yellow;">Heroglyphs</mark> block graffiti (e.g., #seba12345) after the validator's graduation period has ended and make sure the **execution reward of the block** goes to the Seba pool.

### Graduation Rewards

Graduation rewards come in the form of shares in the <mark style="color:green;">pybSeba</mark> Vault:

* The number of shares is determined by the validator’s total attestation rewards during the period, multiplied by any applicable boost factor (up to 3.0x).
* The calculation accounts for effective balance, meaning validators with more staked ETH earn proportionally more shares. However, missed attestations reduce the total, promoting optimal performance.

### Can a Validator ID Graduate multiple times?

Graduation occurs only once per validator ID. After graduating, a validator cannot gain more shares for that ID, but they can start a new validator and join again.


---

# 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/graduation.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.