Licensing
Proprietary Software - Copyright © 2025 Ant Somers. All Rights Reserved.
See LICENSE for full terms.
Wealth Trading Bot requires a valid license for production use.
Overview
- Development Mode: Licensing is optional (for testing)
- Production Mode: Valid license required
- Machine Binding: Each license can be activated on a limited number of machines
- Automatic Validation: License is re-validated periodically during runtime
Getting a License
- Contact: Visit wealth.thiras.net for licensing inquiries
- Receive License Key: You'll receive a license key via secure channel
- Configure: Set the license key environment variable
export WEALTH__LICENSING__LICENSE_KEY="YOUR-LICENSE-KEY-HERE"
- Run the Bot: License activates automatically on first run
wealth run
License Commands
Check License Status
wealth license check
Shows:
- License ID and status
- Expiration date
- Current machine activation
Show Machine Fingerprint
wealth license show-fingerprint
Use this when contacting support about licensing issues.
Validate License
wealth license validate
Tests license connectivity and configuration.
Deactivate License
wealth license deactivate --confirm
Use when transferring your license to a different machine.
Transferring Your License
Moving to a New Machine
-
On the old machine, deactivate:
wealth license deactivate --confirm -
On the new machine, configure and run:
export WEALTH__LICENSING__LICENSE_KEY="your-license-key" wealth run
The license will automatically activate on the new machine.
If You Can't Access the Old Machine
Contact support with your machine fingerprint:
wealth license show-fingerprint
They can remotely deactivate your old machine.
License Types
| Type | Use Case | Features |
|---|---|---|
| Development | Testing & development | Lower machine limits, shorter duration |
| Production | Live trading | Higher machine limits, longer duration |
| Kubernetes | Container deployments | Higher machine limits, supports pod scheduling |
Kubernetes Deployments
The Helm chart automatically handles license activation in Kubernetes environments. The fingerprint is generated from the node name and namespace, ensuring:
- Stable identity: Survives pod restarts on the same node
- Security compliant: Works with Pod Security Standards (no hostPath mounts)
- Proper tracking: Different nodes count as separate machines
Note: For multi-node clusters, ensure your license has sufficient machine activation slots for your expected cluster size.
Troubleshooting
"License key not configured"
Set your license key:
export WEALTH__LICENSING__LICENSE_KEY="your-license-key"
"Machine activation limit exceeded"
You've reached your activation limit. Either:
- Deactivate an old machine:
wealth license deactivate --confirm - Contact support to increase your limit
"License has expired"
Contact support to renew your license.
"Network error"
Ensure your firewall allows HTTPS connections to api.keygen.sh.
"Failed to get machine fingerprint" (Containers)
If running in Docker without the Helm chart, ensure /etc/machine-id is accessible or contact support for guidance.
Security Best Practices
- Never commit license keys to version control
- Use environment variables for license configuration
- Contact support if you suspect your key was compromised
FAQ
Q: Can I run the bot without a license for testing?
A: Yes, debug builds don't require a license.
Q: How many machines can I activate?
A: Depends on your license type. Check with sales.
Q: What happens if my license expires while running?
A: The bot will gracefully shut down within 6 hours, closing all positions safely.
Q: Can I transfer my license to a different machine?
A: Yes, deactivate on the old machine first, then activate on the new one.
Support
- Sales & Licensing: Visit wealth.thiras.net
- Technical Support: Open an issue on GitHub (include your machine fingerprint)