Cowrie Research

drift-entity-primary-sources-2026-08-13

4 min read

Drift entity primary-source snapshot

Fetched: 2026-08-13 UTC

1) Official homepage

Source: https://www.drift.trade/

Selected excerpts from the official site:

Built for Traders. Engineered for Execution.

Your all in one DeFi Suite

Performance-first infrastructure

Additional signals from the source:

  • The homepage frames Drift as a packaged trading and execution environment rather than a narrow single-program protocol
  • Mobile-app promotion, institutional language, and broad product bundling all point toward a named operator / distribution shell above the contracts

2) Series B funding announcement

Source: https://www.drift.trade/updates/drift-raises-25m-in-series-b-funding-led-by-multicoin

Selected excerpts from the official post:

Drift is excited to announce a $25M Series B led by Multicoin Capital

The funds raised will be directed towards Drift’s mission of building the most capital-efficient Defi platform in the world. A SuperApp that offers you all your favorite trading products under one roof.

The funding round helps Drift pursue two main goals: growing the team with top talent and funding the development of the first of its kind DeFi Superapp on Solana

Drift plans to leverage its new funding to expand the accessibility of BET through a dedicated mobile app

Additional signals from the source:

  • Team growth, superapp packaging, mobile distribution, and market-localization plans are company-shaped execution choices rather than protocol mechanics alone
  • The post is useful evidence that Drift still has a named builder / operator center making roadmap and packaging decisions

3) Series A funding announcement

Source: https://www.drift.trade/updates/drifts-series-a-announcement

Selected excerpts from the official post:

The fundraise will be directed towards expanding Drift’s product lines as well as building out further infrastructure that will bring more users and liquidity into the ecosystem

Drift intends to decentralise the protocol and push the frontiers of what’s only possible on Solana.

The funding round helps us pursue two main goals: growing our team with top talent and continually innovating our product design

Drift plans to launch a full Drift Mobile experience

Drift is investing heavily into network architecture research to reduce user confirmation times and rival centralised exchange experiences.

Additional signals from the source:

  • The post makes the timing legible: decentralization is described as future-oriented while team, product, mobile, and infrastructure work remain centrally organized in the present
  • Network-architecture and UX optimization belong in the operator / implementation story, not only the protocol note

4) GitHub organization inventory

Source: https://github.com/drift-labs

Selected excerpts / signals from the public org page:

protocol-v2

drift-vaults

swift

gateway

Additional signals from the source:

  • The public org inventory shows Drift maintaining a broader stack than the core protocol alone
  • Gateway, vault, and Swift repos make the named implementation organization analytically useful

5) protocol-v2 README

Source: https://raw.githubusercontent.com/drift-labs/protocol-v2/master/README.md

Selected excerpts from the official repo:

This repository provides open source access to Drift V2’s Typescript SDK, Solana Programs, and more.

Example bots (makers, liquidators, fillers, etc) can be found here

Additional signals from the source:

  • The repo confirms that the drift-labs boundary includes SDK, programs, and bot-facing surfaces rather than only contract artifacts

6) gateway README

Source: https://raw.githubusercontent.com/drift-labs/gateway/master/README.md

Selected excerpts from the official repo:

Self hosted API gateway to easily interact with Velocity Protocol

use delegated signing mode

Gateway will resubmit txs until they are either confirmed by the network or timeout.

Additional signals from the source:

  • The gateway is a meaningful operator-facing surface: delegated signing, rebroadcast policy, account handling, and RPC topology all become part of the practical control story
  • Even self-hosted tooling can make the implementation organization important because users often inherit the defaults it publishes

7) swift README

Source: https://raw.githubusercontent.com/drift-labs/swift/master/README.md

Selected excerpts from the official repo:

Infrastructure for the Swift order pipeline.

Swift Server: HTTP server for receiving signed order messages from takers

Ws Server: Ws server for broadcasting taker orders to market makers

Confirmation Server: Provides API for server progress tracking

Additional signals from the source:

  • The Swift repo is direct evidence that important orderflow machinery and market-maker interaction live in the implementation boundary around Drift
  • This is exactly the kind of adjacent company-shaped infrastructure the protocol note should not flatten away

Notes

  • Drift now deserves a cleaner protocol-versus-company split: the protocol note for trading mechanics and risk design, the company note for implementation gravity, gateway / orderflow tooling, and first-party product distribution.
  • The strongest entity evidence in this pass is not a legal-entity filing. It is the consistent first-party pattern of team growth, mobile / product packaging, and the maintained drift-labs code surface around the protocol.

Graph View