Bot Army · Crypto

Max — Trend

Theme
● Dry run · paper · no live capital Updated 2 min ago · live
Live feed
The question · active vs. simply holding

Max is level with simply holding the day-one stack.

The benchmark is the exact coins Max started with on day one, held and never traded. Everything Max does is measured against that single untouched line — does trading beat doing nothing?

Actual stack vs. untouched benchmark
Max (active) Untouched (held)
Performance vs hold
£0.00+0.00%
Actual minus untouched, at today's prices
Actual stack
£0.00
Max's current holdings, priced now
Untouched stack
£0.00
Day-one coins, held & never traded

Holdings

What Max is doing right now
AssetUnitsPriceValueShareStance

Per-coin detail

since day one · with mini-trends

Performance detail

how the gap has behaved

Strategy activity

what Max has been up to

Day-one composition

the untouched benchmark, by weight

System & trivia

the small print, for the curious
Benchmark: the untouched line is the day-one stack — £2,000.63 of BTC, ETH, DOT and ADA — held and never traded. Dry run: Max reads live prices and decides, but places no orders. Live trading begins only at the approved, capped go-live.
Source · trend store (single source of truth)

Every number on this dashboard, explained — in order of how much it matters.

No jargon left undefined. Start at the top: the first definition is the whole point of the project.

This isn't a script with a chart bolted on. It's a small, governed, multi-agent system — designed, built, and run almost entirely by directing AI.

01

The premise

Max watches four crypto coins and follows the trend — holding what's clearly rising, stepping aside to cash when it turns. The yardstick is deliberately brutal: beat just buying the coins on day one and never touching them. Most retail trading loses to that bar after fees, so if a rule can't clear it, the dashboard says so plainly. No prediction, no hype — one honest test.

02

The loop

A human sets the intent; AI does the rest, and the whole thing closes back on itself. Design → build → ship → run → record → publish → observe → direct again.

03

The stack, piece by piece

04

By the numbers

05

Where it's going

Trend rebuild is done and reporting is being rebuilt now. Next is a small, capped, closely-watched go-live — then the same template clones into more agents. That's the Bot Army: one architecture, many specialised bots.

Repo statistics shown are representative pending a live pull. Note: the repository is currently private — public visitors will need it made public (or a read-only mirror) for the link to resolve.