# A Validator's Lifecycle

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

The controller of a Staking Pool can choose any set of Node Operators to work with.

* Staking Pools give an **allowance** to the Node Operators.&#x20;

{% hint style="info" %}
**Allowance** represents the maximum number of validators to be created.
{% endhint %}

* Node Operators propose a validator with specific details.
* Every proposal requires 1 ETH from Operator, **which will be reimbursed upon activation.**

{% hint style="info" %}
Pool Maintenance Fee, Operator Fee, and validator period is set on proposal.&#x20;

These parameters can not be changed afterwards.
{% endhint %}

* Oracle approves these proposals.
* Node Operators move 32 ETH from the staking pool to the approved validator.
* Validators are exited within the validator period.
* Fees are distributed after the validator withdrawal. However, with partial claiming

{% hint style="success" %} <mark style="color:green;">Staking Pool can change the allowance at any given point.</mark>&#x20;

<mark style="color:green;">As old validators are exited, their stake is redistributed as per the allowance.</mark>
{% endhint %}


---

# Agent Instructions: 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:

```
GET https://docs.geode.fi/operator-marketplace/a-validators-lifecycle.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.