20 CLI Commands: Complete Wallet Management for Your Self-Hosted Setup
Self-hosting your crypto wallet infrastructure means full control over your private keys, transaction policies, and agent permissions — no third-party custody required. WAIaaS provides a complete CLI toolkit with 20 commands for managing wallets, sessions, and policies on your own infrastructure. Whether you're running a single AI trading bot or managing multiple autonomous agents, these CLI commands give you granular control over every aspect of your wallet-as-a-service deployment.
Why CLI Management Matters for Self-Hosters
When you're running your own wallet infrastructure, you need more than just a web interface. You need scriptable commands for automation, backup strategies that work with your existing systems, and the ability to provision wallets without touching a GUI. Traditional wallet solutions force you to click through interfaces or rely on their hosted APIs with rate limits and custody risks.
Self-hosted wallet management eliminates these constraints. Your private keys never leave your server, your transaction policies can't be overridden by external services, and your AI agents operate with the permissions you define — not what a SaaS provider allows.
The Complete CLI Toolkit
WAIaaS includes 20 CLI commands covering wallet lifecycle, session management, backups, and integrations. Here's how they solve real self-hosting challenges:
Initial Setup and Provisioning
The init command creates your data directory and configuration files:
# Standard setup with password prompt
waiaas init
# Auto-provision mode generates a random master password
waiaas init --auto-provision
Auto-provision is perfect for Docker deployments where you want zero interaction during container startup. The master password gets saved to recovery.key for later hardening.
Start your daemon with complete control over the process:
waiaas start # Foreground with logs
waiaas start --daemon # Background process
waiaas status # Check if running
waiaas stop # Clean shutdown
Wallet and Session Management
Create wallets for different purposes without any external API calls:
# Create wallets for different chains
waiaas wallet create --name "trading-bot" --chain solana --environment mainnet
waiaas wallet create --name "ethereum-defi" --chain evm --environment mainnet
# Get wallet details
waiaas wallet info --wallet-id <uuid>
The quickset command creates a complete multi-chain setup in seconds:
# Creates Ethereum + Solana wallets with MCP sessions
waiaas quickset --mode mainnet
# Outputs ready-to-use MCP configuration for Claude Desktop
Sessions provide AI agents with scoped access to specific wallets:
# Create session for an AI agent
waiaas session prompt --wallet-id <uuid>
# Returns: "Add this to your agent's environment:"
# WAIAAS_SESSION_TOKEN=wai_sess_eyJhbGciOiJIUzI1NiJ9...
Backup and Recovery Strategy
Self-hosters need reliable backup strategies that integrate with existing infrastructure:
# Create encrypted backup bundle
waiaas backup create --output-file "./backups/waiaas-$(date +%Y%m%d).backup"
# List backup contents without restoring
waiaas backup inspect --file "./backups/waiaas-20240408.backup"
# View all available backups
waiaas backup list
# Restore from backup (destructive operation)
waiaas restore --file "./backups/waiaas-20240408.backup"
Backup files are encrypted and contain everything needed to restore your complete setup: wallet keys, policies, session configurations, and transaction history. This integrates cleanly with standard backup tools like rsync, rclone, or your favorite backup solution.
MCP Integration for AI Frameworks
Model Context Protocol (MCP) connects your wallets to AI frameworks like Claude Desktop:
# Auto-register all wallets with Claude Desktop
waiaas mcp setup --all
# Register specific wallet
waiaas mcp setup --wallet-id <uuid>
This writes configuration directly to Claude's config file, enabling your AI agents to access 45 MCP tools for wallet operations, DeFi actions, and transaction management.
Owner Connection and Security
The owner authentication system provides human oversight for high-value transactions:
# Connect hardware wallet or signing app
waiaas owner connect
# Check connection status
waiaas owner status
# Disconnect when done
waiaas owner disconnect
This establishes the cryptographic identity for transaction approvals and emergency controls, separate from your master password.
Notification Channels
Set up signing channels for transaction approvals:
# Configure push notifications for mobile approval
waiaas notification setup --channel push-relay
# Set up Telegram bot integration
waiaas notification setup --channel telegram
These channels enable human-in-the-loop approvals for transactions that exceed your instant execution policies.
Updates and Maintenance
Keep your self-hosted instance current:
# Update to latest version
waiaas update
# Check current status and version
waiaas status
Self-hosted updates give you control over when to upgrade, unlike SaaS platforms that force updates.
Docker Integration for Production
The CLI commands integrate seamlessly with Docker deployments. Here's a production-ready setup:
# Start with Docker Compose
git clone https://github.com/minhoyoo-iotrust/WAIaaS.git
cd WAIaaS
docker compose up -d
# Initialize through the container
docker exec waiaas-daemon waiaas init --auto-provision
# Create wallets via CLI
docker exec waiaas-daemon waiaas quickset --mode mainnet
# Retrieve auto-generated master password
docker exec waiaas-daemon cat /data/recovery.key
Environment variables control daemon behavior:
# In your .env file or docker-compose.yml
WAIAAS_AUTO_PROVISION=true # Skip password prompts
WAIAAS_DAEMON_PORT=3100 # API port
WAIAAS_DATA_DIR=/data # Persistent storage
WAIAAS_RPC_SOLANA_MAINNET=<your-rpc> # Custom RPC endpoints
Quick Start: Complete Self-Hosted Setup
Here's how to go from zero to running AI agents with wallet access in under 5 minutes:
- Install and initialize:
npm install -g @waiaas/cli
waiaas init --auto-provision
waiaas start
- Create wallets and sessions:
waiaas quickset --mode mainnet
# Outputs MCP configuration automatically
- Set up Claude Desktop integration:
waiaas mcp setup --all
- Create first backup:
waiaas backup create --output-file "./waiaas-backup-$(date +%Y%m%d).backup"
- Test with Claude: Open Claude Desktop and ask "Check my wallet balance" — it should connect via MCP and return your wallet information.
Production Considerations
For production self-hosted deployments, consider these CLI patterns:
Automated backups with cron:
# Daily encrypted backups with 30-day retention
0 2 * * * /usr/local/bin/waiaas backup create --output-file "/backups/waiaas-$(date +\%Y\%m\%d).backup" && find /backups -name "waiaas-*.backup" -mtime +30 -delete
Health monitoring in your monitoring stack:
#!/bin/bash
# Health check script
waiaas status || {
echo "WAIaaS daemon down, restarting..."
waiaas start --daemon
}
Secure password rotation:
# After initial auto-provision, harden the master password
waiaas set-master
rm /data/recovery.key # Remove auto-generated password file
The CLI's scriptable nature means it integrates with existing infrastructure automation tools like Ansible, Terraform, or simple bash scripts.
What's Next
These 20 CLI commands provide complete control over your self-hosted wallet infrastructure, from initial setup through production operations. The combination of Docker deployment, automated backups, and MCP integration creates a robust foundation for AI agent wallet access without third-party dependencies.
Ready to deploy your own wallet infrastructure? Clone the repository at https://github.com/minhoyoo-iotrust/WAIaaS and follow the self-hosting guide. For detailed configuration options and advanced deployment patterns, visit the documentation at https://waiaas.ai.