gitwtfhub

wtf is cfquant?

95ge/cfquant — explained in plain English

Analysis updated 2026-05-18

26PythonAudience · developerComplexity · 3/5Setup · moderate

TL;DR

A local bridge that lets miniQMT trading scripts work like the full QMT trading interface, connecting a web console, Python code, and QMT strategies.

Mindmap

mindmap
  root((cfquant))
    What it does
      Bridges web console
      Connects Python scripts
      Links QMT strategies
    Tech stack
      Python
      QMT
      xtquant
    Use cases
      Run xtquant code on miniQMT
      Bridge multiple terminals
      Manage account bindings
    Audience
      Quant traders
      Developers

Code map

Detail Auto

An interactive map of this repo's files and how they connect — its source is parsed live in your browser. Click Visualize to build it.

filefunction / class

Why would anyone build with this?

REASON 1

Run existing xtquant-based trading strategy code against miniQMT with minimal code changes.

REASON 2

Bridge a web control panel to one or more QMT terminals for market data and trade requests.

REASON 3

Manage multiple QMT terminals from one place by mapping trading accounts to separate bridge endpoints.

What's in the stack?

PythonQMTxtquant

How it stacks up

95ge/cfquantaevella/sky-pc-mcp-companionalicankiraz1/gemma-4-31b-mtp-vllm-server
Stars262626
LanguagePythonPythonPython
Setup difficultymoderatemoderatehard
Complexity3/53/54/5
Audiencedevelopervibe coderops devops

Figures from each repo's GitHub metadata at analysis time.

How do you spin it up?

Difficulty · moderate Time to first run · 30min

Requires a Windows machine running QMT, plus copying specific files into the QMT Python strategy directory.

Wtf does this do

cfquant is a bridge tool for QMT, a stock trading platform used in China. It connects a web control panel, external Python programs, and QMT trading strategy scripts, forwarding market data subscriptions, trade requests, account lookups, and callback events between them. Its main purpose is to let the lighter miniQMT version behave like the full QMT xtquant interface, so existing trading code written against xtquant can keep working with only small import changes. To set it up, you download the source, unzip it to a folder, and run a start script on Windows, which launches a local server and opens a web control panel in the browser. From there you use a binding page to link your QMT accounts to the bridge. Separately, you copy a handful of specific files and folders into your QMT Python strategy directory and load two of them inside QMT itself, one for regular use and one described as a low latency trading entry point. External Python programs that want to use cfquant as a drop in replacement for xtquant install it locally, since it is not yet published to a package index, either with an editable pip install from the source folder or by copying its two core folders directly into a Python environment. Code that previously imported from xtquant can then import the same functions from cfquant instead, or alias the whole import so existing code barely changes. A configure function, or equivalent environment variables, lets you point the bridge at a different host, port, or token if you are not using the defaults. The project supports multiple QMT terminals at once by giving each one its own bridge identifier, with accounts mapped to bridges through the web console. It also has a basic update mechanism that pulls new code from GitHub or a zip file while keeping a couple of backups so a bad update can be rolled back. The README does not mention what license the project is released under.

Yoink these prompts

Prompt 1
Help me set up cfquant as a bridge for my QMT trading strategy on Windows and load it into QMT correctly.
Prompt 2
I have existing code that imports from xtquant. Show me how to switch it to use cfquant instead with minimal changes.
Prompt 3
Explain how cfquant's bridge_id and account binding works for running multiple QMT terminals.
Prompt 4
Walk me through configuring cfquant's host, port, and token instead of using the local defaults.

Frequently asked questions

wtf is cfquant?

A local bridge that lets miniQMT trading scripts work like the full QMT trading interface, connecting a web console, Python code, and QMT strategies.

What language is cfquant written in?

Mainly Python. The stack also includes Python, QMT, xtquant.

How hard is cfquant to set up?

Setup difficulty is rated moderate, with roughly 30min to a first successful run.

Who is cfquant for?

Mainly developer.

View the repo → Decode another repo

This repo across BitVibe Labs

Don't trust strangers blindly. Verify against the repo.