Velocity vs Drift Protocol: Post-Hack Relaunch or Archive?

Author: Riley HolterhusEditor: Kurt BarryReviewer: Rajeev Gopalakrishna

Quick verdict: Choose Velocity if you want to trade on the live incarnation of this codebase: Solana perpetuals with USDT settlement, a rebuilt administration model (tiered admin keys, the removed durable-nonce mechanism) and a staker-owned insurance fund — accepting the closed-beta status and unproven liquidity. Choose Drift Protocol only as a subject of study: trading halted after the April 1, 2026 hack, the venue operates as an archive with a recovery-payout mechanism, and its full product suite (spot, prediction markets, Fuel) is a thing of the past.

Parameter Velocity Drift Protocol
Platform status Running in closed beta (whitelist) since July 14, 2026; no public launch date announced. Halted after the April 1, 2026 hack; trading and withdrawals never resumed.
Architecture A fresh deployment of the forked Drift v2 program: its own program ID, tiered admin keys, a 100% staker-owned insurance fund, USDT settlement. The original v2 architecture on Solana: a single admin key, the durable-nonce mechanism (the hack vector), USDC settlement.
Product suite Perpetuals and Borrow & Lend only (plus Amplify, swaps up to 5x). No spot order book. The full stack: perpetuals, spot, prediction markets, vAMM LP shares, the Fuel loyalty program.

1. Security: the attack vector versus the rebuilt defenses

The critical Drift incident did not stem from a smart-contract bug: attackers compromised privileged multisig signatures through the durable-nonce mechanism, tricking the Security Council into unknowingly signing withdrawal transactions — roughly $286 million across 31 transactions in about 12 minutes. Investigators linked the attack to the Lazarus Group.

Velocity was built as a direct answer to that vector: the durable-nonce mechanism is removed from the program, the single administrator is split into cold/warm/hot/pause tiers, protocol-fee withdrawals are locked to a fixed recipient and require a dedicated FeeWithdraw hot key, and the deployment passed a review under STRIDE, Solana's security program. Audit coverage is honestly incomplete, however: the Trail of Bits and Neodyme reports describe the pre-fork code, and OtterSec's final report on Velocity's own changes has not been published yet.

2. Product: a trimmed perps-only venue versus the full stack

Drift v2 was one of the most feature-rich venues on Solana: perpetuals and spot in a single cross-margin account, prediction markets, vAMM LP shares, lending and the Fuel loyalty program. After the incident, that lineup survives only as history.

Velocity deliberately narrowed the scope to the core: perpetual futures and Borrow & Lend with the Amplify looping product and swaps up to 5x. The spot order book, external fulfillment venues, prediction markets, LP shares, protected maker mode and high-leverage mode are all gone. For a trader who needs only a perp engine with USDT settlement, the trim is not a loss but a reduced attack surface; for users of Drift's full stack, it is an irreversible loss of functionality.

3. User funds: the recovery mechanism and new accountability

Affected Drift users are compensated through recovery tokens: $1 of tokens per $1 of verified loss, redeemable once the pool crosses the $5 million threshold (seeded with $3.8 million of remaining protocol assets), refilled by quarterly exchange revenue, the ~$127.5 million Tether credit line and up to $20 million from partners. Early redemption means a pro-rata share of the pool's current balance and a waiver of the remaining claim.

Velocity does not carry old balances or liabilities into the new deployment — it is a clean venue whose economics are directly tied to repaying the legacy: revenue from the relaunched exchange is the source of the payouts. From a user's perspective, Velocity's success and the completeness of compensation are linked processes.

Detailed technical specifications

A comparison of architectural parameters and trading conditions for 2026:

Technical parameter Velocity Drift Protocol
Status Closed beta behind a whitelist; no public launch date. Halted after the hack; trading never resumed.
Program deployment A new program (vELoC…) with no state carry-over, fork point 0ae3e3b1d. The compromised deployment (dRifty…) is stopped.
Administration model Tiered cold/warm/hot/pause keys; recipient-locked fee withdrawals; durable-nonce removed. A single admin key; durable-nonce exploited by attackers.
Settlement asset USDT across all markets (a condition of the Tether credit line). USDC (historically).
Insurance fund 100% staker-owned; risky tiers walled out with a zero cap. A mixed model with protocol-owned shares.
Fees (Maker/Taker) −0.0025% rebate / 0.020–0.055% across 30-day volume tiers. Historically −0.0025% / 0.035%; the schedule is obsolete.
Maximum leverage Up to 20x per market (SOL-PERP); HLM removed. Up to 20x (historically).
Audit coverage ToB 2022 + Neodyme 2024 (pre-fork); the post-fork OtterSec report is unpublished. Pre-incident audits did not prevent the key compromise.
Liquidity Forming; no public metrics (beta). Withdrawn; pre-incident OI exceeded $700M — the Solana record.

Frequently Asked Questions (FAQ)

Do I need to migrate my old Drift account to Velocity manually?

Old Drift accounts and balances do not carry over: Velocity is a brand-new program deployment where even PDA addresses derive from a different program ID, and the global-state seed was renamed from drift_state to velocity_state. Affected users interact with the recovery mechanism through a separate compensation-token procedure, not through account migration.

What happens to the DRIFT token?

The DRIFT token still trades on secondary venues at a price near its all-time low, but Velocity has no native token: governance-staking fee discounts were removed from the new model, and fee tiers depend solely on 30-day volume. No official announcements about a DRIFT conversion or claims against the new platform have been made.

Is it safe to send funds to Velocity right now?

The platform is available only to closed-beta participants on the whitelist: most traders cannot access it, and no public launch date has been announced. Until access opens, sending funds makes no sense; once it does, verify the domain, confirm your access and remember the risks of any exchange's earliest stage.