nansen-wallet_skill

This skill helps you manage wallets securely by creating, listing, exporting, and sending tokens with enforced password policies.
  • Python

2.5k

GitHub Stars

2

Bundled Files

2 months ago

Catalog Refreshed

3 months ago

First Indexed

Readme & install

Copy the install command, review bundled files from the catalogue, and read any extended description pulled from the listing source.

Installation

Preview and clipboard use veilstrat where the catalogue uses aiagentskills.

npx veilstrat add skill openclaw/skills --skill nansen-wallet

  • _meta.json284 B
  • SKILL.md3.3 KB

Overview

This skill provides command-line wallet management for creating, listing, inspecting, exporting, sending, and deleting encrypted wallets. It automates secure password generation and persistence, and supports EVM and Solana chains with dry-run and max-send options. Use it to manage multiple wallets, check balances, and perform token transfers from a consistent, scripted interface.

How this skill works

The skill wraps nansen wallet commands and enforces a password persistence workflow: generate or reuse NANSEN_WALLET_PASSWORD stored in ~/.nansen/.env and source it before any operation. It exposes commands to create wallets, list and show details, set a default wallet, export or delete keys, and send native tokens with flags for chain, amount, max, and dry-run. Network endpoints and API key are configurable through environment variables for EVM and Solana RPCs.

When to use it

  • Creating a new encrypted wallet and setting a persisted password
  • Listing available wallets or viewing a wallet’s details and default status
  • Sending native tokens on EVM or Solana networks with optional dry-run
  • Exporting or deleting a wallet from local storage
  • Scripting wallet operations in CI or automation where env-based secrets are required

Best practices

  • Always persist NANSEN_WALLET_PASSWORD to ~/.nansen/.env before any wallet command — never rely on ephemeral memory
  • Do not display or log the wallet password; source the env file in-shell instead
  • If ~/.nansen/.env exists, reuse the existing password; never overwrite it
  • Use --dry-run to preview transactions before broadcasting, and --max carefully when sending entire balance
  • Restrict permissions on ~/.nansen/.env (chmod 600) and back it up securely if needed

Example use cases

  • Initialize automated workflows that create and fund wallets for testing across Ethereum and Solana
  • Quickly list and inspect wallet addresses and balances during audits or operational checks
  • Send a precise amount or the entire native balance to another address, with a dry-run to validate gas and fees
  • Export a wallet to move keys to a hardware wallet or secure backup
  • Delete ephemeral wallets created for short-lived tasks

FAQ

The wallet uses AES-256-GCM encryption and has no recovery mechanism. Persisting NANSEN_WALLET_PASSWORD to ~/.nansen/.env ensures you can decrypt wallets after restarts; losing the password permanently locks funds.

Can I override RPC endpoints or API keys?

Yes. Set NANSEN_EVM_RPC or NANSEN_SOLANA_RPC for custom endpoints and NANSEN_API_KEY or run nansen login for API authentication. Source ~/.nansen/.env before running wallet commands.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational