I just picked up a One G2. I know there’s a ton of support and discussion here for hip hop and related genres, as well as finger drumming. However, I’d love to chat about other genres such as house, chill and pop. How are people using the MPC to produce, mix and master original and remix projects all within the One?
Do all Go 7 Gen II suffer from input lag?
All the reviewers I watched (mono and color) discussed it.
If you had up to $200/month to spend on one investing or trading-related tool/service, what would it be and why?
I’m not a trader, but I’m interested in putting money into something that can actively manage or trade on my behalf — crypto, stocks, futures, options, etc. I’m not looking for hype or “guaranteed returns.” I’m looking for something trustworthy, transparent, and reasonably risk-managed.
I’d be open to something slightly aggressive, but not reckless. Ideally, I want a service that’s active daily and doesn’t require me to micromanage trades.
Curious what people here have actually used, what worked, what didn’t, and what red flags I should watch out for. Thanks in advance!
Over the last several months I’ve been building a crypto-focused trading research and execution framework called MTB.
The project started primarily as a learning exercise driven by curiosity about market structure, systematic trading, exchange behavior, and how professional-grade trading systems are actually engineered. Most of the work so far has been vibe coded while continuously iterating on the architecture, telemetry, ingestion systems, and validation workflows. At this point I’d estimate the project is somewhere around 70% complete.
MTB is not trying to present itself as a finished institutional platform or a magic AI trading system. There are already many strong open-source and professional systems in this space built by people with far more experience than I have. My goal has been narrower and more practical: build a crypto-native framework that can continuously ingest market data, study market behavior, evaluate potential edge honestly, and preserve enough runtime evidence to determine whether the system is actually learning something useful or simply overfitting noise.
The current focus is entirely on crypto markets, particularly short-horizon exchange behavior and market microstructure. I’m intentionally avoiding expanding into equities, options, or futures for now because I want to keep the scope manageable and stay focused on understanding one environment well.
A large part of MTB revolves around skepticism and operational honesty. I’ve become increasingly convinced that 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.
Because of that, MTB leans heavily into:
- deterministic data lineage
- replayability
- telemetry and runtime observability
- paper-trading-first workflows
- conservative execution assumptions
- strategy validation gates
- evidence preservation
- anti-overfitting discipline
- operational monitoring
The paper trading dashboard is a major part of the project. The intent is less “retail trading UI” and more an operational surface for understanding what the system believed, why it believed it, what evidence existed at decision time, and how those decisions performed afterward under realistic assumptions.
Architecturally, MTB separates ingestion, normalization, evaluation, telemetry, lifecycle management, and execution responsibilities into distinct subsystems rather than treating everything as one monolithic bot. Most of the implementation today is Python, although I expect some lower-latency or throughput-sensitive components may eventually move toward Rust.
I do not claim MTB has solved trading or discovered durable alpha. The project is still evolving heavily, and a lot remains to be validated properly over time. But I do think the system has developed some interesting characteristics around governance, replayability, telemetry, and evidence tracking that may be valuable to people who enjoy systematic trading research and infrastructure engineering.
Soon, I’d like to open source the project on GitHub and build a Discord community around it. I’m particularly interested in connecting with people who enjoy both the engineering side and the trading side of crypto markets.
At this stage, I’m mainly looking for people who:
- understand Python and/or Rust
- have interest in systematic crypto trading
- care about data quality and realism
- enjoy market structure and microstructure research
- think critically about validation and overfitting
- like building operational systems instead of only backtests
The project still has a long way to go, but the core runtime systems already operate continuously and are generating telemetry, ingestion data, paper-trading evidence, and research artifacts around the clock.
—
This has been cross-posted to a few threads. Looking for some healthy discussion and ideas.