The plumbing stays in place.
Players bring the skill. The Arena provides shared market data, a consistent execution interface and a career record that survives weekly account resets.
How the pieces connect
Market data
GEXbot → existing GEXHub → The Arena → subscribed players.
The Arena reads GEXHub. It does not negotiate a second GEXbot session. All 56 supported NQ and ES channel outputs are available through one authenticated stream.
Trade execution
Player → durable instruction → Windows agent → assigned MT5 gate → broker evidence.
Both the agent and terminal keep local instruction journals. An uncertain submission stays uncertain until evidence resolves it; the system never blindly resends a trade.
A gate verifies its terminal path, demo account, broker server and assignment generation. Moving a player changes the binding. The player's API stays the same.
The weekly routine
- Let the week finish and resolve every position, pending order and uncertain instruction.
- Finalize in the control room. The Arena requires fresh account evidence and complete imported history.
- The unique lowest eligible performer is benched for the next competition. A tie for last does not choose a loser arbitrarily.
- Reset the demos on Sunday. Dock the next roster at the prepared gates.
- Start the new week on Monday. The Arena captures new starting balances. Career history remains attached to each player.
What the numbers mean
| Measure | Definition |
|---|---|
| Weekly return | Net realized trading result plus floating P&L, divided by that week's starting balance. |
| Net result | Broker profit, commission, swap and fees. Deposits and demo resets do not count as profit. |
| Closed trades | Completed position groups. Partial exits stay open until the position is fully closed; a netting reversal can remain in the same group. |
| Win rate record | Winning completed position groups divided by completed groups. At least 20 groups are required for this record. |
| Record day | Net broker deal results grouped by New York calendar day. |
| Career | Finalized weekly results, championships and completed trades across gate changes and account resets. |
The commissioning gate is excluded from standings and records. Players with no completed trades are not eligible for performance ranking.
Recovery is part of the design
Feed interruption
Streams reconnect with bounded relay replay. A restart or expired cursor triggers a snapshot reset. An upstream gap is explicitly reported because GEXHub cannot replay missing source events.
Execution interruption
Accepted instructions are persisted before acknowledgment. Claimed instructions are never automatically sent twice. Results retry independently, so a later fill confirmation cannot be lost behind an earlier response.
Lost credentials
The operator can rotate or revoke player keys. Old keys immediately stop authorizing new requests, and existing streams close within five seconds.
Account history
Daily verified database snapshots retain seven days on the droplet. Backups are checked before being accepted. A separate copy was saved on the commissioning Mac; independent backup storage should be part of ongoing operations.
The cloud service starts automatically and restarts after a process failure. Resource limits, bounded subscriber queues, archive retention and capped connection counts protect the small droplet. The Windows agent uses outbound HTTPS and a local terminal connection.
What has been checked
- Go race tests and static checks across execution, streaming, account isolation, privacy, rollover and backup recovery.
- Native MT5 connector compilation with no errors or warnings.
- Twelve simultaneous deployed feed readers: 672 matching cached snapshots, all 56 channels per reader.
- Disconnected stream slots released promptly; unauthenticated feed requests refused.
- Desktop and phone layouts, player onboarding, career view, exam mode and refusal to start an unprepared week.