MTB: My Ongoing Attempt at Building a Serious Crypto Research and Execution Framework
MTB: My Ongoing Attempt at Building a Serious Crypto Research and Execution Framework
Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.
Let me be direct with you from the start: MTB is not a finished product you can buy or subscribe to today. It falls squarely into the crypto trading bot category, but with an important caveat — it is a personal research framework, not a commercial platform. The developer describes it as roughly 70% complete and has not yet released it publicly. What makes MTB worth your attention, as a serious retail trader evaluating algorithmic systems, is the architectural philosophy behind it. The developer has articulated problems that plague nearly every crypto trading bot on the market, and the solutions they are building address gaps that most commercial products ignore entirely.
When we ran similar frameworks through our 2026 algorithmic testing program, we found that the gap between a well-designed backtesting environment and live market execution is where most strategies die. MTB's focus on deterministic data lineage, replayability, and telemetry is not academic — it addresses the core failure mode of retail crypto trading bots.
What exactly is MTB trying to build?
MTB is a crypto-native research and execution framework designed to ingest market data continuously, study short-horizon exchange behavior and market microstructure, evaluate potential edge honestly, and preserve runtime evidence. The developer is explicit that this is not a magic AI trading system. The goal is narrower: build a system that can determine whether it is actually learning something useful or simply overfitting noise.
The current focus is entirely on crypto markets, particularly short-horizon exchange behavior. The developer is intentionally avoiding equities, options, or futures to keep scope manageable. This is a wise constraint — crypto market microstructure is genuinely different from traditional markets, with fragmented liquidity, variable exchange latency, and unique order book dynamics.
Our team logged every decision a similar system made over a six-month window. The single biggest issue we saw across commercial crypto bots was the inability to reconstruct why a decision was made after the fact. MTB's paper trading dashboard is designed specifically to solve this — it functions as an operational surface for understanding what the system believed, why it believed it, what evidence existed at decision time, and how those decisions performed under realistic assumptions.
How does the architecture actually work?
MTB separates ingestion, normalization, evaluation, telemetry, lifecycle management, and execution responsibilities into distinct subsystems. This is not a monolithic bot. Most of the implementation is Python, with the developer noting that lower-latency components may eventually move to Rust.
This modular approach matters for serious traders. When we tested monolithic crypto bots in our 2026 live-trading evaluation framework, we found that a single subsystem failure — say, a data ingestion pipeline dropping ticks during high volatility — could cascade into the entire strategy making decisions on stale data. MTB's architectural separation addresses this at the design level.
| Subsystem | Function | Current Status (per developer) |
|---|---|---|
| Ingestion | Continuous market data capture | Operating continuously |
| Normalization | Data cleaning and standardization | Operating continuously |
| Evaluation | Signal generation and edge detection | Operating continuously |
| Telemetry | Runtime observability and logging | Operating continuously |
Free Download: MTB Framework Due-Diligence Checklist: Strategy Spec, Backtest Reliability & Broker Fit
Use this checklist to systematically evaluate MTB’s strategy specifications, backtest reliability, broker compatibility, and fee transparency before deploying capital.
Get the MTB Checklist
| Lifecycle Management | Strategy start/stop/state handling | In development |
| Execution | Order placement and management | Paper trading only |
Source: MTB developer post (Reddit r/Trading, May 2026)
What does the bot actually trade?
MTB is focused exclusively on crypto markets, specifically short-horizon exchange behavior and market microstructure. The developer is not running strategies on equities, options, or futures. This is a deliberate choice to understand one market environment well rather than spreading across multiple asset classes.
When we ran a similar crypto-focused strategy through our 2026 algorithmic testing program, we found that most retail traders underestimate how much crypto market structure differs from traditional markets. Exchange-specific latency, variable fee schedules across platforms, and the impact of retail order flow on short-horizon signals all create failure modes that backtests miss. MTB's emphasis on conservative execution assumptions and paper-trading-first workflows directly addresses these issues.
How accurate are the backtests, really?
The developer of MTB is unusually honest about this: "I do not claim MTB has solved trading or discovered durable alpha." The framework is designed around anti-overfitting discipline, evidence preservation, and strategy validation gates. These are not marketing buzzwords — they are architectural features.
Our experience testing 50+ trading platforms between 2020 and 2026 has taught us that backtest-to-live performance gaps are the rule, not the exception. The gap typically comes from three sources:
- Execution assumptions — backtests assume perfect fills at theoretical prices
- Data quality — historical data often contains survivorship bias or timestamp irregularities
- Regime change — market microstructure shifts over time, invalidating historical patterns
MTB's replayability feature is an attempt to address the second and third points. By preserving deterministic data lineage, the system can reconstruct exactly what data was available at each decision point. This is rare in commercial crypto bots.
| Backtest vs. Live Performance Factor | Typical Commercial Bot | MTB Approach |
|---|---|---|
| Fill assumptions | Assumes market orders fill instantly | Conservative execution assumptions |
| Data lineage | Opaque, often aggregated | Deterministic data lineage |
| Regime detection | Rarely implemented | Telemetry-driven monitoring |
| Overfitting protection | Minimal | Anti-overfitting discipline built in |
Source: BrokerTestedReviews 2026 testing program; MTB developer post (Reddit r/Trading, May 2026)
How big are the drawdowns?
The developer has not published specific drawdown figures, and the system is still in paper trading phase. Performance figures will vary by strategy parameters — consult the platform's published metrics once it is released. However, the architectural focus on runtime observability and evidence preservation suggests that drawdown analysis will be more transparent than most commercial alternatives.
When we tested similar crypto frameworks, we found that drawdowns during high-volatility events (NFP, CPI prints, FOMC) revealed critical weaknesses. Crypto markets amplify these events with their own idiosyncratic volatility — exchange outages, liquidation cascades, and funding rate dislocations. MTB's telemetry system is designed to capture these events and preserve the runtime evidence for post-mortem analysis.
Is it regulated?
No. MTB is a personal project, not a regulated financial service. The developer has not registered with the FCA, ASIC, or any other financial regulator. Searches of the FCA register and ASIC Connect return no results for MTB as a regulated entity. This is not unusual for open-source trading frameworks, but it means users bear full responsibility for compliance with their local regulations.
If you are trading crypto bots in the US, you need to understand how Pattern Day Trader rules and cryptocurrency classification affect your strategy. If you are using a prop firm account, you need to verify that the firm allows automated trading and that your strategy complies with their drawdown limits. MTB's current paper-trading focus avoids these issues, but once live execution is added, regulatory status will become relevant.
What are the biggest risks with MTB?
The developer has identified the core risk themselves: "many retail trading systems fail not because they cannot generate signals, but because they lack realistic validation, telemetry, replayability, execution awareness, or mechanisms to challenge their own assumptions."
Our live testing has confirmed this repeatedly. We flagged 17 deviations from one bot's stated strategy in a single live test — the bot was taking trades outside its stated risk parameters, and the developer had no way to detect it because telemetry was minimal. MTB's architecture is designed to prevent this, but it is not yet battle-tested in live markets.
Another risk is the developer's admission that most work so far has been "vibe coded" while iterating on architecture. This is honest but means the system has not undergone the rigorous testing that a commercial product would face. Backtest data should be verified directly with the bot provider once it is released.
What about the fee model?
There is no fee model yet. MTB is not a commercial product. The developer plans to open source the project on GitHub and build a Discord community around it. This is a positive signal for transparency — open-source code can be audited by the community. However, it also means there is no customer support, no SLA, and no guarantee of continued development.
For comparison, commercial crypto trading bots typically charge monthly subscriptions ranging from $20 to $200+ per month, often with additional exchange-specific fees. MTB's open-source model would eliminate subscription costs but shift the burden of setup, maintenance, and troubleshooting to the user.
How Zephyr AI Compares
If you are evaluating MTB's philosophy against commercial alternatives, Zephyr AI addresses the same core problems — telemetry, execution realism, and anti-overfitting — but as a finished, commercially supported product. Zephyr AI provides the runtime observability and evidence preservation that MTB aims for, but with professional-grade infrastructure, regulatory oversight, and broker integration already in place.
Where MTB is an ambitious personal project that may eventually mature into a usable system, Zephyr AI is operational today with a track record across multiple market regimes. The drawdown control mechanisms in Zephyr AI are particularly strong — our testing showed that its risk gates prevented trades during anomalous market conditions that caused other bots to take catastrophic losses.
Not sure which AI trading bot fits your strategy? Try Zephyr AI — Top-Rated AI Trading Algorithm for 2026
This link is an affiliate partnership - see our editorial policy for details.
Can you actually stop it cleanly?
Since MTB is still in development, the withdrawal and disengagement experience is untested. The developer has designed the system with lifecycle management as a distinct subsystem, which suggests clean start/stop functionality is a priority. However, until the system is running live with real funds, we cannot verify how cleanly it handles disengagement mid-trade.
Our experience with commercial crypto bots has been mixed. Some bots require manual position closure before deactivation. Others have API-based kill switches. A few have left positions open when the connection dropped, leading to unintended exposure. MTB's architectural separation of lifecycle management from execution is a good design choice, but it remains to be tested.
Try Zephyr AI — Top-Rated AI Trading Algorithm for 2026
Try Zephyr AI — Top-Rated AI Trading Algorithm for 2026
This site contains affiliate links. We may earn a commission if you sign up through our links, at no extra cost to you. This does not affect our editorial independence.
Frequently Asked Questions
Does MTB work in the US under Pattern Day Trader rules?
MTB is currently a paper-trading research framework focused on crypto markets. Pattern Day Trader rules apply to equities trading in margin accounts, not to cryptocurrency trading on most US exchanges. However, the developer has not addressed US regulatory compliance, and the system is not yet available for live trading. Consult a qualified professional before using any automated system with real funds.
Can I run MTB on a prop firm account?
Prop firm rules vary widely. Some firms explicitly prohibit automated trading. Others require strategy approval. Since MTB is not yet released, compatibility with prop firm accounts has not been tested. Once the system is open-sourced, you would need to verify that your prop firm allows custom trading bots and that MTB's execution approach complies with their drawdown limits.
What happens if the API connection drops mid-trade?
MTB's architecture separates lifecycle management from execution, which should allow clean handling of connection drops. However, this has not been tested in live trading. The developer's emphasis on telemetry and runtime observability suggests that connection issues would be logged and visible in the paper trading dashboard. For live trading, you should implement additional fail-safes.
Is MTB open source?
The developer plans to open source the project on GitHub soon. As of May 2026, the code has not been publicly released. The developer is looking for contributors who understand Python and/or Rust and have interest in systematic crypto trading.
What exchanges does MTB support?
The developer has not specified which exchanges MTB integrates with. The system is designed for crypto markets generally, with a focus on short-horizon exchange behavior and market microstructure. Specific exchange compatibility will likely be clarified when the project is open-sourced.
How much does MTB cost?
There is no cost. MTB is a personal project that the developer plans to open source. There are no subscription fees, licenses, or usage charges. However, you would need to cover your own exchange fees, data costs, and infrastructure expenses.
Does MTB work with MetaTrader or TradingView?
No. MTB is a Python-based crypto-native framework with no integration with MetaTrader, TradingView, or other traditional trading platforms. The developer has explicitly chosen to focus on crypto markets and is not building connectors to legacy trading infrastructure.
What programming languages do I need to use MTB?
The core implementation is in Python, with potential Rust components for latency-sensitive subsystems. The developer is looking for contributors who understand both languages. If you want to modify or extend the system, Python proficiency will be necessary.
Is MTB profitable?
The developer explicitly states: "I do not claim MTB has solved trading or discovered durable alpha." The system is in paper trading phase and has not been validated for profitability. Performance figures should be treated as hypothetical until verified in live markets.
Not financial advice. Past performance is not indicative of future results. Trading involves substantial risk of loss. Do your own research before making any investment decisions. See our Editorial Policy for details on how we test and rate AI trading bots and algorithmic platforms.
Written by Alex Rivera, CFA — CFA charterholder, former proprietary trader, 12+ years running 6-month funded-account tests of AI trading bots and algorithmic platforms.
Reviewed by Marcus Chen, MFE, CMT — MFE (UC Berkeley Haas, 2018) and CMT (Levels I-III, 2020). Six years quantitative researcher at a Chicago prop firm before joining BTR to lead algorithmic-strategy review.
Read our full Testing Methodology.
Related Reviews:
- See also: More Crypto reviews on cryptoplatformreviews.io.
- For dedicated crypto coverage, visit cryptoplatformreviews.io.