nansen-wallet-manager
Original:🇺🇸 English
Translated
Wallet management — create, list, show, export, send, delete. Use when creating wallets, checking balances, or sending tokens.
3installs
Sourcenansen-ai/nansen-cli
Added on
NPX Install
npx skill4agent add nansen-ai/nansen-cli nansen-wallet-managerTags
Translated version includes tags in frontmatterSKILL.md Content
View Translation Comparison →Wallet
Auth Setup
bash
# Save API key (non-interactive)
nansen login --api-key <key>
# Or via env var:
NANSEN_API_KEY=<key> nansen login
# Verify
nansen research profiler labels --address 0xd8dA6BF26964aF9D7eEd9e03E53415D37aA96045 --chain ethereumWallet Creation (Two-Step Agent Flow)
Wallet creation requires a password from the human user. The agent must NOT generate or store the password itself.
Step 1 (Agent → Human): Ask the user to provide a wallet password (minimum 12 characters).Step 2 (Agent executes): Run the create command with the password the user gave you.
bash
NANSEN_WALLET_PASSWORD="<password_from_user>" nansen wallet createAfter creation, the CLI automatically saves the password:
- OS keychain (macOS Keychain, Linux secret-tool, Windows Credential Manager) — secure, preferred
- ~/.nansen/wallets/.credentials file — insecure fallback when no keychain is available (e.g. containers, CI)
All future wallet operations retrieve the password automatically — no env var or human input needed.
If the file fallback is used, the CLI prints a warning on every operation. To migrate to secure storage later, run .
.credentialsnansen wallet securePassword resolution order (automatic)
- env var (if set)
NANSEN_WALLET_PASSWORD - OS keychain (saved automatically on wallet create)
- file (insecure fallback, with warning)
~/.nansen/wallets/.credentials - Structured JSON error with instructions (if none available)
Critical rules for agents
- NEVER generate a password yourself — always ask the human user
- NEVER store the password in files, memory, logs, or conversation history
- NEVER use flag — that enables interactive prompts which agents cannot handle
--human - After wallet creation, you do NOT need the password for future operations — the keychain handles it
- If you get a error, ask the user to provide their password again
PASSWORD_REQUIRED
Create
bash
# Ask the user for a password first, then:
NANSEN_WALLET_PASSWORD="<password_from_user>" nansen wallet create
# Or with a custom name:
NANSEN_WALLET_PASSWORD="<password_from_user>" nansen wallet create --name tradingList & Show
bash
nansen wallet list
nansen wallet show <name>
nansen wallet default <name>Send
bash
# Send native token (SOL, ETH) — password auto-resolved from keychain
nansen wallet send --to <addr> --amount 1.5 --chain solana
# Send entire balance
nansen wallet send --to <addr> --chain evm --max
# Dry run (preview, no broadcast)
nansen wallet send --to <addr> --amount 1.0 --chain evm --dry-runExport & Delete
bash
# Password auto-resolved from keychain
nansen wallet export <name>
nansen wallet delete <name>Forget Password
bash
# Remove saved password from all stores (keychain + .credentials file)
nansen wallet forget-passwordMigrate to Secure Storage
bash
nansen wallet secureFor detailed migration steps (from , , or env-var-only setups), see the nansen-wallet-migration skill.
~/.nansen/.env.credentialsFlags
| Flag | Purpose |
|---|---|
| Recipient address |
| Amount to send |
| |
| Send entire balance |
| Preview without broadcasting |
| Enable interactive prompts (human terminal use only — agents must NOT use this) |
| Skip encryption (keys stored in plaintext — NOT recommended) |
Environment Variables
| Var | Purpose |
|---|---|
| Wallet encryption password — only needed for initial |
| API key (also set via |
| Custom EVM RPC endpoint |
| Custom Solana RPC endpoint |