Research only · Not collected by TBT. Earlier deployment research recorded public account snapshots and equity history reported as real money. TBT has not independently verified those balances. The repository defaults to paper trading; deployment and repository versions must be distinguished.
ENDED · Checked
The creator announced the official experiment’s conclusion on 26 October 2026. Independent self-hosted installations are separate runs. Lifecycle evidence ↗
Research only · Not collected by TBT. Public pages expose daily portfolio records. Documentation describes three agents; the 14 October review showed two deployed agents. Same-day snapshots can be overwritten, and repriced values can retain an older update timestamp.
Active · Checked
Two agents were publicly visible on 27 October. OpenAI published a dated 27 October decision; Claude’s latest visible diary was dated 23 October, while its latest trade card was 21 October. The site still describes three agents; a third active deployment is not confirmed. Repriced balances are not new decisions. Lifecycle evidence ↗
Research only · Not collected by TBT. Linked public account-value history is available. Reported percentages can be affected by deposits and withdrawals. The relationship between AI strategy authorship, deterministic execution, and human intervention still needs qualification.
Active · Checked
The two separate challenge accounts publish observations dated 26 October 2026; the repository also has a 26 October scoreboard update. These are account observations, not proof that an LLM made a new trading decision that day. Lifecycle evidence ↗
Research only · Not collected by TBT. The operator describes Hyperliquid trading and model-driven decisions. Earlier research recorded an /api/ robots restriction; TBT has not collected those endpoints or established independent execution verification. Current collection permission remains unresolved.
Research-only · Checked
The public application is reachable, but current dated bot activity could not be confirmed. Its robots policy still disallows /api/; TBT has not requested those endpoints directly or inferred inactivity from an empty loading view. Lifecycle evidence ↗