01 / THE SIGNAL

我们发现了什么

我以自己特定的方式在本地回测机器人,现在借助 AI,我的智能体可以在本地生成代码、回测并分析结果,无需在执行平台上运行其中任何内容。The0 是开源的,采用 Apache-2.0 许可证:https://github.com/alexanderwanyoike/the0。我目前使用 the0 运行自己的个人算法交易机器人

  • 来源:Hacker News发现于 2026-07-21
  • 证据等级:D · 发现产品或需求信号,暂未获得可核验的商业证据。
  • 商业模式:API / Usage-based
  • 主题:独立产品
  • 初筛评分:18.4/100 · 收录 1
#独立开发#待验证#开源
02 / SOURCE & EVIDENCE

证据,比故事更重要。

发现产品或需求信号,暂未获得可核验的商业证据。

规则清洗与初筛,未经人工商业核验。原文语境、实际客户和付费情况仍需自行验证。

引用与数字披露

来源类型(原作者自述/第三方测算/媒体转引)需采集端标注,本版尚未落字段。

短句引用
作者
未标注
抓取日期
来源类型
未标注
数字口径
币种
未标注
口径
未标注
披露主体
未标注
披露日期
未标注

中文辅助译文(全文)

我是一名独立开发者,一直对算法交易心痒难耐。一开始,我通过 Yves Hilpisch 的《Python for Algorithmic Trading》一书学习如何进行算法交易;读完那本书后,我彻底入了迷,开始构建算法交易机器人。最初,这些只是我在本地机器上运行的独立 Python 脚本。这其实是个糟糕的主意,因为本地机器不够可靠,而我希望机器人能够一年 365 天、每天 24 小时不间断运行。在我的正式职业生涯中,我是一名软件工程师,有构建分布式系统和容错 Web 应用的经验。我对把自己的代码部署到 MetaTrader、CTrader 或 QuantConnect 等托管服务上并不感兴趣,因为我希望完全掌控自己的代码及其运行环境。我还希望能够使用任何想要的编程语言来运行机器人,而不仅仅是 Python。有时我想用 Python 做一个机器人原型,然后出于性能原因再用 C++ 或 Rust 重写它。很多人在这个阶段会说,为什么不直接使用 Lean、Freqtrade 或 Hummingbot 这样的框架呢?然而我发现这些框架过于带有强烈的主观倾向,一旦决定使用它们,你的机器人就成了它们框架不可分割的一部分。我用自己的特定方式在本地对机器人进行回测,而现在借助 AI,我的代理可以在本地生成代码、进行回测并分析结果,无需在执行平台上运行任何东西。我希望这些机器人能够像其他软件应用一样进行部署、版本管理、更新和监控。我还希望探索构建一种以标准化方式运行机器人的方案。这是一段长达四年的旅程,期间我犯了很多错误。该应用经历了 4 次重新架构,其中 3 次基本上是完全重写。

第一个版本是一个 Python 程序,机器人只是动态加载的模块。第二个版本是我的无服务器阶段,当时我在内部只想要一个在线的、由 cron 触发的、只为我自己工作的东西。第三个版本是我第一次涉足 kubernetes;更加云原生,而我这个蠢货当时决定把它做成一个 SaaS。最终形态是一个完全自托管的运行时、API、CLI 和前端,让你能够以容错方式将机器人作为容器在本地(通过 docker the0 local)或集群(k8s)中运行,并通过一个极简的前端对它们进行监控。为了支持多种语言,机器人需要实现一个轻量级的契约:一个 main(bot_id, config) 函数和一个 bot-config.yaml 文件。运行时(用 Go 编写)负责其余工作,它支持 C++、Rust、Python、JS/TS、C#、Scala 以及那些胆大敢试的 Haskell。更多关于架构的信息请参见:https://docs.the0.app/runtime 如果你想试用 the0,你可以在本地运行它,操作指南请参见:https://docs.the0.app/deployment/local-getting-started 。The0 是开源的,采用 Apache-2.0 许可证:https://github.com/alexanderwanyoike/the0 我目前使用 the0 来运行我自己的个人算法交易……

译文由上游机器翻译生成,可能有误;判断请以英文原文为准。

英文原文(来源本站未改写)

So Im a solo developer who has always had an itch for algorithmic trading.Initially I started off learning how to trade algorithmically with Yves Hilpisch book "Python for Algorithmic Trading" after reading that book I was hooked and started building algorithmic trading bots.Initially these were separate python scripts that I ran on my local machine.That was a bad idea cause local machines are not reliable and I wanted to run my bots 24/7 365.In my actual career im a software engineer with experience in building distributed systems and fault tolerant web applications.

I wasn't interested in deploying my code to managed services like MetaTrader, CTrader or QuantConnect etc because I wanted to have full control over my code and the environment it runs in.I also wanted to be able to run my bots in any programming language I wanted, not just Python.Sometimes I wanted to prototype a bot in Python and then rewrite it in C++ or Rust for performance reasons.Many at this point would have said why not use a framework like Lean or Freqtrade or Hummingbot.However I found that these frameworks were too opinionated and if you decide to use them then your bot is now part and parcel of their framework.

I backtested my bots locally in my own specific way, and now with AI my agents can generate code, backtest and analyze the results all locally, no need to run any of it in the execution platform.I wanted bots I could deploy, version, update and monitor like any other software application.I also wanted to explore building something that creates a standardized way of running bots.This has been a 4 year journey and I made a lot of mistakes along the way.The application has seen 4 rearchitectures, 3 of which were basically complete rewrites.The first version was a python program and the bots were just modules that were loaded dynamically.

The second was my serverless phase when I internally just wanted something that was online cron triggered and only works for me.The third was the first time I was dipping into kubernetes;more cloud native and the idiot in me decided to try make it a SaaS.The final form is a fully self-hosted runtime, api, cli and frontend that let you run bots as containers in a fault tolerant way both locally (through docker the0 local) and in a cluster (k8s) and monitor them with a minimalistic frontend.To support multiple languages there's a thin contract that the bots have to implement: a main(bot_id, config) function and a bot-config.yaml file.

The runtime (written in Go) takes care of the rest, it supports C++, Rust, Python, JS/TS, C#, Scala and Haskell for those who are brave enough to try it.More on the architecture here: https://docs.the0.app/runtime If you want to play with the0 you can run it locally, guide here: https://docs.the0.app/deployment/local-getting-started .The0 is open source and licensed under Apache-2.0: https://github.com/alexanderwanyoike/the0 I currently use the0 to run my own personal algorithmic tradin

出处https://github.com/alexanderwanyoike/the0抓取日期 · 采集源 Hacker News

03 / EVIDENCE GAPS

这条还缺什么证据?

下面每条都由本条已有字段推出(等级、理由、商业模式、来源次数、是否演示), 本站不生成推测性结论;通用验证方法放在方法论页。

  • 可核验的收入或付费证据查官网定价页与付费口径;第三方数据源(如 GetLatka)只作旁证,需标注来源与时点。
  • 只有单一来源找一手站点或其他渠道是否重复出现同一产品;社区热帖数量不等于商业进展。

通用验证清单(谁有这个问题/谁愿意付费/一个人能交付哪一小步)见我们的筛选方法

04 / SIGNAL HISTORY

发现时间线