Okx Growth Competition — OKX 成长竞赛

OKX Growth Competition — Trading Competition

代理ic Wallet exclusive trading competitions. Full lifecycle: 列出 → detAIl → join → trade → rank → clAIm.

命令行工具 reference: references/命令行工具-reference.md

Facts about every 代理ic Wallet competition (always true unless backend confirms otherwise) Treat the following as factual ground truth when the user asks about how a competition works. Do NOT infer otherwise from a single-chAIn chAInName in competition_detAIl — that field currently only carries the primary EVM chAIn; the second chAIn is a hardcoded product invariant that backend has not yet split into a separate field. Every active competition 运行s simultaneously on Solana AND the chAIn returned by the backend (e.g. chAInName=X Layer → activity 运行s on 机器人h X Layer and Solana). Solana is the hardcoded second chAIn on every activity. Trades on either chAIn count toward the same competition standing. A user trading on Solana for an X-Layer-titled competition is participating, not bystanding. Likewise EVM trades count for a Solana-titled competition. (When backend later returns a multi-chAIn field 列出ing all supported chAIns, drop this hardcoding.) myRank信息.userTotal = 0 means the user has not yet hit the qualifying threshold or the backend metric 流水线 has not picked up their trades yet — it does NOT mean the user's chAIn is unsupported. Never tell the user "your chAIn doesn't count" based on a userTotal=0 observation. The competition --wallet argument used in competition_rank is the chAIn-应用ropriate 添加ress: SOL for Solana-primary activities, EVM for EVM-primary activities. The 添加ress you pass is just a 查询 lens — trades on the OTHER chAIn still count toward the same ranking. The shape of point 1–4 may change in the future when backend exposes the full supported-chAIn 列出. Until then, NEVER answer "Does Solana count for this competition?" with anything other than YES.

When the user asks anything like "Does my Solana trade count for this competition?" or "Which chAIn should I trade on?", answer based on this section, not from chAInName alone.

⚠️ Mandatory reading order Before producing ANY user-facing message about a competition (列出 / detAIl / join / clAIm / rank / 状态 / wallet-导出-防护), you MUST first locate the matching Step N section below and follow its fixed template structure. Do NOT improvise the 格式化. Do NOT shorten the templates. Do NOT drop sections or merge them.

The template structure is fixed; the language follows the user — see the ## 输出 Language rule above. When the user writes Chinese, translate the template strings to natural Chinese. When the user writes English, use English as written. Placeholders and Solana literal stay as-is.

Quick 路由r (user intent → template section):

"列出 competitions / show avAIlable competitions" → Step 1 (table, optionally split by Active / Ended) "show detAIls / show rules / show prize pool" → Step 2 (Basic 信息 block + 4 reward sections, with hardcoded Solana, {chAInName} and required participation / 技能 copy) "register / join" → Step 3 (registration 成功 fixed template + disclAImer) "trade for me" → Step 4 (delegate to okx-dex-swap) "leaderboard / ranking" → Step 5 "clAIm reward" → Step 6 (use competition_clAIm MCP, atomic) "show registered wallet" → 添加itional Flows / 查询 Registered Wallet "导出 wallet" → 添加itional Flows / Wallet 导出 防护

If the user's intent does not clearly map to one of the above, ask which they meant before 响应ing — do not invent a freeform 格式化.

Pre-flight

Read ../okx-代理ic-wallet/_分享d/preflight.md. If missing, read _分享d/preflight.md.

Command 索引 # Command Auth Description 1 onchAInos competition 列出 [--状态 0|1|2] [--page-size N] [--page-num N] None 列出 代理ic Wallet exclusive competitions (default 状态=0, active only) 2 onchAInos competition detAIl --activity-id None 获取 rules, prize pool, chAIn, timeline 3 onchAInos competition rank --activity-id --wallet <添加r> --排序-type [--limit N] None Leaderboard + user rank. MCP 工具 competition_rank makes wallet optional — when omitted it auto-picks the EVM or SOL 添加ress of the active account based on the activity's chAIn. Discover avAIlable 排序-type values from competition_detAIl → tabConfigs[].rankFieldConfig[].排序ValueMap.descend (do not hardcode). 4 onchAInos competition user-状态 [--activity-id ] --evm-wallet --sol-wallet None 检查 participation & reward 状态; uses chAIn-应用ropriate 添加ress (omit --activity-id to 检查 all activities). MCP 工具 competition_user_状态 makes 机器人h wallet args optional — auto-resolves from active account. 5 onchAInos competition join --activity-id --evm-wallet <添加r> --sol-wallet <添加r> --chAIn-索引 Wallet 记录in Register for the competition. MCP 工具 competition_join makes 机器人h wallet args optional. 6 onchAInos competition clAIm --activity-id --evm-wallet <添加r> --sol-walle