# DIP: Launch Derive V3

- Space: [Derive](https://snapshot.box/s:derivexyz.eth.md)
- Author: 0x76E6F5C2A64df0F53077602642B79a45D5Ba6D52
- State: Passed
- Voting type: Basic
- Start: 2026-09-24 01:40 UTC
- End: 2026-10-04 01:40 UTC
- Votes: 16
- Discussion: https://forums.derive.xyz/t/dip-launch-derive-v3/322
- Open in Snapshot: https://snapshot.box/#/s:derivexyz.eth/proposal/0xf0b2a758ec18edf9e27c5e779dd601140ae0766888de52a9fb2d749d3a87fdcb

## Results

- For: 107,111,354.71 voting power, 99.4%
- Against: 653,796.89 voting power, 0.6%
- Abstain: 0 voting power, 0.0%

## Proposal

# Simple Summary

Deploy and launch Derive V3 (zkVM program settling on Ethereum mainnet), migrate all V2 positions and balances into V3's genesis state, move bridge funds to L1, and wind down Derive Chain.

# Abstract

This proposal describes the process of deploying and migrating to V3, which is as follows:

- Build a V3 genesis state from a pinned V2 snapshot: accounts, balances, positions, wallet-held ERC20s (including stDRV), unclaimed lyra migration, pending rewards, native ETH
- Initialise V3 protocol
- Move bridge balances either to the V3 L1 contracts, directly to owner wallets or LZ OFTAdapter contracts where applicable
- Deploy stDRV to Ethereum mainnet and connect the DRV OFT to Robinhood Chain
- Wind down Derive Chain after successful migration and launch of Derive V3

This proposal also sets out the trust model V3 is built around: what "self-custodial", "trustless" and "private" mean in this design, how each is enforced, and where the remaining trust assumptions sit. Most of V3's technical complexity comes from the trade-offs between these three goals.

Approval of this proposal authorizes the deployment and launch of V3, the migration of V2 state and assets, the wind-down of Derive Chain, and the related token, Security Module and migration actions described below.

# Motivation

From the start, contributors to Lyra and Derive have built at the technical frontier in order to bring the best options trading experience on-chain. Early Lyra contributors built the first options AMM and were among the first teams to deploy to Optimism Mainnet in 2020, as options margin on L1 was economically impractical. In 2023, the protocol was re-architected from an AMM-centric design to an orderbook with on-chain portfolio margin competitive with traditional finance. This institutional-grade portfolio margin required gas throughput not possible on Optimism Mainnet, leading to the launch of Derive Chain using the OP Stack with Conduit. Over the following two years, Derive introduced RFQ options, sub-ms matching engine latencies, significant TVL through partner custodians, and HYPE, ZEC and XAUT options markets. 

These major architecture changes have brought Derive to where it is today. As of 7 September 2026, Derive represented approximately 95% of on-chain options premium volume over the preceding 30 days, based on DeFiLlama data. Derive also represents approximately $2 billion of open options interest against an estimated global total of roughly $40 billion. 

However, as Derive has grown - so too has the number and types of users on the exchange. In particular, Derive is increasingly onboarding more sophisticated users and institutions. This presents a new set of growth opportunities and challenges around which we must once again re-architect the system. 

V3 enables these major improvements:
- Order of magnitude increase in throughput - comfortably handling hundreds of billions daily notional volumes with ability to support new, increasingly complex products and features.
- Thousands of positions cross-margined in a single portfolio
- Significantly faster development of new products and features
- Improved retail and institutional user experience across EOA, Multi-sig, and MPC wallets. 
- A simplified integration experience for builders and institutional partners
- Allow integrators to choose their own bridge infrastructure
- A clear path to e2e privacy

In addition to the above architecture upgrades, several major protocol improvements will also ship in this initial release, with more planned for upgrades soon after launch:
- Risk isolation/risk universes, enabling faster deployment of RWAs and diverse markets
- Borrowing of non-cash assets (e.g. borrow ETH, WBTC, HYPE)
- Cross currency margin for PM subaccounts (e.g. ETH + BTC PM)
- Native 1-click vault deployments
- Institutional-grade session key controls

As well strengthening the liveness and security of the protocol
- Ethereum-native custody
- No "Trusted Risk Assessors": all protocol actions are always fully margined
- Validity-proven state 
- Censorship resistant escape hatch, with forced inclusion of L1 actions
- Minimal to no trade reverts

# Terminology
V3 has three layers with very different trust properties. Much of this proposal turns on which layer is responsible for what.
- Derive Exchange API: a fully centralized backend operated by Lyra Technologies Corp. Counterparty matching, the orderbook / RFQ, and KYC / compliance live here. Users interact with it over REST / WS.
- Sequencer: operated by a Derive group entity designated by the Derive Foundation, but unopinionated: it must follow the rules imposed by the L1 Contracts. Its job is to compress transactions into batches that can be proven and processed on L1. It does not find counterparties, and it cannot forge orders or extend margin beyond the contract parameters.
- L1 Contracts: the decentralized protocol layer, modifiable only through governance and the Owner powers described below. The protocol logic is written in Rust and executed inside the zkVM; a hash of the compiled program (the verifying key) is committed on-chain, which is what forces the sequencer to follow the protocol. Any actor can deposit, withdraw or trade against these contracts by bringing their own proofs.

The Derive Exchange API and Application will continue not to be available to US persons. These restrictions apply to access through the centralized Application and API and do not alter the permissionless nature of the L1 Contracts. 

# Specification  

<For full specification view the forum post: https://forums.derive.xyz/t/dip-launch-derive-v3/322>

---

To vote or create proposals from an AI assistant, connect the Snapshot MCP at https://mcp.snapshot.box

