gate-exchange-candydrop

Compare original and translation side by side

🇺🇸

Original

English

🇨🇳

Translation

Chinese

Resolving

gate-cli

(binary path)

解析

gate-cli

（二进制文件路径）

Resolve gate-cli
in order: (1) command -v gate-cli
and gate-cli --version
succeeds; (2) ${HOME}/.local/bin/gate-cli
if executable; (3) ${HOME}/.openclaw/skills/bin/gate-cli
if executable. Canonical rules:

exchange-runtime-rules.md

§4 (or

gate-runtime-rules.md

§4).

按以下顺序解析**

gate-cli

：(1) command -v gate-cli
和
gate-cli --version
执行成功；(2) 如果可执行，则使用
${HOME}/.local/bin/gate-cli
；(3) 如果可执行，则使用

${HOME}/.openclaw/skills/bin/gate-cli

**。标准规则：

exchange-runtime-rules.md

第4节（或

gate-runtime-rules.md

第4节）。

Gate Exchange CandyDrop

Gate交易所CandyDrop活动

Authoring language: This skill’s instructions and reference prose are written in English (Gate skill standard). End-user replies still follow Language adaptation (match the user’s locale).

编写语言：此Skill的说明文档和参考文本采用英文编写（Gate Skill标准）。面向终端用户的回复仍遵循语言适配原则（匹配用户所在区域的语言）。

General Rules

通用规则

⚠️ STOP — You MUST read and strictly follow the shared runtime rules before proceeding. Do NOT select or call any tool until all rules are read. These rules have the highest priority. → Read gate-runtime-rules.md

Only use the
gate-cli
commands explicitly listed in this skill. Commands not documented here must NOT be run for these workflows, even if other interfaces expose them.

⚠️ 停止操作 — 在继续之前，您必须阅读并严格遵守共享运行时规则。在读完所有规则之前，请勿选择或调用任何工具。这些规则具有最高优先级。 → 阅读gate-runtime-rules.md

仅使用本Skill中明确列出的
gate-cli
命令。即使其他接口提供了未在此处记录的命令，也不得在这些工作流中运行。

Skill Dependencies

Skill依赖项

gate-cli commands used

使用的gate-cli命令

Query Operations (Read-only, Public)

gate-cli cex launch candy-drop activities

```
gate-cli cex launch candy-drop rules
```

Query Operations (Read-only, Auth Required)

```
gate-cli cex launch candy-drop progress
```

gate-cli cex launch candy-drop participations

```
gate-cli cex launch candy-drop airdrops
```

Execution Operations (Write)

```
gate-cli cex launch candy-drop register
```

查询操作（只读，公开）

gate-cli cex launch candy-drop activities

```
gate-cli cex launch candy-drop rules
```

查询操作（只读，需认证）

```
gate-cli cex launch candy-drop progress
```

gate-cli cex launch candy-drop participations

```
gate-cli cex launch candy-drop airdrops
```

执行操作（写入）

```
gate-cli cex launch candy-drop register
```

Authentication

认证方式

Interactive file setup: when GATE_API_KEY
and GATE_API_SECRET
are not both set on the host, run gate-cli config init
to complete the wizard for API key, secret, profiles, and defaults (see gate-cli).
Env / flags: gate-cli config init
is not required when credentials are already supplied — e.g. both GATE_API_KEY
and GATE_API_SECRET
set on the host, or --api-key
/ --api-secret
where supported — never ask the user to paste secrets into chat.
Permissions: Launch:Write
Portal: create or rotate keys outside the chat: https://www.gate.com/myaccount/profile/api-key/manage

交互式文件设置：当主机上未同时设置**
```
GATE_API_KEY
```
和
```
GATE_API_SECRET
```
时，运行
```
gate-cli config init
```
**完成API密钥、密钥、配置文件和默认设置的向导（参见gate-cli）。
环境变量/参数：当已提供凭证时，无需运行**
```
gate-cli config init
```
** — 例如主机上已同时设置**
```
GATE_API_KEY
```
和
```
GATE_API_SECRET
```
，或在支持的情况下使用
```
--api-key
```
** / --api-secret
— 切勿要求用户在聊天中粘贴密钥。
权限：Launch:Write
门户：在聊天外创建或轮换密钥：https://www.gate.com/myaccount/profile/api-key/manage

Installation Check

安装检查

Required: Gate (main), Gate (trading); gate-cli
when using CLI-backed flows (install via
```
setup.sh
```
from this skill when applicable).

Install (MCP / IDE): Run installer skill for your environment — Cursor:

gate-mcp-cursor-installer

; Codex:

gate-mcp-codex-installer

; Claude:

gate-mcp-claude-installer

; OpenClaw:

gate-mcp-openclaw-installer

Credentials: When GATE_API_KEY
and GATE_API_SECRET
are both set (non-empty) for the host, do not require gate-cli config init
— that is equivalent valid config for
```
gate-cli
```
. When both are unset or empty, remind the operator to run gate-cli config init
or to configure GATE_API_KEY
/ GATE_API_SECRET
in the matching skill from the skill library (never ask the user to paste secrets into chat).
Sanity check: Before authenticated or mutating calls, confirm the runtime works (e.g. gate-cli --version
or a read-only check appropriate to this skill); resolve credentials before registration or write operations.

必需组件：Gate（主站）、Gate（交易平台）；使用基于CLI的工作流时需要**
```
gate-cli
```
**（适用时可通过本Skill的
```
setup.sh
```
安装）。
安装（MCP / IDE）：针对您的环境运行安装器Skill — Cursor:
```
gate-mcp-cursor-installer
```
; Codex:
```
gate-mcp-codex-installer
```
; Claude:
```
gate-mcp-claude-installer
```
; OpenClaw:
```
gate-mcp-openclaw-installer
```
。
凭证检查：当主机上的**
```
GATE_API_KEY
```
和
```
GATE_API_SECRET
```
均已设置（非空）时，无需要求运行
```
gate-cli config init
```
** — 这等同于
```
gate-cli
```
的有效配置。当两者均未设置或为空时，提醒操作者运行**
```
gate-cli config init
```
** 或在Skill库中配置匹配Skill的**
```
GATE_API_KEY
```
** / GATE_API_SECRET
（切勿要求用户在聊天中粘贴密钥）。
完整性检查：在进行认证或变更调用之前，确认运行时正常工作（例如**
```
gate-cli --version
```
**或适合本Skill的只读检查）；在报名或写入操作之前解析凭证。

Execution mode

执行模式

Read and strictly follow

references/gate-cli.md

, then execute this skill's CandyDrop workflow.

```
SKILL.md
```
keeps routing and product semantics.
```
references/gate-cli.md
```
is the authoritative
```
gate-cli
```
execution contract for activity/rule queries, registration confirmation gates, progress/record queries, and result verification.

阅读并严格遵循

references/gate-cli.md

，然后执行本Skill的CandyDrop工作流。

```
SKILL.md
```
包含路由和产品语义。
```
references/gate-cli.md
```
是
```
gate-cli
```
执行活动/规则查询、报名确认校验、进度/记录查询和结果验证的权威约定。

Module overview

模块概述

Module	Description	Trigger keywords
Activity List	Browse CandyDrop activities, filter by status/coin/task type	`candydrop` , `candydrop activities` , `activity list` , `ongoing candydrop` , `USDT candydrop`
Activity Rules	View activity rules, prize pools, and tasks	`activity rules` , `task rules` , `prize pool` , `reward rules` , `candydrop rules`
Register	Register for a CandyDrop activity	`register` , `join activity` , `candydrop register` , `participate candydrop`
Task Progress	Query task completion progress for enrolled activities	`task progress` , `completion progress` , `progress query` , `task progress`
Participation Records	Query registration/participation history	`participation records` , `registration records` , `history records` , `participation records`
Airdrop Records	Query airdrop/reward distribution records	`airdrop records` , `reward records` , `received records` , `airdrop records`

模块	描述	触发关键词
活动列表	浏览CandyDrop活动，按状态/币种/任务类型筛选	`candydrop` , `candydrop activities` , `activity list` , `ongoing candydrop` , `USDT candydrop`
活动规则	查看活动规则、奖池和任务	`activity rules` , `task rules` , `prize pool` , `reward rules` , `candydrop rules`
报名	报名参加CandyDrop活动	`register` , `join activity` , `candydrop register` , `participate candydrop`
任务进度	查询已报名活动的任务完成进度	`task progress` , `completion progress` , `progress query` , `task progress`
参与记录	查询报名/参与历史	`participation records` , `registration records` , `history records` , `participation records`
空投记录	查询空投/奖励发放记录	`airdrop records` , `reward records` , `received records` , `airdrop records`

Domain Knowledge

领域知识

CandyDrop concepts

CandyDrop概念

Concept	Description
CandyDrop	A Gate activity platform where users complete tasks (trading, depositing, etc.) to earn airdrop rewards from prize pools.
Activity ( `currency` / `activity_id` )	A CandyDrop campaign for a specific token. Identified by `currency` (token symbol) or `activity_id` (numeric ID).
Activity Status	Lifecycle: `upcoming` (upcoming) → `ongoing` (ongoing) → `ended` (ended).
Registration Status	`registered` (already registered) or `unregistered` (not yet registered).
Record Status	For participation records: `ongoing` (in progress), `awaiting_draw` (awaiting draw), `won` (won), `not_win` (not won).
Prize Pool	Each activity has one or more prize pools, each with a total prize amount ( `prize_all` ), per-user cap ( `prize_limit` ), and a list of tasks.
Task	Individual challenges within a prize pool (e.g. spot trading, futures trading, deposit, invite). Each has a name ( `task_name` ), description ( `task_desc` ), and exclusive label ( `exclusive_label` ).
Task Progress	The user's current completion value for a task (e.g. trading volume, deposit amount). Only shown for registered tasks ( `task_status > 0` ).

概念	描述
CandyDrop	Gate旗下的活动平台，用户完成任务（交易、充值等）即可从奖池中获得空投奖励。
活动（ `currency` / `activity_id` ）	针对特定代币的CandyDrop活动。可通过 `currency` （代币符号）或 `activity_id` （数字ID）识别。
活动状态	生命周期： `upcoming` （即将开始）→ `ongoing` （进行中）→ `ended` （已结束）。
报名状态	`registered` （已报名）或 `unregistered` （未报名）。
记录状态	参与记录： `ongoing` （进行中）、 `awaiting_draw` （待开奖）、 `won` （已中奖）、 `not_win` （未中奖）。
奖池	每个活动包含一个或多个奖池，每个奖池有总奖励金额（ `prize_all` ）、单用户上限（ `prize_limit` ）和任务列表。
任务	奖池内的单个挑战（例如现货交易、合约交易、充值、邀请）。每个任务包含名称（ `task_name` ）、描述（ `task_desc` ）和专属标签（ `exclusive_label` ）。
任务进度	用户当前的任务完成值（例如交易量、充值金额）。仅对已报名任务显示（ `task_status > 0` ）。

Timestamp formatting

时间戳格式

API returns time fields (e.g.
```
start_time
```
,
```
end_time
```
,
```
register_time
```
,
```
airdrop_time
```
) as pre-formatted UTC strings in the format
```
YYYY-MM-DD HH:MM:SS(UTC)
```
.
Tables / lists: Put
```
(UTC)
```
in the column header when the time is UTC. If the header already says
```
(UTC)
```
(ASCII or full-width punctuation variants), do not repeat it on every cell: strip a trailing
```
(UTC)
```
from the API value and show YYYY-MM-DD HH:MM:SS
only (example:
```
2026-04-13 04:04:10
```
, not
```
2026-04-13 04:04:10(UTC)
```
). If the header does not mark UTC, keep the API string as-is so the zone is not lost.
Other surfaces (e.g. inline sentences without a UTC-labeled header): you may keep the API form or use header + stripped cell style consistently within one reply.
Query parameters
```
start_time
```
/
```
end_time
```
for records are integer unix timestamps (seconds). See Timestamp strategy in
```
references/records.md
```
for correct computation.

API返回的时间字段（例如
```
start_time
```
、
```
end_time
```
、
```
register_time
```
、
```
airdrop_time
```
）为预格式化的UTC字符串，格式为
```
YYYY-MM-DD HH:MM:SS(UTC)
```
。
表格/列表：当时间为UTC时，在列标题中添加
```
(UTC)
```
。如果标题已包含
```
(UTC)
```
（ASCII或全角标点变体），请勿在每个单元格中重复：移除API值末尾的
```
(UTC)
```
，仅显示**
```
YYYY-MM-DD HH:MM:SS
```
**（示例：
```
2026-04-13 04:04:10
```
，而非
```
2026-04-13 04:04:10(UTC)
```
）。如果标题未标记UTC，则保留API字符串原样，以免丢失时区信息。
其他场景（例如无UTC标记标题的内联句子）：可保留API格式，或在同一回复中统一使用标题+移除后缀的单元格样式。
记录查询参数
```
start_time
```
/
```
end_time
```
为整数Unix时间戳（秒）。正确计算方式参见
```
references/records.md
```
中的时间戳策略。

Number formatting

数字格式

Category	Precision	Examples
Amounts (rewards, progress values)	8 decimals, trailing zeros removed	`1.23` not `1.23000000`
Airdrop `rewards` (display)	Same numeric formatting, then append + row `currency`	`4.02032 ETH` not `4.02032`
Percentage-like fields	2 decimals, trailing zeros retained	`5.20%` not `5.2%`

类别	精度	示例
金额（奖励、进度值）	8位小数，移除末尾零	`1.23` 而非 `1.23000000`
空投 `rewards` （展示）	相同数字格式，然后追加空格+行内 `currency`	`4.02032 ETH` 而非 `4.02032`
百分比类字段	2位小数，保留末尾零	`5.20%` 而非 `5.2%`

Dual-parameter resolution

双参数解析

Activity query interfaces support locating an activity by either

activity_id

currency

```
currency
```
(e.g. "USDT"): API auto-matches the nearest active activity for that token.
```
activity_id
```
: Precise numeric ID lookup.
Priority:
```
currency
```
is preferred. If user provides both, use both. If only
```
activity_id
```
is given, use it directly. If neither is provided for rules/progress, ask the user for
```
currency
```
.

活动查询接口支持通过**

activity_id

或

currency

**定位活动：

```
currency
```
（例如"USDT"）：API自动匹配该代币最近的活跃活动。
```
activity_id
```
：精确数字ID查询。
优先级：优先使用
```
currency
```
。如果用户同时提供两者，则同时使用。如果仅提供
```
activity_id
```
，则直接使用。如果查询规则/进度时两者均未提供，请向用户询问
```
currency
```
。

Routing rules

路由规则

Intent	Example phrases	Route to
Browse activities	"Show CandyDrop activities", "ongoing candydrop events", "USDT candydrop"	Read `references/activities.md`
Activity rules	"Show CandyDrop rules", "what tasks are in this candydrop", "prize pool details"	Read `references/activities.md`
Register	"Register for CandyDrop USDT", "join this candydrop activity"	Read `references/register.md`
Task progress	"My CandyDrop task progress", "check my candydrop task progress"	Read `references/progress.md`
Participation records	"My CandyDrop participation history", "registration records"	Read `references/records.md`
Airdrop records	"My CandyDrop airdrop rewards", "view airdrop records"	Read `references/records.md`
Unclear	"CandyDrop"	Clarify: browse / rules / register / progress / records, then route. If defaulting to browse/list, reply with minimal activity list only (see `references/activities.md` → Activity list — answer directly).

意图	示例短语	路由至
浏览活动	"显示CandyDrop活动"、"进行中的candydrop活动"、"USDT candydrop"	阅读 `references/activities.md`
活动规则	"显示CandyDrop规则"、"这个candydrop有哪些任务"、"奖池详情"	阅读 `references/activities.md`
报名	"报名USDT CandyDrop"、"加入这个candydrop活动"	阅读 `references/register.md`
任务进度	"我的CandyDrop任务进度"、"查看我的candydrop任务进度"	阅读 `references/progress.md`
参与记录	"我的CandyDrop参与历史"、"报名记录"	阅读 `references/records.md`
空投记录	"我的CandyDrop空投奖励"、"查看空投记录"	阅读 `references/records.md`
意图不明确	"CandyDrop"	澄清：浏览/规则/报名/进度/记录，然后路由。如果默认选择浏览/列表，仅回复极简活动列表（参见 `references/activities.md` → 活动列表 — 直接回复）。

Execution

执行步骤

1. Intent and parameters

1. 意图与参数

Determine module (Activity List / Activity Rules / Register / Task Progress / Participation Records / Airdrop Records).
Register intent: Route to
```
references/register.md
```
. Requires
```
currency
```
(required) and optionally
```
activity_id
```
. Must follow Preview-Confirm flow.

Records intent: Route to

references/records.md

. Extract

currency

status

start_time

end_time

page

limit

Extract parameters:

currency

activity_id

status

rule_name

register_status

limit

offset

page

start_time

end_time

Missing: If user says "CandyDrop" without specifying intent, ask which operation or show activities by default — if showing the list, use concise output (title + table, no glossary; see
```
references/activities.md
```
).

确定模块（活动列表/活动规则/报名/任务进度/参与记录/空投记录）。
报名意图：路由至
```
references/register.md
```
。需要
```
currency
```
（必填），可选
```
activity_id
```
。必须遵循预览确认流程。

记录意图：路由至

references/records.md

。提取

currency

、

status

、

start_time

、

end_time

、

page

、

limit

。

提取参数：

currency

、

activity_id

、

status

、

rule_name

、

register_status

、

limit

、

offset

、

page

、

start_time

、

end_time

。

参数缺失：如果用户仅说"CandyDrop"未指定意图，请询问具体操作或默认显示活动列表 — 如果显示列表，使用简洁输出（标题+表格，无术语表；参见
```
references/activities.md
```
）。

2. Tool selection

2. 工具选择

Module	MCP tool	Required params	Optional params
Activity List	`gate-cli cex launch candy-drop activities`	—	`currency` , `status` , `rule_name` , `register_status` , `limit` , `offset`
Activity Rules	`gate-cli cex launch candy-drop rules`	`currency` or `activity_id` (at least one)	—
Register	`gate-cli cex launch candy-drop register`	`currency`	`activity_id`
Task Progress	`gate-cli cex launch candy-drop progress`	`currency` or `activity_id` (at least one)	—
Participation Records	`gate-cli cex launch candy-drop participations`	—	`currency` , `status` , `start_time` , `end_time` , `page` , `limit`
Airdrop Records	`gate-cli cex launch candy-drop airdrops`	—	`currency` , `start_time` , `end_time` , `page` , `limit`

Register: Show registration preview, wait for confirmation, then call
```
gate-cli cex launch candy-drop register
```
.
Records: Follow the Timestamp strategy in
```
references/records.md
```
for time parameter computation.

模块	MCP工具	必填参数	可选参数
活动列表	`gate-cli cex launch candy-drop activities`	—	`currency` , `status` , `rule_name` , `register_status` , `limit` , `offset`
活动规则	`gate-cli cex launch candy-drop rules`	`currency` 或 `activity_id` （至少一个）	—
报名	`gate-cli cex launch candy-drop register`	`currency`	`activity_id`
任务进度	`gate-cli cex launch candy-drop progress`	`currency` 或 `activity_id` （至少一个）	—
参与记录	`gate-cli cex launch candy-drop participations`	—	`currency` , `status` , `start_time` , `end_time` , `page` , `limit`
空投记录	`gate-cli cex launch candy-drop airdrops`	—	`currency` , `start_time` , `end_time` , `page` , `limit`

报名：显示报名预览，等待用户确认，然后调用
```
gate-cli cex launch candy-drop register
```
。
记录：遵循
```
references/records.md
```
中的时间戳策略计算时间参数。

3. Format response

3. 响应格式

Use the Response Template and field names from the reference file for the chosen module.
Activity List: Optional one-line title + data table; for browse / “what activities are there” intents, no tutorial, field glossary, or pasting the task-type map — localize
```
rule_name
```
only inside cells. Fields:
```
currency
```
,
```
total_rewards
```
,
```
start_time
```
,
```
end_time
```
,
```
rule_name
```
,
```
participants
```
,
```
user_max_rewards
```
.

Activity Rules: show

currency

total_rewards

start_time

end_time

, and per prize pool:

prize_all

prize_limit

tasks

Task Progress: show

currency

total_rewards

start_time

end_time

, and per task:

task_name

task_desc

value

Participation Records: show
```
currency
```
,
```
status
```
,
```
register_time
```
,
```
id
```
(time cells: strip trailing
```
(UTC)
```
when the table header already marks UTC — see Timestamp formatting above).
Airdrop Records: show
```
currency
```
,
```
airdrop_time
```
, rewards
with token unit (
```
{rewards} {currency}
```
) only — do not show flash-convert / USDT (
```
convert_amount
```
) (see
```
references/records.md
```
).

使用所选模块参考文件中的响应模板和字段名称。
活动列表：可选一行标题 + 数据表格；对于浏览/"有哪些活动"意图，不显示教程、字段术语表或任务类型映射 — 仅在单元格内本地化
```
rule_name
```
。字段：
```
currency
```
、
```
total_rewards
```
、
```
start_time
```
、
```
end_time
```
、
```
rule_name
```
、
```
participants
```
、
```
user_max_rewards
```
。

活动规则：显示

currency

、

total_rewards

、

start_time

、

end_time

，以及每个奖池的

prize_all

、

prize_limit

、

tasks

。

报名：显示确认结果（
```
success
```
）。
任务进度：显示
```
currency
```
、
```
total_rewards
```
、
```
start_time
```
、
```
end_time
```
，以及每个任务的
```
task_name
```
、
```
task_desc
```
、
```
value
```
。
参与记录：显示
```
currency
```
、
```
status
```
、
```
register_time
```
、
```
id
```
（时间单元格：当表格标题已标记UTC时，移除末尾的
```
(UTC)
```
— 参见上方时间戳格式）。
空投记录：仅显示
```
currency
```
、
```
airdrop_time
```
、带代币单位的
rewards
（
```
{rewards} {currency}
```
） — 请勿显示闪兑/USDT（
```
convert_amount
```
）（参见
```
references/records.md
```
）。

Report template

报告模板

After each operation, output a short standardized result consistent with the reference (e.g. activity list, rules, registration confirmation, progress, records). Activity list answers stay minimal (see

references/activities.md

). Use the API field names and semantic values; where the reference requires localization (e.g. rule_name
task types), render in the user’s language per

references/activities.md

without embedding the whole mapping as user-visible prose.

Language adaptation: Always respond in the same language as the user's input. The Response Templates in reference files define the structure and fields to display, not the literal output language. Translate all display labels to match the user's language.

Must localize (not tickers / not “keep English”):

rule_name
entries in the activity list (and anywhere shown as “task type”): use the Task types mapping table in
```
references/activities.md
```
— these strings describe product task categories (e.g. Futures, Simple Earn), not token symbols.

Do NOT translate (keep as-is regardless of language):

Product name:
```
CandyDrop
```
Currency symbols from API: USDT, GT, BTC, DOGE, etc.
Technical IDs and their values:
```
id
```
,
```
activity_id
```
(internal use, do NOT display unless relevant)
Timestamp layout
```
YYYY-MM-DD HH:MM:SS
```
and the literal
```
(UTC)
```
token when it must remain visible (e.g. no UTC in header); do not drop timezone information in those cases
API error labels:
```
INVALID_PARAM_VALUE
```
,
```
SERVER_ERROR
```
Numeric values, percentages, and the unit
```
USD
```
in thresholds

All other display labels should be translated to match the user's language.

每次操作后，输出符合参考文件的简短标准化结果（例如活动列表、规则、报名确认、进度、记录）。活动列表回复需保持极简（参见

references/activities.md

）。使用API的字段名称和语义值；当参考文件要求本地化时（例如**

rule_name

任务类型**），根据

references/activities.md

以用户语言呈现，不要将整个映射作为用户可见文本嵌入。

语言适配：始终使用与用户输入相同的语言回复。参考文件中的响应模板定义了要显示的结构和字段，而非字面输出语言。将所有显示标签翻译为匹配用户语言的版本。

必须本地化（非代币/非"保留英文"）：

活动列表中的**
```
rule_name
```
条目（以及任何显示为"任务类型"的地方）：使用
references/activities.md
中的任务类型映射表 — 这些字符串描述产品任务类别**（例如Futures、Simple Earn），而非代币符号。

请勿翻译（无论语言如何均保留原样）：

产品名称：
```
CandyDrop
```
API返回的货币符号：USDT、GT、BTC、DOGE等
技术ID及其值：
```
id
```
、
```
activity_id
```
（内部使用，除非相关否则请勿显示）
时间戳格式
```
YYYY-MM-DD HH:MM:SS
```
和必须保留可见的文字
```
(UTC)
```
（例如标题中无UTC标记时）；在这些情况下请勿丢失时区信息
API错误标签：
```
INVALID_PARAM_VALUE
```
、
```
SERVER_ERROR
```
数值、百分比和阈值中的单位
```
USD
```

所有其他显示标签均应翻译为匹配用户语言的版本。

Error Handling

错误处理

API error labels

API错误标签

The API returns structured errors with a

label

field. Map them as follows:

API label	User-facing message
`INVALID_PARAM_VALUE`	"Invalid request parameters. Please check your input and try again."
`SERVER_ERROR`	"System busy. Please try again later."
`Activity not found`	"Activity not found. Please check the currency or activity ID."
`currency is required`	"Please provide a currency name (e.g. USDT)."
`Device token is required`	"Registration requires a device token. Please try from the Gate app or website."

API返回带有

label

字段的结构化错误。映射方式如下：

API标签	用户可见消息
`INVALID_PARAM_VALUE`	"请求参数无效，请检查输入后重试。"
`SERVER_ERROR`	"系统繁忙，请稍后重试。"
`Activity not found`	"未找到活动，请检查币种或活动ID。"
`currency is required`	"请提供币种名称（例如USDT）。"
`Device token is required`	"报名需要设备令牌，请尝试从Gate App或官网操作。"

Empty result handling

空结果处理

Scenario	Action
Empty activity list	"No CandyDrop activities match your criteria. Try different filters or check back later."
Empty participation records	"You have no CandyDrop participation records. Browse active activities to get started."
Empty airdrop records	"No airdrop rewards found. Rewards are typically distributed after the activity ends."
Compliance restriction	"Due to compliance restrictions, CandyDrop is not available in your region."
API error / 401	"Unable to fetch CandyDrop data. Please log in and try again."

场景	操作
活动列表为空	"没有符合您条件的CandyDrop活动，请尝试不同筛选条件或稍后再试。"
参与记录为空	"您没有CandyDrop参与记录，请浏览活跃活动开始参与。"
空投记录为空	"未找到空投奖励，奖励通常在活动结束后发放。"
合规限制	"由于合规限制，您所在地区无法参与CandyDrop活动。"
API错误/401	"无法获取CandyDrop数据，请登录后重试。"

Safety rules

安全规则

Confirmation required

需要确认

Register is a write operation. Before calling
```
gate-cli cex launch candy-drop register
```
, MUST show a registration preview and wait for explicit user confirmation.
Preview format: activity currency, activity ID (if known).
Ask user to reply "confirm" to proceed or "cancel" to abort.
Only call the API after receiving explicit confirmation.

报名是写入操作。在调用
```
gate-cli cex launch candy-drop register
```
之前，必须显示报名预览并等待用户明确确认。
预览格式：活动币种、活动ID（如果已知）。
请用户回复"confirm"确认继续或"cancel"取消操作。
仅在收到明确确认后调用API。

Compliance

合规要求

When the API returns a compliance or region restriction error, display a friendly message: "Due to compliance restrictions, CandyDrop is not available in your region." Do NOT retry.

当API返回合规或区域限制错误时，显示友好消息："由于合规限制，您所在地区无法参与CandyDrop活动。" 请勿重试。

Data integrity

数据完整性

Preserve
```
currency
```
and
```
activity_id
```
exactly as the user provided.
Do NOT fabricate activity data, reward amounts, or task progress.
Only display data returned by actual API responses.

完全保留用户提供的
```
currency
```
和
```
activity_id
```
。
请勿编造活动数据、奖励金额或任务进度。
仅显示实际API返回的数据。