---
title: "Discussion on \"QuantForge v0.2.0\" | Hashnode"
description: "Discussion on \"QuantForge v0.2.0\". QuantForge v0.2.0 adds live trading, SQLite-backed data sync, and monitoring commands to a Rust-first, CLI-only trading and backtesting framework."
url: "https://hashnode.com/posts/quantforge-v0-2-0/69c71aa77cf27065106e52fc"
---

[Feed](https://hashnode.com/feed) /

Discussion

# [QuantForge v0.2.0](https://formaldehid.hashnode.dev/quantforge-v0-2-0?utm_source=hashnode&utm_medium=feed)

QuantForge v0.2.0 adds live trading, SQLite-backed data sync, and monitoring commands to a Rust-first, CLI-only trading and backtesting framework.

Mar 28 · 3 min read · formaldehid.hashnode.dev  
Updated Jul 29  
Read the article

-   [#rust](https://hashnode.com/tag/rust)
-   [#trading](https://hashnode.com/tag/trading)
-   [#algorithmic-trading](https://hashnode.com/tag/algorithmic-trading)
-   [#opensource](https://hashnode.com/tag/opensource)
-   [#open-source](https://hashnode.com/tag/open-source)
-   [#cli](https://hashnode.com/tag/cli)

## Written by

[Marko Sabec](https://hashnode.com/@formaldehid)

@formaldehid · Ljubljana, Slovenia

  
[View profile](https://hashnode.com/@formaldehid)

Senior Rust & Solana Engineer | Building QuantForge

Senior software engineer working with Rust, Solana, backend systems, cloud infrastructure, Kubernetes, and QuantForge.

## Responses 1

Comments are turned off for this post.

[Arnold Holm](https://hashnode.com/@stratcorealpha)

[Oct 2](https://hashnode.com/posts/quantforge-v0-2-0/69c71aa77cf27065106e52fc/comment/6abf8df160a93221a58bf57a)

For the reconciliation roadmap, I would add an order-accepted-but-response-lost case before the restart test. Persist the client order identifier, interrupt the run after the exchange accepts the order, and restart against the same exchange state. The expected result is one existing order recovered by its identifier, with no second submission just because the local run lacks a success response.
