Skip to Content
DevelopersContributing to Velocity

Contributing to Velocity Protocol

Interested in contributing to Velocity Protocol? There are multiple ways to make valuable contributions, from documentation to code and more. Below are some of the primary avenues you can explore.

Documentation

Raise issues or submit Pull Requests at the Velocity Documentation Repository .

Bot Code

Bots and the on-chain JIT program are all part of the velocity-v1  monorepo.

Keeper Bots

  • Source: apps/keeper-bots-v2
  • Example: filler-lite is a recent effort to make running a keeper bot more accessible for lower-performing RPCs — see src/bots/fillerLite.ts in that directory.

Trading Bots

  • JIT Proxy Program (TS client, not yet published to npm — build from source): packages/jit-proxy
  • JIT Maker: source in apps/keeper-bots-v2/src/bots/jitMaker.ts

SDK

Add new features or improve code quality and maintainability to the SDK.

SDKPackageSource
TypeScript (@velocity-exchange/sdk)npm velocity-v1/packages/sdk 

Velocity has no Python SDK. The in-repo Rust client (rust/velocity-rs) is source-only and unpublished — contributions there build against the workspace in rust/.

Composing Programs on Top of Velocity

  • Example: Velocity Vaults (programs/vaults, first-party in the same monorepo — see Vault Managers)
  • Feature Requests: Tokenization of the insurance fund stake has been requested.

Main Program Contributions

  • Expanding the test suite (both TypeScript and Cargo tests) at the programs/velocity directory of the main repository.

Feel free to pick a project or issue that interests you and start contributing!

Last updated on