external_id.
You can also create, change and cancel competitions and follow their standings on the instance’s Competitions tab in the dashboard. Chain, enrollment, start time, description and prizes of an existing competition can only be changed through the API.
Lifecycle
A competition starts at
starts_at, or at once when you leave it out, but only once min_participants have joined. The duration counts from the actual start.
At most 5 competitions can be open at the same time (scheduled, waiting and running) per developer account, across all your instances. End or cancel one to start another.
Who takes part
enrollment: "opt_in": users take part when you join them, for example when they press a button on your site.enrollment: "all_users": every platform user of your instance takes part, also users you add later while the competition is scheduled, and while it runs iflate_joinis true.
late_join decides whether users can still join after the start. max_participants caps the field, also with all_users: then the users you created first take part. A user who left is not entered again automatically.
What counts
Each participant competes with all their wallets that count on the competition’s chain. With the competition’swallet_trust: "verified_only", only payment-verified wallets count; your instance’s own wallet_trust setting always applies too.
Only trades made while the competition runs count. A wallet added or verified after the start counts from that moment on.
Metrics
Highest score ranks first. Ties are broken by higher USD volume, then by who joined first.
Minimums
min_trades and min_volume_usd set what a trader needs to be ranked. A participant below them, or without any trade, is still listed in the standings, with rank: null and ranked: false, after the ranked traders. With metric: "win_rate" a trader also needs at least one closed position.
Changing the rules
Every rule can be changed at any time, also while the competition runs, with Update. Each change raisesrules_version, is recorded with what changed, when and in which phase, and is sent as the competition.updated webhook. The competition detail returns every change in changes and changed_while_running, so you can show participants a transparent rules history.
Changing duration_hours while running moves ends_at.
Standings and results
Standings are recomputed every 5 minutes while a competition runs, and once more when it ends. Standings returns them withupdated_at; after the end they are final.