What is Volition?
Volition is a hybrid Layer 2 architecture that gives users the choice between rollup mode (data on Ethereum) and validium mode (data off-chain) for each transaction or account. This flexibility allows users to match their security requirements with cost preferences rather than accepting a one-size-fits-all approach. Maximizing security for high-value operations while minimizing costs for frequent, lower-value transactions.
How Volition Works
In a volition system, users or applications specify their data availability preference per transaction. High-value operations, large deposits, or security-critical actions can use rollup mode, paying higher fees for Ethereum-level data availability guarantees. Frequent, smaller transactions can use validium mode at dramatically reduced costs.
The underlying execution and validity proof system remains identical. Proofs ensure computational correctness regardless of DA choice. The difference lies solely in where transaction data is stored and what trust assumptions apply to data retrieval for potential exits.
Use Cases
Consider a gaming application on volition. Users might deposit funds using rollup mode (full security for value entry), conduct in-game transactions in validium mode (cheap, frequent operations like item trades or battle outcomes), and withdraw winnings using rollup mode again. The high-value endpoints get maximum security while gameplay benefits from minimal fees.
DeFi applications might offer rollup mode for large trades and position changes while using validium mode for limit orders, small swaps, or high-frequency strategies. Users actively choose their security/cost balance based on transaction value and risk tolerance.
Implementation Status
zkSync's architecture supports volition-like capabilities. StarkNet could implement volition modes. The concept represents evolution in L2 design. Recognizing that different transactions genuinely have different security requirements and users should be empowered to make these tradeoffs explicitly.
Security Considerations
Volition requires users to understand data availability tradeoffs. Validium mode is not "insecure" in the computational sense. Validity proofs still guarantee correct execution. But it has different trust assumptions regarding data availability. Projects implementing volition must clearly communicate what DA providers are used and what happens if they fail.
The hybrid approach acknowledges that not all transactions need identical security, and forcing maximum security (and cost) on all transactions unnecessarily limits adoption and use cases.