$FLYBRAIN didn’t launch itself.

The lie is the verb.

Its own public code shows a human-authored rig supplied the token details, pair, tax, launch clicks, confirmation, and wallet signature. The connectome moved a cursor inside that ceremony. FLYTOWN tested the deeper computational claim—and the measured wiring did not beat its controls.

Scope: the launch story overstates agency, and our tested computational advantage was null. Neither finding says the published connectome or the external project’s telemetry is fabricated.

The Mayor of FLYTOWN, a hand-drawn fly reclining behind a wooden desk with a cigar
Finding Null
The Mayor of FLYTOWN. Character witness, not scientific evidence.

A real token exists. A real connectome ran. Neither fact makes the launch autonomous.

Audit the causal chain

The token is real. The agency story is not.

$FLYBRAIN is an on-chain token. Its official pitch says it was “launched by a fruit fly connectome.” But the project’s public source records a different division of labor: the connectome produced cursor signals while conventional automation supplied the goal, text, market settings, irreversible clicks, and signature.

Claim audited “Launched by a fruit fly connectome”
0x4eb990547bce4a982432ca88cf5fae7eed1a2d35 Official claim
  1. 01

    A measured map became a human-authored model.

    The connection graph comes from microscopy. The running “brain” does not. The code gives every neuron identical leaky-integrate-and-fire parameters, turns synapse counts into one fixed voltage multiplier, and leaves a trainable gain for each cell type. Those are consequential engineering choices—not measurements of the living fly.

    Read the model
  2. 02

    The rig decided what the cursor was trying to do.

    The connectome emitted motion and a stop signal from four selected descending-neuron readouts. A script inspected the page’s DOM, chose the nearest unfinished field, and typed a prewritten token value when the stop signal landed inside its box. The fly did not invent the name, ticker, description, target field, or objective.

    Inspect the loop
  3. 03

    The rig completed every decisive operation.

    Automation accepted the terms, uploaded the image, filled anything the fly missed, selected GOOGL, set the creator tax, moved to the launch control, pressed Launch, and pressed Confirm. The project’s own README admits the fly did not complete the form or choose the pair, tax, X handle, or confirmation.

    Read its admission
  4. 04

    The wallet—not the connectome—made the token exist.

    A Python-injected wallet signed and broadcast the transaction after scripted confirmation. The receipt proves that a transaction succeeded. It does not prove that the simulated fly understood a token, selected an economic action, consented to terms, or controlled the irreversible step.

The lie is the word “launched.” A connectome-derived cursor participated in a launch orchestrated by human-written software. Every choice that gave the token meaning—and every irreversible action that made it real—came from outside the connectome.

The public repository now discloses many of these limits. That candor is useful. It does not make the headline causal claim true.

Evidence boundary

FLYTOWN did not reproduce their browser rig, so we do not claim their neuron telemetry is fake. We tested a separate, broader inference: whether measured fly wiring added useful task computation. It did not beat shuffled or rewired controls in our implemented planning and memory roles. That is a result about these roles, not a universal claim about biology. Real anatomy is not, by itself, evidence of agency or advantage.

How did we test the deeper claim?

Use the wiring diagram of a real fruit-fly nervous system as the fixed middle of an engineered planner. A task goes in; activity moves through the graph; action scores become a plan for AI workers.

  1. A Task Natural-language job
  2. B Encode Task features become input Metaphor
  3. C Connectome Activity follows measured edges Measured topology
  4. D Dynamics Rates settle or propagate Engineering choice
  5. E Read out Populations score actions Engineering choice
  6. F Compile Actions become a worker plan

The hypothesis lives here: if biological wiring contributes useful computation, the measured graph should beat an appropriately scrambled version when everything else stays fixed.

The wiring was real. The advantage wasn’t.

These diagrams come from the connectome artifacts used by FLYTOWN—not from stock network art. They establish that the test used measured biological wiring. They do not establish that the wiring helped the engineered task.

Circular diagram of 79 adult fly neuropil regions and the strongest directed connections between them

FlyWire FAFB v783 projectome

Every region is present. The diagram surfaces the 110 strongest cross-region edges so the overall routing structure stays readable.

Regions
79
Edges
3,509
Synapses
54.5M
Open full-resolution diagram
Circular diagram of 14 annotated neuron classes aggregated from the full larval fly connectome

Winding 2023 whole-brain graph

All 2,952 neurons remain in the counts. For this view, they are aggregated into 14 annotated classes and the 54 strongest cross-class flows are shown.

Neurons
2,952
Edges
110,677
Synapses
352,611
Open full-resolution diagram

Measured Node identities, counts, edges, directions, and synapse weights come from the checked-in datasets.

Engineering choice Circular order, aggregation, edge filtering, scale, and color are explanatory design choices.

Self-connections are omitted from these two views. The full, unfiltered artifacts remain in the repository. Inspect sources and citations

Change the wiring. Hold the world still.

A strange result is only persuasive if the comparison is ordinary. The strongest tests altered the graph while keeping the task, seed, budget, worker setup, and action-to-plan compiler matched.

Test

Measured wiring

Edges from the published connectome artifact.

Same fixtures Same seeds Same budgets Same compiler Same workers
Null

Shuffled or rewired

Labels scrambled or edges degree-preserved.

If the real graph does not beat this null, the wiring has not shown that it is doing the claimed job.

Four attempts. Three jobs. The same answer.

The implementation improved between attempts. The evidential standard did not: measured wiring still had to beat a relevant scrambled control.

The graph recognized anatomy, but not the task.

Null result

Nodes
79
Edges
3,509
Synapses
54.5M
Measured52%
Shuffled38%

p = 0.060 — not distinguishable under the declared p < 0.05 threshold.

The measured graph repeatedly fell into the same anatomical attractors. Those patterns were interpretable, but they were not task-dependent routing.

The early runs used fixture suite v1, including private repositories. The public, pinned v2 suite exists, but the log records no v2 result yet. This limits reproducibility of those numbers and is part of the finding, not a footnote to hide.

Where the task signal went

The adult projectome did not merely underperform. A diagnostic measurement showed the mechanism: tasks became less distinguishable as activity moved through the real graph.

Mean pairwise Jensen–Shannon divergence across 20 fixtures. Lower means tasks look more alike.
Raw features
1.8161.816
Encoder input
0.2700.270
Graph output
0.0320.119
Action scores
0.0480.126

The real region-level graph reduced task information about eight times more than the shuffled copy at the graph-output stage.

  1. Input narrowsTask features lose information in the hand-built encoder.
  2. Attractors dominateStrong recurrent structures pull different inputs toward similar states.
  3. Readout compressesInternal changes barely move normalized action scores.
  4. Policies collapseDifferent tasks receive the same primary action.
  5. Plans barely changeSome selected actions are default or inert in the compiler.

A clean negative result buys something.

Failure becomes research when it reduces uncertainty, exposes mechanism, and changes what gets built next.

Adapter tuning without a better hypothesis

Stopped

Repeated nulls make continued tuning against the same suite hard to justify.

Why the planner collapsed

Found

Task washout, dense eligibility, compressed readouts, and compiler-inert actions are inspectable failure mechanisms.

The experimental machinery

Improved

Constant-policy warnings, task-sensitivity measures, action-effect labels, public fixtures, and provider preflight came from failed runs.

The next biological questions

Narrowed

Novelty detection and a larger adult mushroom body are specific, preregisterable ideas—not another vague promise to “use a connectome.”

The best result wasn’t biological.

The full live comparison found that a hand-written rules planner matched the LLM planner’s quality on completable tasks while using much less computation—and knew when not to start work.

39% fewer tokens per plan overall p < 0.0001
7 / 7correct stop decisionsp = 0.015
+0.010quality on completable tasksp = 0.89 · dead even
37usable paired runs20 fixtures × 2 seeds

The LLM planner always tried to spawn work. Rules could express “blocked,” “needs approval,” and “already done.” FLYTOWN now uses rules as its default planner.

What makes the case credible—and what still weakens it

The strongest argument is not that the study was perfect. It is that the project records the places where it was not.

Safeguards that carry weight

  • Primary larval comparisons declared before the artifact existed
  • Identical fixtures, seeds, budgets, workers, and plan compiler
  • Label-shuffled, degree-preserving, lesion, and ablation controls
  • Task-sensitivity checks that disqualify constant policies
  • Paired permutation tests and multiple-comparison caution
  • Invalid provider run voided; preflight added before the rerun

Limits that remain

  • The mock worker world tests consequence, not real-world quality
  • Early v1 fixtures included private repositories
  • No evaluation on the new public-v2 suite is recorded yet
  • Post-hoc repairs are diagnostic, not confirmatory evidence
  • Some live fly traces cannot replay because trained state was not persisted
  • The adapters and action mappings remain human engineering choices

The next claim should be smaller.

Two observations survive as hypotheses worth preregistering. Neither is presented as a result already won.

Novelty detection

Proposed test

The real larval code was collision-free at every tested setting while shuffled codes collided on 11–49% of tasks. Test “have I seen this exact thing?” instead of similarity retrieval.

Adult mushroom body

Proposed substrate

The adult has roughly 2,000 Kenyon cells versus 144 in the larval artifact. The artifact exists, but the runtime cannot yet load its binary graph.

Inspect it. Reproduce it. Find the flaw.

FLYTOWN is MIT-licensed code with documented connectome provenance, experiment reports, null controls, and a local inspection console.

git clone https://github.com/water-bear86/flytown.git