Open source cloud mining CLI for Midnight's Scavenger Mine. Deploy in one click on AWS with the fastest Rust implementation.
USE AT YOUR OWN RISK
- AWS Costs: This software deploys cloud infrastructure that will incur AWS charges. You are solely responsible for all costs.
- No Guarantees: Mining profitability is not guaranteed and may result in losses.
- Security: You are responsible for securing your private keys and credentials.
- Monitoring: Always monitor your AWS billing and resource usage.
- Testing: Start with small deployments to understand costs before scaling.
The authors provide no warranty and are not liable for any losses, damages, or costs incurred.
- 🚀 One-click AWS deployment
- ⚡ Fastest Rust-based mining implementation
- 📊 Real-time status monitoring
- 🔄 Auto-scaling support
- 💰 Multi-wallet management
- 📝 CloudWatch logs integration
- 💻 Local mining support for development
# 1. Initialize configuration
npx @night-cloud/cli init
# 2. Generate wallets
npx @night-cloud/cli wallet --region ap-south-1 --auto
# 3. Deploy to AWS
# As of latest difficulty, 6 addresses per EC2 instance (c7g.xlarge) is sufficient
npx @night-cloud/cli deploy --region ap-south-1 --instances 100 --addresses-per-instance 6
# 4. Monitor your deployment
npx @night-cloud/cli dashboard# Install globally
npm install -g @night-cloud/cli
# Follow the same steps
night-cloud init
night-cloud wallet --region ap-south-1 --auto
night-cloud deploy --region ap-south-1 --instances 100 --addresses-per-instance 6
night-cloud statusWhy you need wallets first: Each Cardano wallet address can submit one solution per challenge. More wallets = more potential solutions.
Wallet-to-instance ratio: By default, each EC2 instance (c7g.xlarge) is assigned 10 wallet addresses. This is typically more than enough since:
- Each instance can find multiple solutions per challenge
- Solutions are distributed across the 10 addresses automatically
- You can adjust this with
--addresses-per-instanceif needed
Planning your deployment: NOTE: These numbers of frequently changing as the difficulty increases. You may want to lower your addresses per instance configuration over time.
- Target 10 solutions/hour? Generate ~25 wallets
- Target 100 solutions/hour? Generate ~250 wallets
- Target 1000 solutions/hour? Generate ~2500 wallets
- Deploy instances based on compute needs, not wallet count
Region selection - Cost optimization:
ap-south-1 (Mumbai) has the cheapest c7g.xlarge spot instances (~$0.06-0.08/hour vs $0.08-0.12/hour in other regions).
Recommended strategy:
- Start with ap-south-1 - Deploy as many instances as you need here first
- Max out ap-south-1 - Scale to your AWS account limits in this region
- Only then expand - If you need more capacity, deploy to other cheaper regions like
ap-northeast-2,ap-northeast-3,us-east-2, etc.
This can save you 30-40% on infrastructure costs compared to deploying across multiple regions from the start.
- Node.js 18 or higher
- AWS account with credentials configured
- AWS CLI installed and configured (recommended)
Initialize configuration and validate AWS credentials
night-cloud initDeploy mining infrastructure to AWS
night-cloud deploy --region ap-south-1 --instances 5Options:
--region, -r: AWS region (default: ap-south-1)--instances, -i: Number of instances--miners-per-instance, -m: Addresses per instance (default: 10)
Show current deployment status
night-cloud status --region ap-south-1Scale instances up or down
night-cloud scale --region ap-south-1 --instances 10Stop mining in a region
night-cloud stop --region ap-south-1
night-cloud stop --region ap-south-1 --terminate # Terminate instancesEmergency kill switch - immediately terminate all mining operations
night-cloud kill --region ap-south-1
night-cloud kill --region ap-south-1 --force # Skip confirmation prompts- Sets Auto Scaling Group capacity to 0
- Terminates all running instances immediately
- Stops all mining operations
- Cannot be undone
Options:
--region, -r: AWS region (required)--force, -f: Skip confirmation prompts (use with caution!)
When to use: Use this command when you need to immediately stop all mining operations, such as:
- Emergency cost control
- Unexpected AWS billing alerts
- Critical issues requiring immediate shutdown
Note: Unlike stop, this command requires double confirmation (type "KILL" to confirm) unless you use the --force flag. After killing, you can resume mining with the scale command.
Manage Cardano wallets
# Generate wallets (automatically registers them)
night-cloud wallet --region ap-south-1 --generate 50
# Generate without registering
night-cloud wallet --region ap-south-1 --generate 50 --register=false
# List wallets
night-cloud wallet --region ap-south-1 --list
# Register existing wallets with API
night-cloud wallet --region ap-south-1 --register
# AUTO MODE: Continuously generate wallets with rate limit protection
# Generates 50 wallets per batch, waits 60s between batches
# Perfect for bulk wallet generation - just let it run!
night-cloud wallet --region ap-south-1 --autoAuto Mode Features:
- 🤖 Generates 50 wallets per batch automatically
- ⏳ Built-in 60-second cooldown between batches to avoid rate limits
- 🔄 Runs continuously until you stop it (Ctrl+C)
- 📊 Shows progress, batch numbers, and countdown timer
- ✅ Automatically registers wallets with the API
- 🛡️ Error recovery - continues even if a batch fails
View CloudWatch logs from instances
night-cloud logs --region ap-south-1
night-cloud logs --region ap-south-1 --follow # Follow logsLive dashboard monitoring all regions at once
night-cloud dashboard
night-cloud dashboard --refresh 5 # Refresh every 5 secondsShows:
- Global totals across all regions (instances, wallets, solutions)
- Current challenge and difficulty
- Per-region breakdown with instances, wallets, and solution rates
- Automatically filters to show only active regions
Perfect for: Multi-region deployments where you want a single pane of glass to monitor everything!
Consolidate all rewards from your mining wallets to a single destination address.
# Consolidate all wallets from a region to your personal wallet
night-cloud consolidate --region ap-south-1 --to addr...Options:
--region, -r: AWS region to consolidate from (required)--to, -t: Destination Cardano address - must be an address you control (required)--workers, -w: Number of parallel worker threads (default: 10)--batch-size, -b: Number of donations per batch (default: 100)--pause, -p: Seconds to pause between batches (default: 2)--output, -o: Output JSON filename (auto-generated if not specified)
-
Consolidation Window: You can run this command at any time! The consolidation window closes 24 hours after mining ends. If you don't consolidate, you'll need to claim from each individual wallet separately.
-
Use Your Own Address: The destination address (
--to) MUST be a Cardano address you personally control (hardware wallet, browser wallet like Nami/Eternl, etc.). Do NOT use one of the generated mining wallets. -
Run Once Per Region: You only need to run this command once per region. It will process all wallets in that region automatically.
-
No Support for Missed Consolidation: If you don't consolidate during the window, no support will be added to this project to help you sign claim transactions from individual wallets. Consolidate to make your life easier!
-
Why Consolidate: By consolidating, you'll only need to sign a single transaction to claim all your NIGHT tokens instead of signing hundreds or thousands of transactions from individual mining wallets.
Example workflow:
night-cloud consolidate --region ap-south-1 --to addr...
night-cloud consolidate --region us-east-1 --to addr...
night-cloud consolidate --region eu-west-1 --to addr...
# Then when claiming opens, you'll only need to claim from your single browser or hardware wallet!The command will:
- Load all wallets from the specified region
- Check each wallet's solution count
- Skip wallets with no solutions
- Donate all rewards to your destination address in parallel
- Save detailed logs to
donations/directory - Display total solutions consolidated
Run the miner locally (for development/testing)
night-cloud mine --region ap-south-1
night-cloud mine --region ap-south-1 --addresses 5 --workers 4Options:
--region, -r: AWS region to load wallets from (required)--addresses, -a: Number of addresses to mine with (default: all)--workers, -w: Number of worker processes (default: CPU cores)--poll-interval, -p: Challenge polling interval in ms (default: 60000)
Note: Local mining still uses AWS S3 for solution tracking and challenge queue management. This is useful for testing the mining logic without deploying to EC2.
Configuration is stored in .night-config.json in your working directory.
During initialization, you'll be prompted for:
- AWS region
- Spot instance max price
- Addresses per instance
- Keys directory - where to store wallet keys (default:
./keys)
Typical costs (as of 2025):
- c7g.xlarge spot instance: ~$0.06-0.10/hour
- 10 instances: ~$7-12/day
- Always monitor your actual AWS billing
- Never commit your keys directory or
.night-config.json - Use AWS IAM roles with minimal required permissions
- Enable AWS billing alerts
- Regularly rotate credentials
- Keep private keys secure and backed up
- Add your keys directory to
.gitignore
- GitHub Issues: https://github.com/nightcloudminer/night-cloud-cli/issues
- Documentation: https://github.com/nightcloudminer/night-cloud-cli#readme
MIT License - See LICENSE file for details
Remember: You are solely responsible for all costs, security, and compliance when using this software.