# Vola Validation Nodes As a PartnerChain, Vola Network inherits its foundational security model from the Cardano ecosystem while extending it to support decentralized storage, compute, and cloud coordination at scale. > ***Vola Validation Nodes form the core consensus, verification, and coordination layer of the network, acting as the backbone upon which the entire Vola ecosystem operates.*** These nodes are responsible for producing blocks, validating state transitions, and continuously recording all protocol-relevant information generated by users, applications, and infrastructure providers. This includes -but is not limited to- file ownership records, storage commitments, availability proofs and staking activity. **As such, validation nodes represent the canonical source of truth for the Vola Network.** #### **Backbone of the Vola Ecosystem** Vola Validation Nodes underpin every major function of the network, such as: * **File ownership and metadata tracking** * **Storage availability proofs and node performance data** * **Governance actions and protocol upgrades** * **Application-level state used by frontends and dApps** A distributed set of validation nodes continuously produces blocks that record this information on-chain. Applications and services built on Vola rely on this validated state to deterministically associate files, storage nodes, and future compute workloads with user identities and permissions. #### **Validator Responsibilities** Validators verify all on-chain activity, including storage availability proofs, node performance metrics, staking updates, governance actions, and cross-chain settlement. They also coordinate ongoing monitoring of stored files by issuing and recording availability challenges, ensuring continuous accountability at the protocol level. Validation nodes enforce all runtime rules governing staking, slashing, economic incentives, infrastructure participation, and interoperability. As decentralized compute will be introduced, validators will additionally track compute usage, workload execution, and processing commitments to maintain unified coordination across storage and compute. #### **Rewards and Incentives** Validation nodes are compensated for securing the PartnerChain and coordinating decentralized cloud operations. Incentives may include: * **Block Rewards**\ Compensation for block production and validation. * **Protocol Fee Participation**\ A share of transaction fees and ecosystem activity generated by storage and compute usage. **Reward parameters are governed on-chain and evolve with network usage.** #### **Separation From Infrastructure Nodes** A core architectural principle of Vola as a PartnerChain is **clear separation of responsibilities**: * Validation Nodes secure and coordinate the blockchain * Storage Nodes provide decentralized data availability * Compute Nodes execute distributed workloads This separation ensures scalability, security, and operational clarity across the decentralized cloud stack. #### **Integration With Cardano SPOs** As a PartnerChain, Vola is designed to be natively compatible with Cardano Stake Pool Operators (SPOs). Many SPOs already operate with: * High-availability infrastructure * Globally distributed nodes * Secure key management systems Through initiatives such as the [**Early Node Onboarding Program (ENOP)**](/vola-node-economy/early-node-operator-program-enop.md), SPOs can extend their infrastructure to include Vola Storage Nodes, leveraging existing expertise while earning additional rewards within the Vola ecosystem. --- # 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/vola-node-economy/vola-validation-nodes.md?ask= ``` 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.