| name | okx-agentic-wallet |
| description | OKX Agentic Wallet — the single skill for the user's wallet and on-chain execution. Use it whenever the user wants to operate their wallet or execute an on-chain action, including: login & accounts, balance / holdings, wallet address / deposit / receive, send / transfer, contract calls (approve / deposit / withdraw), transaction history & status, message signing, wallet export & policy; pay gas with a stablecoin (Gas Station, Solana); swap / trade / buy / sell / convert, get a quote; cross-chain bridge & track arrival; limit orders (buy dip / take profit / stop loss / buy above) plus cancel / list / resume them; broadcast / gas / simulate / track a transaction; look up any public address's holdings; security scanning (token / honeypot 蜜罐 / 貔貅, DApp phishing, tx & signature checks, approvals); audit log. Once matched, follow this skill's Intent Routing to dispatch to the exact action. |
| license | MIT |
| metadata | {"author":"okx","version":"4.4.9","homepage":"https://web3.okx.com"} |
Onchain OS Wallet
Unified wallet skill driving the onchainos CLI: wallet lifecycle, Gas Station, DEX swap, cross-chain bridge, limit-order strategy, transaction gateway, public-address portfolio, security scanning, and audit log.
Intent Routing
Match the user intent to a row, then read that row's linked file first — it holds the flow. Read only the matched file; do not load other rows' files. Each file links its own deeper files (cli-reference, troubleshooting) at the bottom via explicit links — open those when the flow needs them; never construct a file path yourself.
| User Intent | Reference |
|---|
| Sign in / connect / social login (Google / Apple / Email) / logout; add / switch account; login status | wallet |
| My wallet address / QR code; check my (logged-in) balance / holdings | wallet |
| Send / transfer native or ERC-20 / SPL tokens | wallet |
| Call a contract (approve / deposit / withdraw / custom function) | wallet |
| Transaction history / tx detail / order status; sign a message (personalSign / EIP-712) | wallet |
| Policy / spending limit / whitelist; export wallet / mnemonic; MEV protection for a contract-call; third-party Solana plugin write pre-flight | wallet |
| Apple-login wallet differs from the OKX Wallet App / "missing" balance; rename a wallet or account; how transaction signing works (TEE) | account-faq |
Pay gas with a stablecoin on Solana; enable / disable / change default gas token / status; a send / contract-call returns gasStationUsed or a Gas Station Confirming; Gas Station FAQ / "check order" | gas-station |
| Swap / trade / buy / sell / convert tokens; quote; best route; calldata-only swap; liquidity sources; ERC-20 approval for a DEX | swap |
| Bridge / cross-chain swap / move tokens between chains; bridge quote / fee comparison; supported bridges; track cross-chain arrival | bridge |
Pre-flight Checks
Before the first onchainos command this session, read and follow _shared/preflight.md.
Build the Command
- Read the matched row's linked file first (per the Intent Routing table) — it carries the flow and the commands you need. Never guess subcommand, flag, or file names.
- When you need exact flags, defaults, or return-field schemas that the domain file doesn't spell out, run
onchainos <group> <subcommand> --help (the CLI is the source of truth), or load that domain's -cli-reference.md when the flow needs it (each domain file lists its own deeper files at the bottom). Don't load it up front.
- Confirm before any state-changing command. Display the prompt, get an explicit affirmative, and follow the Confirming Response rule below.
Chain Name Support
--chain accepts numeric chain IDs and human-readable names. Resolution rules and the supported-chain matrix live in _shared/chain-support.md. If <100% confident of a chain name, run onchainos wallet chains.
Confirming Response
Some state-changing commands return confirming (exit code 2) when the backend needs user confirmation. The response carries message (prompt to show) and next (what to do after they confirm).
- Display
message and ask for confirmation.
- Confirms → follow
next (usually: re-run the same command with --force appended).
- Declines → do NOT proceed; tell the user it was cancelled.
Never pass --force on the FIRST invocation of a state-changing command. Add --force only after all of: (1) you ran the command once without it, (2) the CLI returned a Confirming response (exit code 2, "confirming": true), (3) you displayed message and the user explicitly confirmed.
Amount Display Rules
- Token amounts in UI units (
1.5 ETH), never base units.
- USD values with 2 decimal places; if
< 0.01, show full precision.
- Large amounts in shorthand (
$1.2M, $340K); sort holdings by USD value descending.
- In balance/holdings displays, show the abbreviated contract address alongside the symbol (
0x1234...abcd); native tokens with empty tokenAddress → (native).
- Flag suspicious prices: if a token looks like a wrapped/bridged variant (
wETH, stETH, wBTC, xOKB…) and its price differs >50% from the base token, add an inline price unverified flag and suggest onchainos token price-info to cross-check.
Security & Global Notes
- Credential protection: never log, display, or ask for session tokens,
clientId, API keys, private keys, seed phrases, or passwords. Never expose: accessToken, refreshToken, apiKey, secretKey, passphrase, sessionKey, sessionCert, teeId, saTeeId, encryptedSessionSk, signingKey, raw tx data. Show raw accountName (never raw accountId to the user).
- Credential recovery: on a
Credentials corrupted / "please login again" error the local credential store is unreadable — don't retry the same command, re-authenticate the user with wallet login. See wallet-troubleshooting.md.
- Address integrity (funds-loss risk): any on-chain identifier shown to the user (wallet address,
txHash, signature, contract address) MUST be echoed verbatim, character-for-character from the most recent CLI stdout. Never reproduce an identifier from memory, expand an abbreviated form, or re-type it across messages — re-invoke the CLI (wallet addresses or wallet status) and copy from fresh stdout. Never paraphrase, normalize case, insert spaces, or line-break inside an identifier. Always display the full txHash.
- No address hallucination: never fabricate a contract address — malicious tokens clone legitimate names. Only use addresses from a token lookup or the user's explicit input.
- Recipient validation: EVM
0x-prefixed, 42 chars; Solana Base58, 32–44 chars. Validate before sending.
- Transaction simulation: the CLI runs pre-execution simulation; if
executeResult is false → show executeErrorMsg, do NOT broadcast.
- Risk action priority:
block > warn > empty (safe). Top-level action = highest priority from riskItemDetail.
- CLI-classified risk verdicts: the CLI returns the risk verdict as fields — : read them; : recompute from raw / / client-side, since the CLI owns the matrix and hand-derived rules drift from it. → per-token ( / / / ) plus top-level (severity > > > ). / → per-route ( / / ) plus . The CLI only classifies; you decide the interaction (halt on , explicit yes/no on , surface the and ask on , proceed on / ).
