Nansen Limit Orders

⚙️ Configuration

A Solana wallet configured in nansen-cli: nansen wallet show (or

nansen wallet create if none exists). Local, Privy, and WalletConnect wallets are all supported for trade limit-order.

The wallet must hold the sell token plus a small amount of SOL for fees.

For the alert fallback: a notification channel (Telegram chat ID, Slack or

Discord webhook, or generic webhook URL).

NANSEN_API_KEY. Smart alerts are internal-only; non-internal users get 404.

First-time trade limit-order create auto-registers a trading vault and

caches a JWT at ~/.nansen/limit-order-auth.json for ~23h.

> Two mechanisms, not one. The limit order itself is price-triggered — > it executes when the market price crosses the target. A companion smart > alert is a settlement confirmation — it fires after the trade settles > on-chain (i.e. when the bought token actually arrives in the wallet). They > are independent: the order handles the trigger, the alert tells the user the > fill landed.

📋 Tips & Best Practices

Chain aliases for alerts: Hyperliquid = hyperevm, BSC = bnb.

Use single quotes for names with $ or special characters.

For immediate swaps (not price-triggered), use the nansen-trading skill.

For webhook delivery of alerts, pair with nansen-alerts-webhook-listener.