Research guide
Derive V3 Explained: zkVM, Settlement & Risk
A plain-English guide to Derive V3's proposed architecture, portfolio margin, settlement, risk isolation, vaults, and builder surface.
- Updated
- Updated 2026-09-22
Quick answer
Derive V3 is best read as a proposed change to the clearing and execution architecture, not as a description of every capability currently live. The thesis is that zkVM execution and Ethereum settlement could support stronger portfolio margin, more collateral types, isolated listing risk, native vaults, and a builder SDK. This is editorial context, not a current quote. Verify changing product facts with the protocol before acting.
Last updated: September 22, 2026 — Answer framing and editorial context reviewed; dated product facts remain subject to the linked primary source.
Key takeaways
- A roadmap or DIP is not a shipped feature; separate proposed architecture from current mainnet behavior.
- The important V3 questions are settlement proofs, margining, collateral, listing risk, and migration.
- A more capital-efficient options venue can also create more complex liquidation and systemic-risk paths.
On this page
Derive V3 is best read as a proposed change to the clearing and execution architecture, not as a description of every capability currently live. The thesis is that zkVM execution and Ethereum settlement could support stronger portfolio margin, more collateral types, isolated listing risk, native vaults, and a builder SDK.
What to verify before relying on it
- Has the proposed migration shipped on mainnet?
- Which collateral, margin, and liquidation rules are live today?
- What is isolated per listing versus shared across a portfolio?
- How do proofs, bridges, custodians, and upgrade keys affect the risk path?
- What happens to existing positions and integrations during migration?
See the onchain options hub, Derive review, and options watchlist.
What would change for an existing Derive user?
The practical migration questions are custody, collateral support, margin rules, open-position handling, trigger orders, staking, and bridge exposure. Do not treat a proposed architecture as a reason to move funds early; wait for live migration instructions and confirm that the product you use has actually switched.
Is Derive V3 a new options venue or an upgrade?
Derive V3 is presented as an architectural upgrade to the existing Derive stack, not an independent venue a user can safely assume is already live. Proposed zkVM execution, Ethereum settlement, and portfolio-margin features create a different operational and liquidation surface only after the relevant components ship.
Frequently asked
Is Derive V3 live yet?
Treat Derive V3 as proposed until Derive's own documentation and live interface confirm the relevant migration, settlement, margin, and custody components. A roadmap, DIP, or third-party recap can explain the design without proving that users can access it today.
What should an existing Derive user do before V3?
Do not move funds or recreate positions based only on a proposal. Wait for official migration instructions, then check open-position handling, collateral support, triggers, bridge exposure, staking, and withdrawal paths before interacting with the new system.