okx-agentic-wallet

SKILL.md

Onchain OS Wallet

Wallet operations: authentication, balance, token transfers, transaction history, and smart contract calls.

Instruction Priority

This document uses tagged blocks to indicate rule severity. In case of conflict, higher priority wins:

<NEVER> — Absolute prohibition. Violation may cause irreversible fund loss. Never bypass.

<MUST> — Mandatory step. Skipping breaks functionality or safety.

<SHOULD> — Best practice. Follow when possible; deviation acceptable with reason.

Pre-flight Checks

Parameter Rules
--chain Resolution

--chain accepts both numeric chain ID (e.g. 1, 501, 196) and human-readable names (e.g. ethereum, solana, xlayer).

Translate user input into a CLI-recognized chain name or numeric ID (e.g. "币安链" → bsc, "以太坊" → ethereum). The CLI accepts common human names / aliases (eth, bsc, sol, arb, base, xlayer, op, avax, …) and any numeric chain ID; the authoritative supported set is in _shared/chain-support.md (or run onchainos wallet chains).

If <100% confident in the mapping → ask user to confirm before calling.

Pass the resolved name or ID to --chain.

If the command returns "unsupported chain: ...", the name was not in the CLI mapping. Ask the user to confirm, and run onchainos wallet chains to show the full supported list.

If no confident match: do NOT guess — ask the user. Display chain names as human-readable (e.g. "Ethereum", "BNB Chain"), never IDs.

Amount

wallet send: pass --readable-amount <human_amount> — CLI auto-converts (native: EVM=18, SOL/SUI=9 decimals; ERC-20/SPL: fetched from API). Never compute minimal units manually. Use --amt only for raw minimal units.

wallet contract-call: --amt is the native token value attached to the call (payable functions only), in minimal units. Default "0" for non-payable. EVM=18 decimals, SOL=9.

Command Index

Full parameter tables, return field schemas, and usage examples → cli-reference.md. Don't guess subcommand names — the valid set is listed below; you may also run onchainos wallet <cmd> --help to confirm syntax. login / verify are covered in Authentication.

Group
Subcommands
Auth

A — Account
add (auth) · switch <id> · status · logout · chains · addresses [--chain] · qrcode --address
mostly no

B — Balance
balance [--chain] [--token-address <addr>] [--all] [--force]
yes

D — Transaction
send · contract-call
yes

D-GS — Gas Station
gas-station update-default-token / enable / disable / status / setup
yes

E — History
history (list) · history --tx-hash <h> --chain <c> --address <a> (detail)
yes

F — Sign Message
sign-message --chain <c> --from <a> --message <m> [--type eip712]
yes

X Layer Testnet faucet: trigger when the user asks for testnet tokens, or when wallet balance --chain xlayer_test returns OKB = 0. Reply using the template below — substitute {address} with the user's current wallet address, keep the URL exactly as shown, and do not invent extra steps.

Your current wallet address [{address}] has an OKB balance of 0 on X Layer Testnet.

You can claim testnet tokens from the official OKX faucet:
https://web3.okx.com/xlayer/faucet

Once the page loads, paste your wallet address [{address}] into the address input field on the faucet page, then follow the prompts to select and claim. The faucet currently supports OKB, USDG, USDT, and USDC on X Layer Testnet.

Let me know after you've claimed and I'll help confirm whether the balance has arrived.

Gas Station pays gas with stablecoins (USDT/USDC/USDG) when native is insufficient; activates automatically during wallet send. Full param/flow detail in references/gas-station.md.

Safety Rules

Before wallet contract-call (custom calldata), run onchainos security tx-scan first.

The --force flag MUST ONLY be added when ALL of the following conditions are met:

You have already called the command without --force once.

The API returned a confirming response (exit code 2, "confirming": true).

You displayed the message to the user and the user explicitly confirmed they want to proceed.

Determine intent before executing (wrong command → loss of funds):

Intent
Command
Example

Send native token (ETH, SOL, BNB…)
wallet send --chain <chain>
"Send 0.1 ETH to 0xAbc"

Send ERC-20 / SPL token (USDC, USDT…)
wallet send --chain <chain> --contract-token
"Transfer 100 USDC to 0xAbc"

Interact with a smart contract (approve, deposit, withdraw, custom function call…)
wallet contract-call --chain <chain>
"Approve USDC for spender", "Call withdraw on contract 0xDef"

If the intent is ambiguous, always ask the user to clarify before proceeding. Never guess.

Transaction submitted. The returned Tx Hash is for tracking purposes only — it does NOT mean the transaction has been included on-chain, confirmed, or executed successfully. Final status must be verified by querying the transaction's on-chain confirmation status.

Load references/eip7702-upgrade.md only when the response contains needUpdate7702=true or authHashFor7702. Never expose 7702 terminology to the user — see Global Notes vocabulary table.

For user-facing wording of gas-station enable / disable / update-default-token (pre-confirmation prompts and success messages), use the sanctioned templates in references/gas-station.md → "User-Facing Reply Templates (Management Commands)". The enable/disable mechanism is an internal DB flag flip — never surface that mechanism to the user.

Treat the intent as "ask about OKX Agentic Wallet Gas Station".

Answer using the verbatim FAQ templates in references/gas-station.md → FAQ section. Translate to the user's language; do NOT paraphrase the content.

Do NOT answer from general training knowledge about ERC-4337, Paymaster, Biconomy, Gelato, Pimlico, Alchemy Account Kit, meta-transactions, or any third-party gas-abstraction protocol. Do NOT frame OKX Gas Station as "a category of services" or "one of several paymaster solutions". Also do NOT conflate it with OKX DEX Gas Swap — that is a separate OKX product, not this Gas Station feature.

Do NOT list alternative/competing protocols unless the user explicitly asks for comparisons. Even then, keep the scope limited and avoid implying OKX Gas Station is interchangeable with generic paymaster/relayer tech.

Confirming Response

Some commands return confirming (exit code 2) when backend requires user confirmation (e.g., high-risk tx).

Output format

{
  "confirming": true,
  "message": "The human-readable prompt to show the user.",
  "next": "Instructions for what the agent should do after user confirms."
}

How to handle

Display the message field to the user and ask for confirmation.

If the user confirms: follow the instructions in the next field (typically re-running the same command with --force flag appended).

If the user declines: do NOT proceed. Inform the user the operation was cancelled.

Example flow

# 1. Run command without --force
onchainos wallet send --readable-amount "0.1" --recipient "0xAbc..." --chain 1
# → exit code 2, confirming: true → show message to user

# 2. User confirms → re-run with --force
onchainos wallet send --readable-amount "0.1" --recipient "0xAbc..." --chain 1 --force

Third-Party Plugin Pre-flight

When the user invokes a third-party DeFi plugin (e.g. aave-v3-plugin, uniswap-plugin) that internally calls wallet contract-call --force, the plugin is a black box. Before dispatching ANY third-party plugin command that performs an on-chain write, load references/plugin-preflight.md and run the Gas Station pre-flight (wallet gas-station status → branch on recommendation). That reference also holds the skip conditions, post-failure reactive diagnosis, and the --force exit-code table (0/1/2/3).

Authentication

For commands requiring auth (sections B, D, E), check login state:

Run onchainos wallet status. Read data.loggedIn from the response. If loggedIn: true, proceed.

If not logged in, or the user explicitly requests to re-login:

2a. Display the following message to the user verbatim (translated to the user's language):

You need to log in with your email first before adding a wallet. What is your email address?
We also offer an API Key login method that doesn't require an email. If interested, visit https://web3.okx.com/onchainos/dev-docs/home/api-access-and-usage

2b. Once the user provides their email, run: onchainos wallet login <email> --locale <locale>.
Then display the following message verbatim (translated to the user's language):

English: "A verification code has been sent to {email}. Please check your inbox and tell me the code."
Chinese: "验证码已发送到 {email}，请查收邮件并告诉我验证码。"
Once the user provides the code, run: onchainos wallet verify <code>.
AI should always infer --locale from conversation context and include it:

Chinese (简体/繁体, or user writes in Chinese) → zh_CN

English or any other language → en_US (default)

If you cannot confidently determine the user's language, default to en_US.

Fallback: If the inferred locale is not in the supported set (en_US, zh_CN),
the CLI silently falls back to en_US and emits a stderr warning. The login flow
still succeeds. AI callers do not need to handle this case specially.

If the user declines to provide an email:

3a. Display the following message to the user verbatim (translated to the user's language):

We also offer an API Key login method that doesn't require an email. If interested, visit https://web3.okx.com/onchainos/dev-docs/home/api-access-and-usage

3b. If the user confirms they want to use API Key, run onchainos wallet login directly (the CLI picks up OKX_API_KEY / OKX_SECRET_KEY / OKX_PASSPHRASE from env).

3c. After silent login succeeds, inform the user that they have been logged in via the API Key method.

3d. Login-diff handling (applies to BOTH Step 2 email login and Step 3b AK login) — when a wallet login invocation returns a confirming: true response with exit code 2:

If message.contains("not the account you used last time") (substring match on the verbatim discriminator, NOT the leading ⚠️ emoji) → this is the login-diff gate. The CLI message body already names the scenario and includes any masked identifiers; render it to the user verbatim (translated if needed; the discriminator substring stays English-only and verbatim — never translate, paraphrase, or modify it). Collect Yes/No:

On Yes → re-run the same command with --force appended (onchainos wallet login <email> --locale <locale> --force, or the AK equivalent with --force).

On No → abort. Do NOT call any auth API. Do NOT mutate any local state. Tell the user: "Login aborted; previous session preserved."

Ambiguous answer → re-prompt EXACTLY ONCE with the same warning. If the second answer is still ambiguous, treat it as No and abort.

Any other confirming response → handle per its own discriminator.

After login succeeds, display the full account list with addresses by running onchainos wallet balance.

New user check: If the wallet verify or wallet login response contains "isNew": true, output the Policy Settings template followed by the Wallet Export template (load references/portal-actions.md). If "isNew": false, skip this step.

After successful login: a wallet account is created automatically — never call wallet add unless the user is already logged in and explicitly requests an additional account.

MEV Protection

contract-call supports --mev-protection (Ethereum / BSC / Base / Solana; send does not). Load references/mev-protection.md when the user requests MEV protection, or before a high-value / DEX-swap contract-call. Solana additionally requires --jito-unsigned-tx — never substitute --unsigned-tx.

Amount Display Rules

Token amounts always in UI units (1.5 ETH), never base units (1500000000000000000)

USD values with 2 decimal places

Large amounts in shorthand ($1.2M, $340K)

Sort by USD value descending

Always show abbreviated contract address alongside token symbol (format: 0x1234...abcd). For native tokens with empty tokenContractAddress, display (native).

Flag suspicious prices: if the token appears to be a wrapped/bridged variant (e.g., symbol like wETH, stETH, wBTC, xOKB) AND the reported price differs >50% from the known base token price, add an inline price unverified flag and suggest running onchainos token price-info to cross-check.

Security Notes

TEE signing: Private key never leaves the secure enclave.

Transaction simulation: CLI runs pre-execution simulation. If executeResult is false → show executeErrorMsg, do NOT broadcast.

Sensitive fields never to expose: accessToken, refreshToken, apiKey, secretKey, passphrase, sessionKey, sessionCert, teeId, encryptedSessionSk, signingKey, raw tx data. Only show: email, accountId, accountName, isNew, addressList, txHash.

Recipient address validation: EVM: 0x-prefixed, 42 chars. Solana: Base58, 32-44 chars. Validate before sending.

Risk action priority: block > warn > empty (safe). Top-level action = highest priority from riskItemDetail.

Approve calls:

Do NOT set approve amount to type(uint256).max or 2^256-1 or any equivalent "infinite" value.

Do NOT call setApprovalForAll(operator, true) — this grants full control over all tokens of that type.

If the user explicitly requests unlimited approval, you MUST:

Warn that this is irreversible and allows the spender to drain all tokens at any time.

Wait for explicit secondary confirmation ("I understand the risk, proceed").

Even after confirmation, cap the approve amount to the actual needed amount (e.g. swap amount + 10% buffer), never unlimited.

If the user insists on unlimited after the warning, refuse and suggest they execute manually via a block explorer.

Portal Actions — Policy / Wallet Export

These flows output a verbatim Web-portal template (Policy Settings or Wallet Export), chosen by loginType. Load references/portal-actions.md for the templates and exact steps when any trigger below fires. Policy and wallet export are configured by the user on the Web portal only — the Agent detects intent, explains risk, and gives the jump link; it never displays mnemonic / private key content.

Trigger
Action (detail in references/portal-actions.md)

New user login (isNew: true)
Handled in Authentication step 5 — Policy Settings + Wallet Export templates

After a successful wallet add
Output Policy Settings template, prefixed "New account created."

User asks about Policy / spending limit / daily limit / whitelist
Run wallet status, show current settings if any flag set, then Policy Settings template

User asks to export wallet / mnemonic / migrate
MUST first run competition user-status; if any joinStatus=1, show forfeit warning and stop for confirmation before the Wallet Export template

Policy includes ONLY: per-transaction limit, daily transfer limit, daily trade limit, transfer whitelist. Do NOT invent other rules (no "tx count limit", "gas limit", "token blacklist").

Edge Cases

Load on error: references/troubleshooting.md

Global Notes

FAQ

For Gas Station FAQ (what is it, how it works, supported tokens/chains, open/close flow): read references/gas-station.md FAQ section.

Q: The agent cannot autonomously sign and execute transactions — it says local signing is required or asks the user to sign manually. How does signing work?

A: OKX Agentic Wallet uses TEE (Trusted Execution Environment) for transaction signing. The private key is generated and stored inside a server-side secure enclave — it never leaves the TEE.