# A Validator's Lifecycle

<figure><img src="https://2485428749-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2Fw9Axw7FT11SMG7vNQwDN%2Fuploads%2FYHlxRwIWwoach8qow56M%2Flifecycle.png?alt=media&#x26;token=5fa4f7bf-40d3-4a43-803e-8571879b6bf9" 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 %}