Gate Dex Wallet

Gate DEX Wallet

Pure Routing Layer — This SKILL.md is a lightweight router. All sub-module details live in references/.

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

Signing gate — terminal tx-checkin (mandatory)

Before any MCP call to dex_wallet_sign_transaction, dex_wallet_sign_message, or dex_tx_x402_fetch:

1. User must pass the existing confirmation gates (preview / message text / payment intent) for that operation.
2. Agent MUST run the terminal tx-checkin flow in references/tx-checkin.md and treat success as a hard prerequisite. Do not skip because a prior operation did not require it or no error was returned. Use the prebuilt check-in binaries under tools/tx-checkin/bin/ — end users do not compile (go build / go run not required). Resolve the CLI from this skill’s skill_root: Linux → tx-checkin-linux-amd64, macOS → tx-checkin-darwin-universal, Windows → tx-checkin-windows-amd64.exe — users need not set TX_CHECKIN (optional override only); see references/tx-checkin.md.
3. After dex_tx_transfer_preview, check-in must use the preview field txBundle only: write that string to a file and run tx-checkin -tx-bundle-file — do not assemble txbundle JSON from unsigned_tx_hex or other fields (see references/tx-checkin.md).
4. x402 (dex_tx_x402_fetch): Always complete terminal check-in before the first dex_tx_x402_fetch call in that payment flow. Do not call dex_tx_x402_fetch first to probe 402 or “see if GV needs check-in.” After successful check-in, pass checkin_token from stdout JSON into dex_tx_x402_fetch when the tool exposes that parameter; use -intent / -message (or documented body) for check-in per references/x402.md and references/tx-checkin.md.
5. Other single-step MCP tools that sign internally: same terminal check-in immediately before the tool when the gateway requires it; follow backend docs for checkin_token / intent payload.

Applicable Scenarios

Use this skill when the user wants to manage their on-chain wallet account, identity, or assets:

• Authenticate or manage sessions (login via Google or Gate OAuth, logout)
• Query token balances, total portfolio value, or wallet addresses
• View transaction history or past swap records
• Transfer or send tokens to an address (single or batch); mandatory terminal tx-checkin before any signing (references/tx-checkin.md)
• Withdraw or cash out on-chain to their Gate Exchange account (deposit address resolved for their UID; not CEX-internal balance moves from this skill)
• Pay for HTTP 402 resources via x402 protocol (EVM exact/upto, Solana exact/upto); terminal tx-checkin before dex_tx_x402_fetch (references/x402.md, references/tx-checkin.md)
• Interact with DApps (connect wallet, sign messages, approve tokens, call contracts)
• Use the gate-wallet CLI tool for any of the above
• Detect or configure MCP Server connectivity

Capability Boundaries

Module Routing

Route to the corresponding sub-module based on user intent:

MCP Server Connection Detection

Before the first MCP tool call in a session, perform one connection probe:

1. Discover: Scan configured MCP servers for tools dex_wallet_get_token_list, dex_tx_quote, and dex_tx_swap.
2. Identify: Accept flexible server names (gate-wallet, gate-dex, dex, wallet, user-gate-wallet, or any custom name).
3. Verify: CallMcpTool(server="<id>", toolName="dex_chain_config", arguments={chain: "eth"}).

OpenClaw Platform Detection

When the OpenClaw/mcporter platform is detected, route MCP calls through mcporter:

CallMcpTool(server="mcporter", toolName="call_tool", arguments={
  server: "<gate-dex-server>",
  tool: "<tool_name>",
  arguments: { ...params }
})

Setup Guide (shown once on detection failure)

Gate DEX MCP Server:
  URL:  https://api.gatemcp.ai/mcp/dex
  Type: HTTP

  Cursor:      Settings -> MCP -> Add server, or edit ~/.cursor/mcp.json
  Claude Code:  claude mcp add --transport http gate-dex --scope project https://api.gatemcp.ai/mcp/dex
  Codex CLI:    codex mcp add gate-dex --transport http --url https://api.gatemcp.ai/mcp/dex

Runtime Error Handling

Follow-up Routing

After completing an operation, proactively suggest 2-4 relevant next actions to the user (see each module's "Post-XXX Suggestions" section for templates). Then route based on the user's response:

NOT This Skill (Common Misroutes)

These intents should NOT trigger this skill:

Supported Chains

EVM: eth, bsc, polygon, arbitrum, optimism, avax, base | Non-EVM: sol

Security Rules

1. Authentication first: Verify mcp_token validity before all operations; on failure follow §3 of gate-runtime-rules.md.
2. Token confidentiality: Never display mcp_token in plaintext; use placeholders like <mcp_token>.
3. MCP Server errors: Display all MCP Server error messages to users transparently — never hide or modify them.