OpenViSTAI · Agents · Blockchain · Crypto
Menu
Exchanges & Trading

Heisenberg Algo Trading

Heisenberg Algo Trading is an open-source C++20 codebase for developing cryptocurrency algorithmic-trading applications, with documented build instructions and sandbox and ccapi-based order-execution components.

Independent OpenViST project profile, based on linked sources.

Heisenberg Algo Trading — OpenViST project profile in Exchanges & Trading.
OpenViST project illustration. See the linked sources for product details.
Understand the project

Practical overview

When it fits

Use it when you need a buildable C++ starting point for crypto algorithmic-trading work or want to examine order-execution flows, including a network-free sandbox path.

Who it is for

  • C++ developers building or studying cryptocurrency trading software
  • Developers who want to explore order-execution code with a local sandbox before working with live exchange connectivity

Documented uses

  • Configure and build the codebase for Debug or Release using Conan and CMake.
  • Build and run the documented Catch2 tests.
  • Smoke the CLI order flow through an in-memory sandbox executor without API keys.
  • Study the ccapi-based live executor and its exchange-specific credential and symbol requirements.
Before you choose

Requirements & limits

The repository is public and licensed under MIT.

  • The documented build workflow uses Conan, CMake and Ninja Multi-Config; Linux and macOS steps are in the README, while Windows has separate instructions.
  • Building both Debug and Release requires Conan dependency generation for both configurations in the same build directory.
  • The sandbox executor records order calls in memory and does not use ccapi or a network connection.
  • Live exchange use relies on ccapi and requires credentials and symbol strings matching the selected venue.

Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.

Source-based practical guide

Build and run the sandbox CLI on Linux or macOS

Configure the repository and build the CLI example that records an order call in memory without network access.

Before you start

  • Linux or macOS
  • Python 3
  • The repository's documented Conan and Ninja dependencies
  • A GCC 12 profile matching the documented example, or an adjusted profile for another toolchain

Steps

  1. Clone the repository, enter its directory, create and activate a Python virtual environment, and install the requirements file.

  2. Detect a Conan profile and install the repository's Conan configuration.

  3. Run the documented Conan install for the desired build configuration; for both Debug and Release in the Ninja Multi-Config tree, run both profile installs into the same build directory.

  4. Source the generated Conan build environment and configure with cmake --preset conan-default.

  5. Build the execute_order target, then run it with --sandbox --symbol BTC-USD --side buy --size 1 --type limit --price 100.

Expected outcome

The CLI invokes the sandbox executor, which records the order call in memory without using ccapi or a network connection.

Guide limitations

  • The documented build commands cover Linux and macOS; Windows has separate instructions.
  • The GCC profile commands are examples and may require adjustment for a different compiler or toolchain.
  • This sandbox example does not submit a live exchange order.
Source-based practical guide

Build and run the documented Catch2 tests

Build the test target and invoke CTest after configuring the project.

Before you start

  • A configured project using the documented Conan and CMake workflow
  • The default BUILD_TESTING setting, which is ON
  • A Debug or Release build configuration

Steps

  1. Configure using cmake --preset conan-default.

  2. Build heisenberg_tests with cmake --build build --config Debug --target heisenberg_tests --parallel, or substitute Release for Debug.

  3. From the build directory, run ctest --output-on-failure -C Debug, or substitute Release to match the build.

Expected outcome

CTest runs the configured Catch2 test target for the selected build configuration.

Guide limitations

  • The README says to configure with BUILD_TESTING=OFF if the test target should be omitted.
  • The documented commands are build instructions, not a claim that the tests have been run or passed.
Evidence and transparency

Sources & review

Source record details
Source availability
Active
Sources checked
8 October 2026
Original website title
profitviews/heisenberg · Official homepage title · retained in its source language