Drift

• Name: Drift
• URL: https://www.drift.trade/
• Category: onchain trading infrastructure / perpetuals and spot exchange protocol / Solana execution and automation stack
• Tags: solana-ecosystem
• Summary: Drift is an open-source Solana trading protocol that has expanded from perpetual futures into a broader execution and capital-efficiency stack spanning perps, spot margin, swaps, lending, insurance-fund staking, automation bots, self-hosted gateway access, and delegate-managed vaults. Its current primary-source surface jointly exposes user trading, protocol risk machinery, builder SDKs, keeper/JIT infrastructure, and multiple repo-level operating components. Keep this note on the protocol and product surface itself; the named implementation and distribution boundary now lives separately in drift-labs.
• What it does:
  • Provides onchain perpetual futures, spot margin trading, and token-swap functionality on Solana
  • Lets users lend and borrow assets, use deposited collateral across products, and stake into an insurance fund according to the protocol docs
  • Publishes TypeScript and Python SDKs, example bots, and a self-hosted gateway for developers and integrators building on top of the protocol
  • Supports automated offchain keeper roles such as matching, order triggering, liquidation, and JIT maker activity, with public tutorials and reference repos
  • Maintains adjacent infrastructure such as delegate-managed vault programs and transaction-server components in its public GitHub organization
• Key claims:
  • The homepage positions Drift as Solana’s premier trading hub, highlights deep liquidity, gasless trading, open-source verifiable contracts, a real-time risk engine, and a liquidation engine built for market stability
  • The main docs introduction says Drift is an open-sourced decentralized exchange on Solana and documents perps, spot trading, swaps, lend/borrow, insurance-fund staking, SDKs, and trading automation
  • The protocol docs are especially useful because they make the cross-margined risk-engine model explicit, including that deposits can serve as collateral across perpetuals and borrow/lend functions
  • The keeper-bot docs show Drift depending on rewarded offchain agents for matching, order triggering, liquidations, and JIT market making, which makes the protocol materially more than a static frontend or single-program exchange
  • The GitHub organization reveals a broader operating surface around protocol-v2, drift-vaults, swift, gateway, SDK repos, and example implementations
  • The protocol-v2 README confirms that the public codebase includes Solana programs, a TypeScript SDK, bot examples, local build flows, and a bug-bounty surface
• Whitepaper: No canonical standalone Drift whitepaper or litepaper surfaced in this pass. The clearest current source of truth is the official site, protocol docs, keeper-bot docs, and public GitHub organization/repositories; see ../whitepapers/drift-primary-sources-2026-04-28.md. For the newer protocol-versus-company split, see ../whitepapers/drift-entity-primary-sources-2026-08-13.md.
• Sources:
  • https://www.drift.trade/
  • https://docs.drift.trade/protocol
  • https://docs.drift.trade/developers/trading-automation/keeper-bots
  • https://github.com/drift-labs
  • https://github.com/drift-labs/protocol-v2
  • https://raw.githubusercontent.com/drift-labs/protocol-v2/master/README.md
  • https://raw.githubusercontent.com/drift-labs/gateway/master/README.md
  • https://raw.githubusercontent.com/drift-labs/swift/master/README.md

Internal linkages

• Company boundary for default app packaging, gateway / Swift orderflow tooling, and broader implementation gravity: drift-labs.
• Best orderflow and routing reads: jupiter and jito.
• Best oracle dependency anchor: pyth-network.
• Best vertically integrated exchange-stack contrast: hyperliquid.

Protocol / company boundary

• Keep this note on the protocol and product surface: market structure, shared collateral and risk logic, lending, insurance-fund staking, vault primitives, SDKs, and the offchain keeper / JIT roles the system depends on.
• Use drift-labs when the sharper question is who ships the first-party app, publishes the gateway and Swift order-pipeline stack, grows the team, and keeps extending the easiest builder and user path around Drift.
• That split matters because how does Drift work? and which named organization is packaging and operationalizing the default Drift experience? are related but not identical questions.

Control surface

• The markets, collateral logic, vaults, and program state live on Solana.

• The practical edge at the protocol layer still sits in keeper participation, JIT makers, liquidators, gateway compatibility, routing defaults, and oracle delivery. Those offchain layers decide a lot of the user outcome before the exchange UI does.

• Do not flatten that into the company note, though. This file should stay anchored on how the trading stack works; drift-labs is the cleaner place to reason about first-party rollout, implementation gravity, and the adjacent operator tooling many integrators inherit.

• Read Drift as execution infrastructure, not just as a perp venue.

• Last reviewed: 2026-08-13 UTC