# Validation Nodes

Validation Nodes are the backbone of the Vola partnerchain. Validators are responsible for producing new blocks and finalizing them, ensuring that every transaction, storage proof, and network event is permanently and immutably recorded on chain.

Running a Validation Node is one of the most direct ways to contribute to the security and stability of Vola Network.

**If you would like to dive straight into Validator setup:**

{% content-ref url="/pages/URwHYJTiJoJFY4O4OZ5n" %}
[Setting Up a Validation Node](/docs/vola-node-economy/vola-nodes-overview/validation-nodes/setting-up-a-validation-node.md)
{% endcontent-ref %}

{% hint style="warning" icon="cloud-question" %}

#### **Validator Node Staking Requirement**

Running a Validation Node requires a stake of 50,000 $VOLA.

This threshold is intentionally set high to ensure only operators with serious infrastructure commitments secure the chain. The Vola Faucet does not distribute enough test $VOLA to meet this requirement.

If you are interested in running a Validation Node during testnet, please reach out to the Nuvola team directly via [Discord →](https://discord.gg/qnMSwT3Pvx)
{% endhint %}

#### What Validators Do

<details>

<summary><strong>Block Production</strong> </summary>

Validators take turns producing new blocks using the Aura consensus algorithm. Every active validator in the pool gets to author blocks in each era, as long as they remain online and produce blocks within the expected time window.

</details>

<details>

<summary><strong>Block Finality</strong></summary>

Once blocks are produced, the validators need to finalize them, confirming they are irreversible and agreed upon by the active validator nodes.

</details>

<details>

<summary><strong>Proof Verification</strong> </summary>

Validators verify the integrity of storage proofs, OAuth tokens, and file ownership records submitted to the chain, maintaining trust across the entire network.

</details>

<details>

<summary><strong>Era-Based Selection</strong></summary>

At the start of each era, the required number of validators are selected from the active staking pool. This selection repeats every era, ensuring consistent and fair participation.

</details>

#### How Validation Works

Vola uses two consensus algorithms that work together:

<details>

<summary><strong>Aura - Block Production</strong></summary>

Aura uses a round-robin algorithm to assign block authorship slots to validators from the active pool. As long as a validator is online and produces blocks within the optimal time window, they will author blocks in every era they are active. Missing your slot means missing that era's block production rewards.

</details>

<details>

<summary><strong>GRANDPA - Block Finality</strong></summary>

GRANDPA runs alongside Aura to finalize blocks, confirming that the blocks are valid and can never be reverted. Once a block is finalized, every transaction and proof recorded in it is permanently settled on chain.

</details>

#### Staking Requirements

To become a validator on Vola Network, you must stake between 50,000 and 100,000 $VOLA.

<table><thead><tr><th width="354">Parameter</th><th width="390.6666259765625">Details</th></tr></thead><tbody><tr><td><strong>Minimum Stake</strong></td><td>50,000 $VOLA</td></tr><tr><td><strong>Maximum Stake</strong></td><td>100,000 $VOLA</td></tr><tr><td><strong>Selection Method</strong></td><td>Round-robin per era</td></tr><tr><td><strong>Reward Rate</strong></td><td>~5% APY</td></tr></tbody></table>

{% hint style="warning" icon="cloud-xmark" %}
**No delegation to validators.**\
Vola's validator system is self stake only, validators bond their own VOLA and there is no nomination or delegation of stake to validators. This is distinct from Storage Node delegation, which operates separately.
{% endhint %}

{% hint style="info" icon="key" %}
**How selection works.**\
Once your stake requirement is met, your node becomes eligible for selection from the next era onwards. The network selects the required number of validators from the active pool each era using a round-robin approach.
{% endhint %}

### Validator Rewards

Validators earn from two sources:

{% stepper %}
{% step %}

#### **Transaction Fees**&#x20;

Every block a validator authors contains transactions. The fees paid for those transactions go to the validator who produced that block. The more activity on the network, the more fee revenue validators earn.
{% endstep %}

{% step %}

#### **Staking Rewards**&#x20;

In addition to transaction fees, validators earn staking rewards based on the total staked amount relative to the circulating supply.

Validator staking rewards formula is being finalized.

{% hint style="info" %}
For validators, staking rewards apply with a maximum stake cap, meaning staking beyond the cap of 100,000 $VOLA does not increase staking rewards further.&#x20;
{% endhint %}
{% endstep %}
{% endstepper %}

{% hint style="warning" %}
**Stay online.**\
Validators that go offline or fail to produce blocks in their assigned slot miss out on rewards for that era. Consistent uptime is key.
{% endhint %}

#### Hardware Requirements

| Component        | Minimum Requirement (Recommended) |
| ---------------- | --------------------------------- |
| **RAM**          | 4GB (8GB)                         |
| **CPU**          | 2 Cores (4 Cores)                 |
| **Storage**      | 20 GBs (50+ GBs)                  |
| **OS**           | Linux (recommended)               |
| **Dependencies** | Docker, Docker Compose            |

{% hint style="info" %}
These requirements apply to the testnet phase. Requirements may evolve as the network transitions to mainnet.
{% endhint %}

### Setting Up a Validation Node

Now that you know all about validation nodes, lets jump straight into setting up your Validation node.

{% content-ref url="/pages/URwHYJTiJoJFY4O4OZ5n" %}
[Setting Up a Validation Node](/docs/vola-node-economy/vola-nodes-overview/validation-nodes/setting-up-a-validation-node.md)
{% endcontent-ref %}

### What's Next?

<table data-view="cards"><thead><tr><th></th><th></th><th data-hidden data-card-target data-type="content-ref"></th></tr></thead><tbody><tr><td><strong>Node Staking Requirements</strong></td><td><em>Understand the staking formula and how your stake affects your position in the network.</em></td><td><a href="/pages/1Z3WvSS7obhDHKQnv0JD">/pages/1Z3WvSS7obhDHKQnv0JD</a></td></tr><tr><td><strong>Node Rewards</strong></td><td><em>How validator rewards are calculated and when they are distributed.</em></td><td><a href="/pages/3Xr3L81JEkDpfquNCjaW">/pages/3Xr3L81JEkDpfquNCjaW</a></td></tr><tr><td><strong>Vola Smart Nodes (Storage)</strong></td><td><em>Looking to earn storage fees on top of staking rewards? Explore running a Vola Smart Node.</em></td><td><a href="/pages/GsrLAfwWLWaMNhVQ2sph">/pages/GsrLAfwWLWaMNhVQ2sph</a></td></tr></tbody></table>


---

# 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://wp.vola.network/docs/vola-node-economy/vola-nodes-overview/validation-nodes.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.