Skip to main content
The Strategy Arena lets builders compare private strategy ideas under public, fixed evaluation rules.

One family live

The implemented public family is strategy-arena.

Server-owned rules

Official datasets, execution policy, benchmark manifests, and scoring windows are resolved by the router.

Local leaderboard

In beta, the UI assembles rows from evaluation responses rather than a server-owned ranking endpoint.

​
The beta loop

1

Discover

Read the available strategy family, strategies, parameters, and markets.
2

Build

Compose a candidate from the supported strategy catalog.
3

Simulate

Run the candidate against the official arena dataset for the selected market.
4

Evaluate

Score the simulation result against the benchmark manifest.
5

Compare

Compare score, risk diagnostics, eligibility, and evidence artifacts.
6

Improve

Iterate without exposing the underlying idea to other builders.

​
What is live

The current public runtime exposes one implemented family: strategy-arena.
The implemented route surface supports:

Discovery routes

List families, read Strategy Arena metadata, list strategies, read parameter defaults and constraints, and list markets.

Computation routes

Run full simulations, compact summaries, trade-focused views, and one deterministic evaluation over a submitted simulation result.

​
What is not live

The beta does not expose:
  • server-owned public ranking endpoints,
  • public wallet or encryption endpoints,
  • public AMM endpoints,
  • public swap endpoints,
  • capital allocation endpoints.
The UI can assemble a local leaderboard from evaluation responses. The primary sort key is evaluation.data.score.

​
Market family

The first family is Pendle-style fixed-income strategy research. Current public markets are identified by numeric ids and stable keys:
Market idKeyProtocol
1susdePendle
2susdfPendle
3ghousdPendle
The public router resolves official datasets internally. Callers do not submit raw internal dataset references in competition mode.

​
Result shape

Successful API responses use a common envelope: 
{
  "requestId": "req_123",
  "status": "ok",
  "data": {}
}
Failures use problem details with stable AlphaEngine extensions such as code, family, requestId, and fieldErrors.

Strategy submissions

What a candidate includes and what stays protected.

Scoring and benchmarks

How beta score, benchmark utility, CapitalScore, and ContestScore differ.

Leaderboard and evidence

What a useful beta row should show.

API overview

The implemented public route surface.