# FAQ

Answers to the most common questions about Vola Network, node operations, staking, and the testnet. If your question isn't covered here, join the [Nuvola Discord](https://discord.gg/qnMSwT3Pvx) and ask the team directly.

#### Getting Started

<details>

<summary><strong>What is Vola Network?</strong></summary>

Vola Network is a decentralized cloud platform that unifies storage, compute, and identity into a single infrastructure layer.

It is built on a Substrate-based blockchain using the Polkadot SDK and anchored to Cardano for shared security.

Rather than storing files and running workloads on centralized servers owned by a single company, Vola distributes these functions across a global network of independent node operators; making cloud infrastructure more resilient, transparent, and censorship-resistant.

{% hint style="success" icon="cloud-check" %}
[**Nuvola Drive**](https://drive.nuvoladigital.io/) is the first application built on Vola.

Nuvola Drive is a user-facing cloud storage product that demonstrates what decentralized infrastructure can power in practice.
{% endhint %}

</details>

<details>

<summary><strong>What is $VOLA?</strong></summary>

$VOLA is the native token of Vola Network.

It serves three core functions:\
\- it is the payment currency for storage and compute services,\
\- it is the staking asset that node operators lock as collateral to participate in the network, &\
\- the governance token that holders will use to vote on protocol decisions.

With a total supply of 1 billion tokens and a 20-year emission schedule, $VOLA is designed for long-term, sustainable network participation rather than short-term speculation.

</details>

<details>

<summary><strong>How do I get test $VOLA?</strong></summary>

During the testnet, test $VOLA is available through the [Vola Faucet.](https://faucet.vola.network/)

The faucet distributes a limited amount per request, this limit exists to prevent the network from being spammed with storage requests that would consume available node capacity.

If you need additional test $VOLA for running a validator node, reach out to the team via [Discord.](https://discord.gg/qnMSwT3Pvx)

</details>

<details>

<summary><strong>Do I need blockchain experience to run a node?</strong></summary>

Not necessarily. Storage Nodes and RPC Nodes are designed to be accessible to anyone with reliable hardware and a basic comfort level with command-line tools and Docker.

You do not need to understand blockchain consensus mechanisms or write any code. The documentation walks you through every step of the setup process.

</details>

#### Node Operations

<details>

<summary><strong>What types of nodes can I run?</strong></summary>

Vola currently supports three node types during the testnet:

* **Validation Nodes**: produce and finalize blocks. Require a 50,000 $VOLA bond and team coordination.
* **Storage Nodes**: store user files and submit availability proofs. Require staking based on capacity committed and a public domain with SSL.
* **RPC & Archive Nodes**: serve chain queries for wallets and applications. No staking required, no rewards.

Compute Nodes are coming in a future release.

</details>

<details>

<summary><strong>What is the difference between a Validation Node and a Storage Node?</strong></summary>

Validation Nodes secure the blockchain itself: they produce blocks and finalize transactions using the Aura and GRANDPA consensus algorithms. They earn transaction fees and staking rewards but do not store user files.

Storage Nodes store the actual files uploaded by users through Vola-powered applications. They earn storage fee revenue and staking rewards, and they support delegated staking, allowing other $VOLA holders to back them without running hardware themselves.

</details>

<details>

<summary><strong>How much $VOLA do I need to run a node?</strong></summary>

$VOLA needed depends on the node type:

* Validation Nodes need 50,000 $VOLA staked.
* Storage Node stake is calculated based on storage capacity committed, using the network's staking formula. The minimum storage commitment is 500 GiB.
* RPC & Archive Node no staking required.

If you don't have enough $VOLA to meet the full Storage Node staking requirement yourself, you can open your node to delegators who contribute the remaining stake.&#x20;

</details>

<details>

<summary><strong>Can I run multiple nodes?</strong></summary>

Yes. There are no restrictions on the number of nodes a single operator can run.

Running multiple nodes increases your contribution to the network and your potential reward earnings. Each node must be registered and staked separately.

</details>

<details>

<summary><strong>What happens if my node goes offline?</strong></summary>

The impact depends on your node type.

For Validation Nodes, going offline means missing block production slots in your assigned era. You lose both transaction fee revenue and staking rewards for that era. Consistent downtime may affect your standing in the active validator set.

For Storage Nodes, going offline means missing DOP proof submission windows. Each missed proof lowers your DOP score, which directly reduces your share of the reward pool through the slashing mechanism. Sustained downtime will progressively reduce your rewards. Files you are responsible for must continue to be served, abruptly going offline without deactivating your node on-chain is penalized.

</details>

<details>

<summary><strong>What is a DOP proof and why does it matter?</strong></summary>

DOP stands for Proof of Downloadability. It is a cryptographic proof that a Storage Node must submit once per checkpoint *(approximately every day)* to demonstrate that the files it holds are still intact and retrievable.

The chain generates random values corresponding to specific chunks of files stored across the network. Each node must locate the relevant chunk, generate a Merkle proof of its inclusion in the file, and submit it to the chain within the checkpoint window.

The DOP score is calculated as the ratio of valid proofs submitted to total proofs expected and it directly affects your reward share. A consistently high DOP score means more rewards. Consistently missing proofs means reduced rewards through slashing.

**It is one of the most important metrics for a Storage Node operator to monitor.**

</details>

#### Staking & Rewards

<details>

<summary><strong>When do I receive my rewards?</strong></summary>

It depends on your node type.

Validation Node rewards are distributed per era (currently approximately every 7 hours). Once an era is complete, rewards can be claimed by submitting a TX to credit rewards to your configured payee account.&#x20;

Storage Node rewards are distributed per epoch (approximately every 5 days). At the end of each epoch.

</details>

<details>

<summary><strong>What is delegated staking?</strong></summary>

Delegated staking allows $VOLA holders to back an existing Storage Node with their tokens without running any hardware themselves.

Delegators earn a proportional share of the node's rewards based on how much they've staked and the operator's commission settings. It is important to note that delegation is only available for Storage Nodes.&#x20;

</details>

<details>

<summary><strong>How long is the unstake lock period?</strong></summary>

It depends on your role:

* **Validation Nodes:** 7 eras ≈ 49 hours after initiating unbonding.
* **Storage Nodes:** approximately 3 months. Stake becomes eligible to unstake once all files the node was responsible for have expired following deactivation.
* **Delegators**: approximately 4 months. This period is sized to cover the maximum file storage duration (3 months) plus the renewal window (1 month), ensuring files backed by your stake continue to be served until they expire.

</details>

<details>

<summary><strong>What is slashing?</strong></summary>

Slashing is the mechanism by which a node's rewards are reduced as a penalty for poor performance or misbehaviour.

For Validation Nodes, slashing occurs for protocol violations such as double-signing,\
i.e. producing two conflicting blocks for the same slot.&#x20;

For Storage Nodes, slashing is performance-based. It is calculated through a slashing factor R that reflects the node's historical DOP score.&#x20;

{% hint style="warning" icon="cloud-question" %}
**Slashing details will be available in the coming weeks.**
{% endhint %}

</details>

#### Testnet

<details>

<summary><strong>When does the public testnet launch?</strong></summary>

Public testnet is live, you can check the relevant links are below.

* [Testnet Explorer](https://testnet.volascan.io/)
* [Vola Wallet Extension](https://chromewebstore.google.com/detail/vola-wallet/bobefjjkdijgecmeclailfmnnoiagidp)
* [Vola Testnet Dashboard](https://testnet.vola.network/)
* [Vola Testnet Faucet](https://faucet.vola.network/)

</details>

<details>

<summary><strong>How do I qualify for testnet incentives?</strong></summary>

Testnet incentives are available exclusively to node operators, participants who run and maintain active Validation or Storage Nodes during the testnet period.

Simply setting up a node is not enough, your node must be registered, staked, and actively contributing to the network with confirmed participation throughout the testnet.

*RPC & Archive Node operators and delegators do not qualify for testnet incentives.*

</details>

<details>

<summary><strong>Why aren't exact incentive amounts published?</strong></summary>

Publishing exact reward figures in advance creates incentives for farming; operators spinning up nodes purely to capture rewards rather than to genuinely contribute to the network.

By announcing amounts at TGE based on confirmed participation data, Vola ensures rewards go to operators who actually contributed throughout the testnet period, not those who gamed the system.

**If you run a reliable node throughout the testnet, you will be rewarded fairly for your contribution.**

</details>

#### General

<details>

<summary><strong>Where can I get support?</strong></summary>

The primary support channel for Vola is the [Nuvola Discord server.](https://discord.gg/qnMSwT3Pvx)

The team actively monitors Discord throughout the testnet period and will respond to issues, questions, and feedback as quickly as possible.

</details>

<details>

<summary><strong>Where can I report issues and provide feedback?</strong></summary>

For bug reports and technical issues, refer to the [Reporting & Feedback](/docs/testnet-and-incentives/reporting-and-feedback.md) page.

</details>


---

# 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/appendix/faq.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.
