Volition is a data availability architecture, pioneered by StarkWare, that grants users granular control over the security and cost of their transactions. For each transaction, a user can choose to post their data to the more secure but expensive Ethereum mainnet or to a lower-cost, off-chain Data Availability Committee (DAC). This hybrid model, often described as "sovereign data availability," creates a spectrum of security guarantees and fees within a single application, allowing users to tailor their experience based on the specific needs and value of each transaction.
LABS
Glossary
Volition
A hybrid Layer 2 scaling architecture where users choose, per transaction, whether data is published on-chain (like a zkRollup) or kept off-chain (like a Validium).
Chainscore © 2026
definition
DATA AVAILABILITY
What is Volition?
A hybrid data availability model that allows users to choose where their transaction data is stored for each individual transaction.
The core innovation of Volition is its per-transaction flexibility, which contrasts with the all-or-nothing approach of traditional Layer 2 solutions. In a ZK-Rollup, all data is posted to Ethereum (high security, high cost), while in a Validium, all data is held off-chain by a DAC (lower security, minimal cost). A Volition system, such as those enabled by StarkEx, operates as a hybrid ZK-Rollup/Validium, letting the end-user decide the data layer for every action. This is implemented by separating the proof verification (which always occurs on-chain) from the data publication location.
From a user's perspective, this might mean choosing high-security data posting for a large NFT mint or a significant DeFi trade, while opting for the cheaper Validium mode for a high-frequency gaming transaction. For developers, integrating Volition provides a flexible product that can cater to a wider range of use cases without fragmenting liquidity or state across multiple independent chains. The model directly addresses the blockchain trilemma trade-off between scalability, security, and cost by making it a user-configurable parameter rather than a fixed system property.
The security model of a Volition is bifurcated based on the user's choice. Data posted on-chain inherits Ethereum's robust security and censorship resistance. Data committed to a DAC relies on the honesty of that committee's members, who cryptographically attest to data availability. If a DAC acts maliciously, it can potentially freeze funds related to off-chain data but cannot steal them, as the integrity of state transitions is still secured by the validity proofs posted to Ethereum. This creates a clear risk spectrum that users must evaluate.
In practice, Volition architectures are a key component in scaling Ethereum for enterprise and high-throughput applications. They enable scenarios where an application can offer both bank-grade settlement assurance for institutional transfers and near-zero fees for consumer micropayments within the same smart contract environment. As the ecosystem evolves, the concept influences broader discussions about modular blockchains and data availability layers, emphasizing user choice and economic efficiency in data management.
how-it-works
DATA AVAILABILITY ARCHITECTURE
How Volition Works
Volition is a hybrid data availability model that allows users to choose, on a per-transaction basis, whether their data is posted to a blockchain or stored off-chain.
At its core, a Volition system provides a user-configurable choice between on-chain data availability and off-chain data availability. When initiating a transaction, the user selects where the associated state data or transaction data will be made available. Choosing the on-chain option posts the data directly to a base layer like Ethereum, inheriting its full security and censorship-resistance but paying higher gas fees. Choosing the off-chain option posts only a cryptographic commitment (like a zk-SNARK proof or validity proof) to the chain, while the full data is stored by a separate data availability committee or on a dedicated data availability layer. This fundamental choice is executed per transaction, not per smart contract or wallet.
The technical mechanism relies on a hybrid rollup or validium framework. In a typical implementation, a zero-knowledge rollup (zk-rollup) processes transactions off-chain and generates a validity proof. The critical divergence occurs with the data: for a 'Volition-on' transaction, the full transaction data is published as calldata on Layer 1. For a 'Volition-off' transaction, only the proof and a data root are posted, with the actual data held by a separate set of off-chain actors. This architecture allows applications to offer users a direct trade-off between security guarantees (full Ethereum-level security for on-chain data) and cost efficiency (significantly lower fees for off-chain data).
A practical example is a decentralized exchange (DEX). A user making a large, infrequent trade might select the on-chain data option to maximize security for their high-value transaction. Conversely, a user making frequent, small trades or playing a blockchain game might consistently choose the off-chain data option to minimize costs, accepting the slightly different trust assumptions of the off-chain data availability solution. This granular control is a key innovation over earlier scaling solutions, which typically enforced a single data availability model for all transactions on a given Layer 2 network.
key-features
ARCHITECTURE
Key Features of Volition
Volition is a hybrid data availability model that allows users to choose, on a per-transaction basis, whether their data is posted to a Layer 1 (e.g., Ethereum) or a Layer 2 (e.g., a Validium).
01
Dual Data Availability Modes
The core innovation of a Volition is providing a choice between two data availability (DA) modes for each transaction:
- On-Chain DA: Data is posted to the base layer (e.g., Ethereum), providing maximum security and censorship resistance.
- Off-Chain DA: Data is posted to a separate, high-throughput data availability committee or layer, providing lower cost and higher throughput. This granular choice is unique to the Volition model.
02
Per-Transaction User Choice
Unlike systems with a fixed DA layer, Volition empowers the end-user or dApp to select the security model for each individual transaction. A user can choose high-cost, high-security on-chain DA for a large NFT trade, while opting for low-cost off-chain DA for a routine token swap. This choice is typically made via the wallet interface at the time of signing.
03
Security Spectrum & Trade-offs
The two modes represent a clear security vs. cost/speed trade-off:
- On-Chain Mode: Inherits the full security and liveliness guarantees of the underlying L1. Transactions are cryptographically verifiable by anyone.
- Off-Chain Mode: Relies on the security of a separate data availability layer (often a Validium). This is faster and cheaper but introduces a trust assumption in the DA committee's honesty and liveness.
04
Execution & Settlement Layer
Regardless of the DA choice, all transaction execution and proof verification occurs on a zero-knowledge rollup (zk-Rollup). The zk-Rollup's state transitions are always proven with validity proofs (ZK-SNARKs/STARKs) and settled on the L1. The DA choice only affects where the transaction data needed to reconstruct the state is stored.
06
Comparison to Validium & Rollup
Volition is a superset architecture that encompasses both:
- Validium: A system that only uses off-chain DA (equivalent to always choosing the Volition's off-chain mode).
- zk-Rollup: A system that only uses on-chain DA (equivalent to always choosing the Volition's on-chain mode). Volition's flexibility makes it a hybrid solution, not a distinct third category.
DATA AVAILABILITY MODES
Volition Mode Comparison: Rollup vs. Validium
A technical comparison of the two primary data availability modes within a Volition architecture, focusing on security, cost, and performance trade-offs.
| Feature / Metric | Rollup Mode | Validium Mode |
|---|---|---|
Data Availability Layer | Layer 1 (On-Chain) | Off-Chain (Data Availability Committee or PoS Network) |
Data Publication | Transaction data posted as calldata on L1 | Zero-knowledge proofs posted; data held off-chain |
L1 Security Inheritance | ||
Censorship Resistance | High (L1-enforced) | Variable (depends on DAC/network honesty) |
Withdrawal Safety | Trustless (enforced by L1 data) | Requires honest majority of DAC/network |
Transaction Throughput | Higher (scales with proof verification) | Highest (no L1 data publishing cost) |
Typical Transaction Cost | Moderate (L1 data fee + proof cost) | Low (proof cost only) |
Data Withholding Attack Risk | Present (requires fraud proof system) |
examples
ARCHITECTURE
Protocols Implementing Volition
Volition is a hybrid data availability model that allows users to choose, per transaction, whether data is posted to a Layer 1 (like Ethereum) or a Layer 2. This section details the major scaling solutions that have implemented this architecture.
06
Core Architectural Trade-off
Implementing Volition introduces a fundamental design choice between universal security and modular flexibility. Key technical considerations include:
- State Management: Protocols must manage two distinct state transition paths (on-chain vs. off-chain DA).
- User Experience (UX): Wallets and dApps must clearly communicate the security implications of the user's choice.
- Composability Risk: Smart contracts may behave differently or face restrictions when interacting across different DA modes within the same system.
- Economic Security: Off-chain DA models rely on cryptoeconomic incentives or trusted committees, which differ from Ethereum's pure consensus-based security.
security-considerations
VOLITION
Security Considerations & Tradeoffs
Volition is a hybrid data availability model that allows users to choose, on a per-transaction basis, whether data is posted to a Layer 1 (for maximum security) or a Layer 2 (for lower cost). This section breaks down the core security tradeoffs inherent to this architecture.
01
Data Availability (DA) Choice
The fundamental security tradeoff in a volition is the choice of data availability layer. Posting data to the L1 (e.g., Ethereum) provides cryptographic guarantees and censorship resistance inherited from the base layer's consensus. Choosing an L2 or external DA layer (like a validium) introduces a trust assumption in that layer's operators to make the data available for fraud proofs or validity proofs. If this data is withheld, funds can become frozen.
02
Custodial Risk in Validium Mode
When operating in validium mode (data on an external DA committee), the system relies on a Data Availability Committee (DAC). Security depends on the assumption that a threshold of honest committee members will always publish data. This is a custodial risk, as a malicious majority could withhold data, preventing users from exiting. Solutions like proof-of-stake slashing for committee members aim to mitigate this, but it remains a weaker security model than pure L1 posting.
03
Exit & Withdrawal Guarantees
A user's ability to withdraw assets depends entirely on the availability of the data proving their ownership. In L1 DA mode, exit proofs can be submitted anytime, as data is permanently on-chain. In L2/Validium mode, if the DA layer fails, the withdrawal process can be halted. Some implementations feature emergency exit modes that allow users to bypass normal proofs after a long challenge period, but these are slower and less efficient.
04
Programmability & State Updates
The security model for smart contract execution and state updates is decoupled from the DA choice. Both modes typically use the same ZK-Rollup or Optimistic Rollup logic for execution integrity. The DA choice only affects the provability of state transitions. A state root published on L1 with L2 DA is only as trustworthy as the availability of the underlying data used to generate it.
05
Cost vs. Security Spectrum
Volition explicitly quantifies the cost-security tradeoff. L1 data posting is expensive but maximally secure. L2/Validium posting is cheap but introduces additional trust assumptions. This allows applications to segment their operations: high-value NFTs or institutional transfers might use L1 DA, while high-volume DeFi swaps or gaming micro-transactions might opt for L2 DA. The user or dApp makes an explicit, granular choice.
06
Implementation & Operator Risk
The security of a volition system also depends on the correctness of its implementation and the honesty of its operator (sequencer/prover). This includes risks like:
- ZK circuit bugs or prover malfeasance.
- Sequencer censorship of transactions.
- Upgradeability controls for the smart contracts governing the system. These risks are common to all rollups but are compounded by the complexity of managing two parallel data pathways.
etymology-history
ORIGIN STORY
Etymology and History
The term 'volition' has a rich history, evolving from a philosophical concept of free will into a precise technical architecture in blockchain scaling.
The term volition originates from the Latin volitio, meaning 'act of willing,' and entered English in the early 17th century as a philosophical concept describing the power of making conscious choices. In blockchain technology, this concept of sovereign choice was co-opted by the zkSync team at Matter Labs to name a novel hybrid scaling architecture that allows users to choose the data availability layer for their transactions. This architectural pattern, first formally proposed around 2020, represents a significant evolution from monolithic chains and single-solution Layer 2s, giving users direct control over the security-cost trade-off.
The historical development of volitions is intrinsically linked to the data availability problem and the rise of modular blockchains. As Ethereum's scalability roadmap, particularly through EIP-4844 (proto-danksharding), began to formalize cheaper, external data layers like blobs, the need for a flexible system became apparent. The volition model emerged as a direct response, allowing a single rollup or zkEVM to post its transaction data either to the high-security Ethereum mainnet (as call data) or to a lower-cost external system, with the user deciding per transaction. This created a new paradigm in user-centric design for scaling solutions.
Key implementations, such as zkSync's zkPorter and StarkWare's Volition mode, brought the concept to life. These systems typically bifurcate state into two tracks: a ZK-rollup track with Ethereum-level security and a validium track with off-chain data availability. The user's volition—their explicit choice at the time of transaction—determines which track and associated security model their assets inhabit. This historical shift moved the critical decision of trust assumptions from the protocol designers directly into the hands of the end-user, a fundamental rethinking of Layer 2 architecture.
DEBUNKED
Common Misconceptions About Volition
Volition is a hybrid data availability model that allows users to choose, per transaction, whether to post data to a Layer 1 (like Ethereum) or a Layer 2 (like a Validium). This section clarifies widespread misunderstandings about its security, functionality, and trade-offs.
No, a Volition is not just a Validium; it is a hybrid system that incorporates both Validium and ZK-Rollup modes. A Validium is a specific scaling solution that posts zero-knowledge proofs to a Layer 1 but keeps transaction data off-chain, relying on a Data Availability Committee (DAC) or similar. A Volition, such as the model pioneered by StarkWare, gives users a per-transaction choice: they can opt for the higher security of a ZK-Rollup (data on L1) or the lower cost of a Validium (data off-chain). This makes Volition a flexible framework, not a single, fixed architecture.
VOLITION
Frequently Asked Questions (FAQ)
Volition is a hybrid data availability architecture that allows users to choose, on a per-transaction basis, whether to store data on-chain (Ethereum) or off-chain (a Data Availability Committee). This section answers common questions about its mechanics and implications.
Volition is a hybrid data availability model that gives users granular control over where the data for their transactions is stored. It works by allowing a user, for each individual transaction, to select one of two data availability (DA) modes: on-chain (data is posted to and secured by the Ethereum L1) or off-chain (data is held by a Data Availability Committee or DAC). The core transaction logic executes on a Layer 2 (L2) like zkSync or StarkNet, but the chosen DA layer determines the security and cost profile. This creates a spectrum where users can opt for maximum security (on-chain) for high-value assets or maximum cost efficiency (off-chain) for lower-risk interactions.
ENQUIRY
Get In Touch
today.
Our experts will offer a free quote and a 30min call to discuss your project.
NDA Protected
Confidentiality24h Response
Time to ValueDirectly to Engineering Team
No Sales Fluff10+
Protocols Shipped
$20M+
TVL Overall