<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"><channel><title>dgbit Blog</title><description>Engineering notes from the dgbit project: backtesting fidelity, order routing on Bybit, and how to wire a custom strategy module.</description><link>https://dgbit.cryptuon.com/</link><language>en-us</language><item><title>Why dgbit uses an NNG service bus, not HTTP between workers</title><link>https://dgbit.cryptuon.com/blog/why-an-nng-service-bus/</link><guid isPermaLink="true">https://dgbit.cryptuon.com/blog/why-an-nng-service-bus/</guid><description>The dgbit data, backtest, and strategy services talk to each other over an NNG IPC message bus rather than HTTP. This post explains the trade-offs that decision encodes and what it means for operators running the stack.</description><pubDate>Wed, 06 May 2026 00:00:00 GMT</pubDate></item><item><title>How to wire a custom strategy module in dgbit</title><link>https://dgbit.cryptuon.com/blog/wiring-a-custom-strategy-module/</link><guid isPermaLink="true">https://dgbit.cryptuon.com/blog/wiring-a-custom-strategy-module/</guid><description>A walk-through of the BaseStrategy / StrategyMetadata / strategy_registry pattern from the dgbit README — what each piece is for, why the framework picks it over a DSL, and what you have to do to ship a strategy from notebook to live.</description><pubDate>Wed, 22 Apr 2026 00:00:00 GMT</pubDate></item><item><title>Why Bybit-specific matters for backtesting fidelity</title><link>https://dgbit.cryptuon.com/blog/why-bybit-specific-matters-for-backtesting-fidelity/</link><guid isPermaLink="true">https://dgbit.cryptuon.com/blog/why-bybit-specific-matters-for-backtesting-fidelity/</guid><description>Multi-exchange backtesting frameworks promise breadth and deliver vagueness. We make the case for binding the data fetcher, fee model, and execution layer to a single exchange — and why dgbit does so to Bybit.</description><pubDate>Wed, 08 Apr 2026 00:00:00 GMT</pubDate></item></channel></rss>