
Essence
The foundational challenge in decentralized options is moving beyond the capital-inefficient architecture of over-collateralization. The concept of Proof Based Liquidity ⎊ which we define as Continuous On-Chain Risk Settlement (CORS) ⎊ is the necessary architectural shift that allows a derivative protocol to achieve capital efficiency comparable to traditional portfolio margining systems while maintaining non-custodial solvency proof. It represents the move from simple, static collateral to a dynamic, risk-adjusted capital model.
This system is predicated on the idea that liquidity providers (LPs) do not need to lock the full notional value of every short option position. Instead, they lock only the capital required to cover the portfolio’s net risk exposure, a calculation that is continuously verified and enforced by the smart contract. This verification is the “Proof” element ⎊ a cryptographic or state-based attestation of solvency at any given block height.
Continuous On-Chain Risk Settlement (CORS) is the dynamic, risk-adjusted capital model required to transition decentralized options from over-collateralization to true portfolio margining.
The systemic implication is profound. Without CORS, decentralized options protocols are confined to the shallow liquidity pools of simple collateral vaults, unable to compete on price or depth with centralized exchanges. CORS provides the technical and financial foundation for a decentralized clearing house, where the solvency of every participant is mathematically provable and automatically enforced, eliminating the single point of failure and opacity inherent in legacy financial infrastructure.

Origin
The requirement for Proof Based Liquidity stems directly from the failure of V1 DeFi derivatives to scale. Early decentralized options protocols relied on simple vault architectures where every short option position had to be 100% or more collateralized, typically in the underlying asset. This design, while simple and trust-minimized, created a deadweight capital cost ⎊ a capital sink that severely limited the capacity for market making and the provision of deep liquidity.
The conceptual genesis occurred when quantitative analysts realized that the collective risk of a diversified options portfolio is always substantially less than the sum of the individual risks. This insight, standard in traditional finance, demanded a cryptographic solution for its application on-chain. The core problem was: how do we calculate the portfolio’s net risk (the Margin Requirement ) in a gas-efficient, verifiable way, and then enforce it instantly?
The solution began to materialize with the development of Liquid Staking Derivatives (LSDs) and their use as options collateral. LSDs offer yield while being staked, providing a structural alpha to the liquidity provider. This capital-efficient collateral ⎊ earning yield while underwriting risk ⎊ is the first, necessary step toward a truly proof-based system, as the staked capital serves as the initial, verifiable proof of a capital base.
The final step is the continuous, real-time calculation of the Greeks to ensure the capital base is sufficient for the current risk.

Theory
The mathematical rigor of CORS is centered on two primary concepts: Portfolio Margining and the Dynamic Risk Vector. Our inability to respect the second- and third-order Greeks is the critical flaw in simplistic risk models.
CORS corrects this by focusing on the total potential loss across the entire book of options, not just the worst-case loss of a single position.

Portfolio Margining and Risk Vector
Portfolio margining dictates that the required collateral is a function of the portfolio’s net sensitivity to market parameters, rather than the sum of its notional exposures. This is formalized by the Dynamic Risk Vector ⎊ a set of Greeks that must be monitored and kept below a protocol-defined threshold.
- Delta (δ): Measures the change in option price relative to the underlying asset price. The net Delta of the LP’s book must be tightly controlled, often hedged to near-zero.
- Gamma (γ): Measures the rate of change of Delta. High Gamma means risk changes quickly, demanding a higher margin buffer.
- Vega (mathcalV): Measures the change in option price relative to volatility. This is the most significant risk factor in an options liquidity pool, as the entire book is fundamentally a short-volatility position.
- Vanna (mathcalVanna): The second-order cross-partial derivative measuring the sensitivity of Delta to changes in volatility, or Vega to changes in the underlying price. Vanna is a powerful, hidden risk that often drives unexpected margin calls.
The true functional elegance of CORS lies in its ability to enforce a risk-minimizing, convex margin requirement, ensuring the capital base is sufficient for the portfolio’s net Vega and Vanna exposure.

Solvency Proof Mechanisms
The “Proof” component is the mechanism by which the protocol verifies the LP’s collateral is sufficient to cover the required margin.
| Mechanism | Proof Basis | Latency | Capital Efficiency |
|---|---|---|---|
| Over-Collateralized Vaults (V1) | 100%+ Notional Lock | Zero (Static) | Very Low |
| Optimistic Risk State (CORS V1) | Attested Off-Chain Risk Report | Challenge Period (Hours) | Medium |
| Zero-Knowledge Risk Proof (CORS V2) | Cryptographic Proof of Solvency | Near-Instant (Sub-Second) | High |
The evolution toward Zero-Knowledge Risk Proofs is inevitable. Using ZK-SNARKs or similar constructions, an off-chain risk engine can compute the complex margin requirement and generate a succinct cryptographic proof that the LP’s collateral is adequate, without revealing the LP’s proprietary trading strategy. This is the true convergence of cryptographic assurance and financial complexity.

Approach
Current implementations of Proof Based Liquidity primarily center on an external, high-frequency Risk Oracle that publishes the required margin for each liquidity provider’s position. This approach trades the theoretical perfection of a fully on-chain calculation for the practical necessity of gas efficiency.

The Margin Engine and Liquidation Triggers
The core of the approach is the Margin Engine, which calculates the Maintenance Margin ⎊ the minimum collateral required to keep the position open. If the LP’s collateral value drops below this level, the protocol initiates an automated, permissionless liquidation.
- Risk Data Ingestion: The protocol feeds real-time market data (spot price, implied volatility surface) into the off-chain risk engine.
- Margin Calculation: The engine calculates the Greeks for the aggregated portfolio and determines the required collateral based on a Value-at-Risk (VaR) or Expected Shortfall (ES) model.
- Proof Publication: The required margin value is signed by the oracle and published on-chain, serving as the “Proof of Required Capital.”
- Collateral Check: The smart contract compares the LP’s current collateral value against the published margin requirement.
The speed of the liquidation process is the ultimate guarantor of solvency. A slow liquidation means the protocol assumes the market risk, which is antithetical to the Proof Based model. The liquidation trigger must be instantaneous and economically rational.
| Parameter | Description | Systemic Implication |
|---|---|---|
| Maintenance Margin Ratio | Minimum Collateral / Required Margin | Buffer against slippage and sudden price moves. |
| Liquidation Penalty | Fee levied on the liquidated collateral. | Incentive for liquidators to act immediately, ensuring system stability. |
| Oracle Latency | Delay between risk event and on-chain update. | The primary vector for systemic risk in an adversarial environment. |
This reliance on an external oracle, even a decentralized one, is the current practical constraint. The system is only as trust-minimized as its risk oracle.

Evolution
The evolution of Proof Based Liquidity is a story of migrating complexity from the off-chain layer to the cryptographic layer.
Early CORS models were a simple, centralized oracle broadcasting a margin number. The current generation is moving toward decentralized oracle networks, but this still only decentralizes the trust in the input, not the computation. The true leap is the adoption of Homomorphic Encryption and Zero-Knowledge Machine Learning (ZKML) to calculate the risk parameters.
This allows the complex Black-Scholes or stochastic volatility models to be computed off-chain, with the resulting margin requirement verified by a ZK proof on-chain. This removes the oracle as a single point of computational trust.
The future of Proof Based Liquidity will be defined by the successful deployment of Zero-Knowledge Machine Learning to prove the solvency of complex, non-linear risk models without revealing the underlying market maker’s proprietary data.
This development has profound implications for market microstructure. Liquidity providers can now compete on their model sophistication ⎊ the quality of their implied volatility surface and their risk engine ⎊ rather than just their raw capital size. This is a game of intellectual property, not balance sheet depth.
The strategic interaction becomes adversarial not just in price discovery, but in the speed and fidelity of the solvency proof itself ⎊ a constant, automated arms race. The most pressing systemic risks today relate to the integration of complex, non-linear derivatives with the underlying blockchain consensus mechanism ⎊ the Protocol Physics. A liquidation event must settle faster than a block time, or the system risks insolvency.
The contagion risk is significant: a failure in the oracle or a sudden, massive volatility spike that outpaces the liquidation engine could propagate failure across all protocols that rely on the same LSD collateral.

Horizon
The final destination for Proof Based Liquidity is the creation of the Decentralized Clearing Utility (DCU). This utility will be a cross-chain, fully collateralized, and mathematically provable system for settling all forms of derivatives.
The DCU will operate on a modular, multi-layer architecture:
- Layer 1 Settlement: Provides finality and the underlying collateral asset.
- Layer 2 Risk Computation: Executes the high-throughput, low-latency margin calculations, likely on a specialized ZK-Rollup, generating continuous solvency proofs.
- Layer 3 Liquidity Aggregation: A unified interface that pools capital from multiple LPs, each operating under the same CORS framework, presenting a single, deep liquidity pool to the end-user.
This future state fundamentally alters the macro-crypto correlation. By creating a robust, provable hedging layer, the DCU provides an essential shock absorber for the entire digital asset market. When the system can prove its solvency during periods of extreme volatility ⎊ when Vega risk explodes ⎊ it demonstrates a resilience that traditional, opaque clearing houses cannot match. The capital flows will shift from seeking simple yield to seeking risk-adjusted, provable returns. The architect’s final task is to design a system that not only survives the next market crash but is strengthened by the clarity of its automated, public solvency proof. The most critical challenge on the horizon remains the regulatory one. How will a sovereign jurisdiction classify a non-custodial DCU whose solvency is proven by cryptography rather than a licensed, centrally audited entity? This tension between mathematical proof and legal recognition is the final frontier.

Glossary

Capital Allocation Strategy

Systemic Contagion Risk

Implied Volatility Surface

Second Order Greeks

Governance Risk Parameters

Margin Requirement

Tokenomics Value Accrual

Portfolio Margining

Derivatives Market Evolution






