mrkeyoor.com_
Fri 02 Oct 14:58 UTC
AI Toolsevaluationupdated 02 Oct 2026

flybook review

Stonkfly feeds Coinbase price charts into a simulated fruit-fly nervous system, then turns selected neural activity into buy, sell, or hold proposals. It can paper trade or place guarded spot orders, but the project states plainly that profitable learning has not been demonstrated.

Verdict

Our run passed 41 tests and built in 5 seconds, but pip-audit reported 20 known vulnerabilities and the project has not demonstrated profitable learning. Use Stonkfly as a carefully documented paper-trading and connectome experiment. Do not fund it as though the biological scale, the passing suite, or the 20 USDC drawdown trigger proves a trading edge or caps your loss.

We ran it

Lab card: what happened when we ran flybookScreenshot of flybook (github.com/flybook-git/flybook)
Install✓ · 60s151 packages · 489 MB
Build✓ · 5s
Tests✓ · 47s41 passed · 0 failed · 1 skipped of 41 (pytest)
Known vulns20(pip-audit)
Repo45 files~3,374 lines of source · 1.5 MB · 1 CI workflows · tests dir

Answers from our run

Does flybook build from source?

Dependencies installed in 60 seconds (151 packages), and the build succeeded in 5 seconds. We cloned commit 78ef3e0 into a clean Debian container with 3 CPUs and no project-specific setup.

Do flybook's tests pass?

Yes: 41 of 41 passed when we ran the project's own test command (pytest). Some failures need services or credentials a bare container does not have.

Does flybook have known vulnerabilities in its dependencies?

pip-audit flagged 20 known advisories in the dependency tree at the time of our run.

Who should not use flybook?

Anyone seeking a proven trading bot: the model documentation says no profitable learning or strategy improvement has been demonstrated.

What are the alternatives to flybook?

Freqtrade, Jesse, Brian 2. Our run passed 41 tests and built in 5 seconds, but pip-audit reported 20 known vulnerabilities and the project has not demonstrated profitable learning.

Setup3/560-second install, then a 1.1 GB dataset and native compiler
Docs5/5Model assumptions, live limits, and recovery steps are explicit
Community2/5227 stars, no open issues or PRs, and little history yet
Maturity2/5v0.1.0 code with no release and no demonstrated profitable learning

Who it’s for

Researchers who want a documented experiment connecting a large biological graph to a live market feed.
Python developers studying guarded Coinbase order execution, resumable state, and audit logs.
Curious builders willing to start in paper mode and treat every result as an experiment rather than a strategy.
Neural-simulation researchers with 16 GB of RAM and room for several gigabytes of data.

Who it’s NOT for

Anyone seeking a proven trading bot: the model documentation says no profitable learning or strategy improvement has been demonstrated.
Users who read the 20 USDC drawdown stop as a loss cap: it stops new orders but does not liquidate holdings or prevent further losses.
Operators unwilling to isolate live funds: the instructions require a dedicated Coinbase portfolio, a portfolio-scoped key, and no manual or competing bot activity.
Small machines or quick demos: preparation downloads about 1.1 GB, several more gigabytes are needed, and 16 GB RAM is recommended.
Buyers who require a clean dependency audit: our pip-audit found 20 known vulnerabilities at commit 78ef3e0.

Setup reality

Our sandbox installed commit 78ef3e0 in 60 seconds: 151 packages used 489 MB. The build passed in 5 seconds. Pytest finished in 47 seconds with 41 passed, 0 failed, and 1 skipped in the reported 41-test run; pip-audit found 20 known vulnerabilities.

Paper mode needs no key, but preparation downloads about 1.1 GB of connectome data and the README recommends 16 GB RAM. Live mode needs a dedicated Coinbase Advanced portfolio, an ECDSA key limited to View and Trade, local environment settings, and an explicit live-trading opt-in.

The worker must stay running, and the local ledger is authoritative after a crash. The repository has one CI workflow and a tests directory but no Dockerfile, so you supply Python 3.11, a C++17 compiler, storage, and the host process.

Passing 41 tests does not prove the fly can trade

Stonkfly is unusually direct about the line between working software and a working strategy. It retains a large fly connectome, sends chart pixels into mapped visual cells, reads activity from selected descending neurons, and converts that signal into buy, sell, or hold. Coinbase integration can place a real spot order. None of those facts demonstrates that the network learns a profitable policy, and the project's own model document says it has not done so.

That distinction should govern your decision. This is an experimental neural controller with serious execution controls, not evidence that fly anatomy contains market insight. Paper mode starts with public BTC-USDC data and a $100 simulated balance. A fixed decoder turns a firing-rate difference into a proposal, while a separate guard may reject it for budget, inventory, price, time, or account-state reasons. The guard never replaces the neural choice with a smarter trade.

166,700 neurons receive pixels instead of price indicators

The retained MaleCNS v1.0 graph contains 166,700 neurons and about 25.6 million directed connections. Stonkfly renders a 320 by 180 price chart, then maps luminance into 3,335 R1-R6 cells and color proxies into 811 R8 cells. The simulator does not receive moving averages, balances, profit, or raw price columns as sensory inputs. That makes the experiment easier to describe honestly: a neural graph sees an image and emits activity.

The biological claims stop well before a living fly. Documentation calls the neuron model approximate, lists simplified transmitter signs, and identifies the display adapter as unvalidated physiology. Each market observation advances 500 ms of neural time even though wall observations are at least 60 seconds apart. Positive and negative portfolio changes stimulate selected dopamine cells, but those engineered signals are not modeled pleasure, pain, or proof of causal credit assignment.

What happened when we ran it

Our sandbox installed commit 78ef3e0 in 60 seconds. It added 151 packages and occupied 489 MB on disk. The build succeeded in 5 seconds, then pytest completed in 47 seconds with 41 passed, 0 failed, and 1 skipped in the supplied 41-test report. Pip-audit found 20 known vulnerabilities. A buyer should resolve or accept those advisories before placing credentials beside the environment.

The checkout itself had 45 files, roughly 3,374 lines of source, and measured 1.5 MB. It included one CI workflow and a tests directory, but no Dockerfile. Our run checked installation, build, and the supplied tests in an unprivileged Python 3.12 Bookworm container with 3 CPUs, 8 GB RAM, and no secrets. It did not demonstrate trading returns, exchange reliability, neural realism, or safe handling of live money.

A 1.1 GB dataset follows the 60-second install

The README calls for Python 3.11, a C++17 compiler, and macOS or Linux. python -m stonkfly prepare then downloads about 1.1 GB of upstream connectome data, verifies locked hashes, and builds the graph. The operations guide says to allow several additional gigabytes for dependencies, derived data, and two checkpoints. It recommends 16 GB RAM, twice the memory available in our lab container.

Paper mode needs no Coinbase credential and stores logs, rendered sensory images, and resumable brain state under a local run directory. The process must stay running for continued observations. SQLite is the authority after a crash, while alternating checkpoints preserve neural state. A STOP file prevents future submissions, though an order already sent as fill-or-kill may still complete. Recovery from an uncertain exchange response requires human inspection rather than an automatic retry.

The 20 USDC drawdown trigger does not cap loss

Live setup requires a dedicated Coinbase Advanced portfolio funded with at most 100 USDC at initialization. The API key must use ECDSA, allow View and Trade, disable Transfer, and be scoped to that portfolio. Live execution also needs an environment acknowledgment, the --live flag, and a preflight command. These layers reduce accidental activation. They do not make the experiment suitable for unattended savings.

Each buy is limited to 10 USDC including a fee reserve, with no borrowing, shorting, transfers, or margin-trading actions exposed. The worker permits at most 24 order attempts per UTC day. At a 20 USDC drawdown it stops opening new orders, but it does not sell existing holdings. Their value can keep falling, and a move between observations can pass the threshold. The documentation says the experiment can lose its entire allocated balance.

A September push and zero open items offer little history

GitHub redirected the requested repository to flybook-git/flybook, which showed 227 stars, no open issues or pull requests, and a last push on September 10, 2026. There was no GitHub release returned. The Python package identifies itself as version 0.1.0. Those facts describe a young codebase with a quiet tracker, not a long operating record.

Stonkfly earns attention because it labels its assumptions and failure boundaries with unusual care. The valuable artifact is the experiment design, paper mode, audit trail, and guarded exchange bridge. The missing artifact is the one a trader needs most: controlled evidence of profitable learning. Run it on paper if the connectome question interests you. Choose Freqtrade or Jesse when your job is to test an explicit trading strategy, and choose Brian 2 when exchange plumbing would only muddy the neural research.

Alternatives

ProjectWhat it isPick it when
Freqtrade gh↗A Python crypto-trading bot built around conventional strategies, backtesting, and exchange operation.pick this instead when strategy testing and normal trading workflows matter more than connectome research.
JesseA Python framework for researching and running crypto trading strategies.pick this instead when you want to write an explicit strategy and evaluate it with familiar trading tools.
Brian 2A Python simulator for spiking neural networks without a built-in trading account connection.pick this instead when the neural model itself is the research subject and exchange execution is a distraction.

What people are saying

  1. [velocity-scout] flybook-git/Main

Sources

  1. Stonkfly README
  2. Stonkfly model and evidence
  3. Stonkfly operation and recovery
  4. Stonkfly repository facts

More ai tools reviews

xialingguo-ip · reelbench-skills · SoL-Pi · crypto-rag · anything2explainer · cek-probe-model · the whole board →