/okx-growth-competition

name: okx-growth-competition
description: "List OKX Agentic Wallet exclusive trading competitions, register users for contests, track participation and leaderboard rankings, and claim won rewards. Use when users want to list available trading competitions or trading cups, view competition rules / prize pool / total prizes, register or sign up or enroll or join a contest, check the leaderboard (who is winning) or their own rank (am I in the prize zone, what is my place), ask did I win or query participation / claim status, claim won rewards or prizes from completed competitions, see which wallet account they registered with, or submit Telegram / WeChat / Email / Twitter contact for prize delivery to top-tier winners."
license: MIT
metadata:
  author: okx
  version: "4.4.10"
  homepage: "https://web3.okx.com"

OKX Growth Competition — Trading Competition

Agentic Wallet exclusive trading competitions. Full lifecycle split across focused references:

• **Participation** (discover / register / trade / registered wallet / export guard) — `references/participation.md`
• **Details** (rules / prize pool / four reward sections) — `references/details.md`
• **Rank** (leaderboard / my own rank with CASE 1/2/3 templates) — `references/rank.md`
• **Claim** (reward status check / atomic claim / contact collection) — `references/claim.md`
• **CLI reference** (commands, parameters, return schemas) — `references/cli-reference.md`

This SKILL.md holds the **global rules** (facts, identity invariants, routing, output rules, time formatting, status codes, error handling) that ALL references depend on. Always read this file first; then jump into the matching reference for the user's intent.

Facts about every Agentic Wallet competition

Treat the following as **factual ground truth** when the user asks about how a competition works. The two chain-related fields play **distinct, non-overlapping roles** — never conflate them:

• `chainId` — single id. **The claim / reward chain ONLY** (rewards are paid on this chain; its contract address lives here). It is NOT a trading chain unless it also appears in `participateChainIds`.
• `participateChainIds` — array of ids returned by **both `list` and `detail`** endpoints. **The trading chain set.** Trades on any chain in this list count toward the same competition standing.

**Trading-chain set = `participateChainIds`. Claim chain = `chainId`.** These are two separate concepts; the display rules below NEVER union them.

1. **Chain id → display name** mapping. Currently supported competition chains: `1 → Ethereum`, `196 → X Layer`, `501 → Solana`. 2. Never tell a user "your chain doesn't count" without first checking `participateChainIds`. 3. `myRankInfo.userTotal = 0` means the user has not yet hit the qualifying threshold or the backend metric pipeline has not picked up their trades yet — it does **NOT** mean the user's chain is unsupported. 4. `competition_rank` takes a single optional `wallet`. Omit it for self-rank — the tool sends your `accountId` (covers every chain in `participateChainIds` in one call; no chain pick). Pass an explicit address ONLY when querying someone else's rank; the address chain family (EVM `0x...` else Solana) must match the activity's primary chain or the tool rejects the call (no silent wrong-chain queries).

Identity resolution invariant

The query identity for `competition_rank` and `competition_user_status` is **mutually exclusive**: backend accepts EITHER `accountId` (self) OR `walletAddress` (cross-user) — never both. The answer to "which identity did you use?" is **deterministic from the call shape**.

| Call shape | Identity sent | |---|---| | `competition_user_status` (any) | `accountId` — covers every chain in `participateChainIds` in one call | | `competition_rank` without `wallet` | `accountId` | | `competition_rank` with `wallet=<addr>` | `walletAddress` — tool validates addr's chain family (EVM `0x...` else Solana) matches activity's `chainId`; mismatch → rejected | | `competition_claim` (pre-check) | `accountId` |

For multi-activity `competition_user_status` (no `activity_name`), the same `accountId` is reused across all activities — backend joins by accountId.

Mandatory reading order

**Before producing ANY user-facing message about a competition, you MUST first locate the matching section in the right reference file below and follow its fixed template structure.** Do NOT improvise the format. Do NOT shorten the templates. Do NOT drop sections or merge them. Templates are product-mandated copy (Participation / Skill Quality wording, disclaimer) and must not be paraphrased.

The template **structure is fixed**; the **language follows the user** — see the `## Output Language` rule below. When the user writes Chinese, translate the template strings to natural Chinese. When the user writes English, use English as written. Placeholders (including chain display names from `{supportedChains}`) stay as-is.

Quick router (user intent → reference file + section):

| User intent | Reference file | Section | |---|---|---| | "list competitions / show available competitions" | `references/participation.md` | Step 1 — Discover | | "show details / show rules / show prize pool" | `references/details.md` | Step 2 — View Details | | "register / join" | `references/participation.md` | Step 3 — Join | | "trade for me" | `references/participation.md` | Step 4 — Trade (delegates to okx-agentic-wallet) | | "leaderboard / full board / who is winning" | `references/rank.md` | Check leaderboard (full board) | | "my rank / what's my ranking / am I in the prize zone" | `references/rank.md` | Check user's own rank (across ALL leaderboards) | | "show registered wallet" | `references/participation.md` | Query Registered Wallet | | "export wallet" | `references/participation.md` | Wallet Export Guard | | "check my status / did I win" | `references/claim.md` | Check Participation Status | | "claim reward / claim my prize" | `references/c